An open protocol, authored by WorkOS, that lets AI agents register for a service on behalf of a user. The service hosts a Markdown file, usually at https://yourapp.com/auth.md, describing the registration flows it supports and the scopes it offers. The agent then registers either by presenting an identity assertion from its provider (agent verified) or by having the user confirm a code (user claimed), and receives a short-lived, scoped OAuth token. It composes existing OAuth standards rather than replacing them.
auth.md
auth.md answers a question the OAuth stack leaves open for agents: how an agent signs a user up for a
service it has never seen, without a human filling in a sign-up form. A service publishes auth.md at
its domain, naming the registration flows it accepts and the scopes it offers.
The spec builds discovery on standards already in the catalog. An agent finds the authorization server
through Protected Resource Metadata (/.well-known/oauth-protected-resource, RFC 9728) and
authorization server metadata (RFC 8414), then registers by one of these paths:
- Agent verified. The agent’s identity provider vouches for the user with an Identity Assertion JWT Authorization Grant (ID-JAG), using the JWT bearer grant (RFC 7523).
- User claimed. The agent shows the user a code to confirm, in the style of the device authorization grant (RFC 8628).
- Service auth. Added in v0.6.0. The agent passes a
login_hintemail, modelled on OIDC CIBA, and the service authenticates the user out of band.
Tokens are revocable (RFC 7009), and security events use RFC 8417 and RFC 8935. WorkOS authors the protocol and offers it as a toggle in AuthKit, but the spec is MIT-licensed and not tied to WorkOS infrastructure.
Related standards
Standards this one builds on, supersedes, profiles or is commonly deployed beside.