Resolve third-party identity to ~handle
The agent maps an external identifier like a GitHub login or email to the user's canonical ~alter handle, enabling cross-platform identity linking without exposing PII.
How it works
Read-onlyProductivity and planning
The agent takes a third-party key (e.g., GitHub username, email) and calls alter_resolve_by_key. It checks the response for 'exists: true' and extracts the handle. If the key is not linked or opted-in, it returns null. This allows the agent to verify if a user has an ~alter identity associated with their external account.
Prompt
Paste this into an agent that has the servers below connected. Adjust the names and dates to your own.
Prompt for Resolve third-party identity to ~handle
Resolve the GitHub user 'octocat' to their ~alter handle using the alter_resolve_by_key tool.MCP servers it needs
Source
The vendor page this playbook is drawn from, and the passage that supports it.
alter_resolve_by_key Free Resolve a paired third-party identity key, an email address or an OAuth platform user id, to the bound ~handle.Docs | ~alter