Introduction

Overview

auth.md provides a standardized path for agents to register for services on behalf of users. It provides multiple implementation paths to provide flexibility to meet an application's needs.

At its core, auth.md is a small Markdown file an application hosts at its domain — typically https://service.com/auth.md. The file describes how agents register with that service, which flows it supports, the scopes it exposes, and what to do once registered. Because Markdown is plain text, the same file works as documentation for human integrators and as a discoverable runtime artifact for agents. See how an auth.md is structured.

There are two primary flows for how an agent can register with an app:

Applications decide which flows they support. Only the agent verified flow requires integration by an agent. The user claimed flow is designed to be discoverable and self-navigable by agents based on details hosted by the app at their auth.md page.

You can follow the guides below to learn how to implement agent registration in your app or in your agent.

Integration guides

Contact Us

If you have questions reach out to us at authmd@workos.com. We also want to know if you have implemented auth.md so we can feature you here.