docs: retire the public-key guide and make the AgentID sign-in guide API-first - #245
Open
sidharth0612 wants to merge 2 commits into
Open
sidharth0612 wants to merge 2 commits into
sidharth0612 wants to merge 2 commits into
Conversation
The agent-signed approval endpoint was removed on 2026-09-08 (agentmail-api #1156) and the issuer dropped keypair approval on 2026-09-05, but the guide stayed live and in the Guides nav, and the enrollment guide still said the flow remains supported during migration. Delete the guide, drop it from the nav, redirect its slug to the enrollment guide so the changelog link keeps resolving, and replace the migration section with a short retirement note. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
The guide described the flow from the browser's point of view: enroll a browser, attach a browser, browser activation. The product is one authenticated API call that authorizes a sign-in for an inbox; the client that holds the resulting key is a detail. Rewrite around the call, and say "client" or "the sign-in page" where the text said browser. What remains is the slug, the browser_origin wire field, and the list of retired routes, none of which can be renamed here. Also fixes two errors: the intro said the key type is `browser` (it is `public_key`), and both code samples validated agentmail_api_keys_endpoint against the authorize URL, which can never match; they now check agentmail_authorize_endpoint. The action example gains the status endpoint, accept_disclosure, and remembered_approval_days the page now publishes, and the samples forward accept_disclosure. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
sidharth0612
changed the title
duharry0915
approved these changes
Sep 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Two commits.
1. Retire the public-key authentication guide. The agent-signed approval endpoint was removed on 2026-09-08 (agentmail-api #1156) and the issuer dropped keypair approval on 2026-09-05, but the guide was still live, still in the Guides nav, and the sign-in guide still said the flow "remains supported during migration". Delete the guide, drop it from the nav, redirect its slug to
/agentid-browser-enrollmentso the July changelog link keeps resolving, and replace the migration section with a retirement note. Supersedes #232 (conflicts with main after #231) and #233 (the live guide already emitsagentid_session_required).2. Make the sign-in guide API-first. It described everything from the browser's side: enroll a browser, attach a browser, browser activation. The product is one authenticated call,
POST /v0/inboxes/{inbox_id}/authorize, that authorizes a sign-in for an inbox; the client holding the resulting key is a detail. Rewritten around the call. "browser" goes from 39 mentions to 7, and the 7 are the slug, thebrowser_originwire field in the JSON and samples, and the list of retired route names.This also fixes two real errors in the guide:
browser. It ispublic_key, as the JSON below it already showed.agentmail_api_keys_endpointagainst the authorize URL. That field is a deprecated alias pointing at/api-keys, so the check could never pass. They now checkagentmail_authorize_endpoint.And it brings the action example up to what the page publishes today:
agentmail_api_key_status_endpoint,accept_disclosure,remembered_approval_days, and the<meta name="agentid-session-action">mirror. The samples forwardaccept_disclosurewhen present. The required permission is stated asprovider_connect, notapi_key_create.🤖 Generated with Claude Code