---
title: "auth.md"
description: "auth.md standardizes how AI agents register with apps, discover supported flows, request scopes, and receive secure user-scoped credentials."
url: https://workos.com/auth-md
---

[auth.md](https://workos.com/auth-md)

# auth.md

Enable agents to register users without the sign-up form. Auth.md provides secure agent registration that any app can implement.

[Make your app agent ready](https://workos.com/auth-md/docs)

VerifiedAgent verified

ClaimedUser claimed

Looks like your app is almost finished. What would you like to do today?

Deploy my app to Cloudflare

Add Firecrawl scraping to my app

Add auth with WorkOS AuthKit

Tap an option↑↓ to navigate · ↵ to select

## Adopted by

- [Add your app](mailto:authmd@workos.com?subject=auth.md%20listing%20request)

## Get started

Make your app agent-ready

For services that want agents to register users on behalf of their customers.

[Read the apps guide](https://workos.com/auth-md/docs/apps)

Become an identity provider

For platforms whose agents act on behalf of users.

[Read the provider guide](https://workos.com/auth-md/docs/agent-providers)

One-click enable with AuthKit

Turn on Agent Registration in the WorkOS Dashboard to enable auth.md.

[Read the docs](https://workos.com/docs/authkit/agent-registration)

## FAQs

- What is auth.md?
  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](https://workos.com/auth-md/docs/auth-md).
- How does an agent register a user with my app?
  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](https://workos.com/auth-md/docs/apps).
- What's the difference between the agent verified and user claimed flows?
  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](https://workos.com/auth-md/docs/flows/verified) · [User claimed](https://workos.com/auth-md/docs/flows/claimed).
- What credentials get issued to the agent?
  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.
- Is auth.md a WorkOS only feature or an open protocol?
  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](https://github.com/workos/auth.md).

## Contact us

We're shaping auth.md with early adopters. Tell us what you're building, ask a question, or share feedback.

authmd@workos.com
