Enable agents to register users without the sign-up form. Auth.md provides secure agent registration that any app can implement.
Looks like your app is almost finished. What would you like to do today?
Tap an option↑↓ to navigate · ↵ to select
Make your app agent-ready
For services that want agents to register users on behalf of their customers.
Become an identity provider
For platforms whose agents act on behalf of users.
One-click enable with AuthKit
Get in touch to enable auth.md on your account.
Get early access
A Markdown file an application hosts at its domain — typically https://yourapp.com/auth.md — that tells agents how to register on behalf of a user. It includes which flows are supported, which scopes exist, and how to register for the service. See the file format.
The agent fetches your auth.md, picks a supported flow, and either presents a verified identity assertion (agent verified flow) or walks the user through a code-confirmation claim (user claimed flow). You stay in control of which flows you accept and what credentials get issued. Read the apps guide.
Agent verified is agent-attested — the agent's identity provider vouches for the user, no human in the loop. User claimed needs no provider — the agent shows the user a code, they sign in and confirm it. Most apps support both and let the agent pick the right one. Agent verified · User claimed.
A scoped access token tied to the user — short-lived and revocable. It's issued over standard OAuth, so you reuse the API auth you already have.
It's open. WorkOS authors the protocol, but auth.md isn't tied to WorkOS infrastructure — it composes existing OAuth standards (Protected Resource Metadata, ID-JAG identity assertions) and any app can publish or any agent can read one with no WorkOS account required. See the protocol on GitHub.
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。