Cross Domain · security identity · IETF — individual submission in the OAuth namespace, not yet working-group adopted

AAuth — Agent Identity and Authorization Protocol (draft-hardt-oauth-aauth-protocol)

An IETF Internet-Draft from Dick Hardt, one of the authors of OAuth 2.0, that gives every agent its own keypair and its own portable identifier of the form aauth:local@domain, then lets it authenticate to a resource it has never registered with by signing the HTTP request itself. It replaces the shared client secret with HTTP Message Signatures over Ed25519, replaces the pre-registered client with four /.well-known/aauth-*.json metadata documents, and adds a mid-task consent round trip — a 401 carrying an AAuth-Requirement header — so a person can approve an access a resource asks for while the agent is already running. It does not replace OAuth; it covers the agent-to-resource case OAuth’s compile-time client model was never built for.

www.aauth.dev/The standard
IETF — individual submission in the OAuth namespace, not yet working-group adoptedGoverning body
2026First published
draft-hardt-oauth-aauth-protocol (20 ...Current version
Yes — four `/.well-known/aauth-*.json...Machine-readable schema · open
0providers in the catalog

Also known as draft-hardt-oauth-aauth-protocol, Agent Identity and Authorization Protocol, AAuth Protocol.

Providers that carry AAuth 0

No provider in the catalog carries this standard as a tag yet. That is a statement about the catalog's tagging, not about adoption: a provider that implements AAuth and says so in its APIs.json profile appears here on the next build. Add or correct a listing.

Read from the API Evangelist standards directory, facts verified 2026-08-30. Provider links come from the catalog's own identity tags and are rebuilt nightly. If this page is wrong about a standard or a provider, say so.