Documentation
Give every agent action an identity you can verify
A typical tool or API request does not identify the individual agent that produced it. It also does not show whether that agent still matches its registered instructions or whether a leaked token is being replayed. Auth51 adds those checks to the authorization path. These docs are organized around the task you want to complete.
New here? Start with the Quickstart, then read Agent identity for the core identity model.
Install the client, run your agent, and review its discovered identity in the console. One import, with no configuration required.
Quickstart →Learn how agent identity and intent tokens work, including why a stolen token cannot be used without its bound key.
Read the concepts →Explore the standards Auth51 builds on, including OAuth, token exchange, and DPoP, along with the protocol draft and paper.
Standards & research →