# Agent Authorization Grant (AAuth) vs OAuth Profile for Delegated AI Agent Authorization (DAAP)

The map lists them as complementary: sites and agents commonly implement both.

[3 Permit](/category/permit/) [Agent Authorization Grant](/protocols/aauth/) · [3 Permit](/category/permit/) [OAuth Profile for Delegated AI Agent Authorization](/protocols/daap/)

|  | [Agent Authorization Grant](/protocols/aauth/) AAuth | [OAuth Profile for Delegated AI Agent Authorization](/protocols/daap/) DAAP |
| --- | --- | --- |
| Lifecycle step | 3 Permit: What may the agent do here? | 3 Permit: What may the agent do here? |
| Answers | How can a conversational AI agent, reached over a channel without browser redirect (phone, SMS), obtain a properly scoped OAuth access token without impersonating the user? | How can a human user delegate constrained, attenuable, revocable authority to an AI agent using standard OAuth mechanisms, with no new endpoints or claims required? |
| Governed by | IETF individual Internet-Draft (OAuth-adjacent, not yet adopted by the OAuth Working Group as of this verification) | IETF individual Internet-Draft (OAuth-adjacent; not yet adopted by the OAuth Working Group as of this verification) |
| Status (issuer's words) | Expired Internet-Draft (expired 2026-04-23) | Internet-Draft, individual submission, Active |
| Version | draft-rosenberg-oauth-aauth-01 (2026-04-22) | draft-mishra-oauth-agent-grants-02 (2026-08-30) |
| Form / transport | endpoint | endpoint |
| Found at | OAuth 2.1 extension grant flow; no well-known file defined | /.well-known/oauth-authorization-server |
| Implementation | none found | prototype |
| Evidence | 5 verified | 2 verified, 1 reported |
| Primary use case | Delegate a user's authority to an agent | Delegate a user's authority to an agent |
| Last verified | 2026-10-23 (current) | 2026-10-23 (current) |
| Specification | [https://datatracker.ietf.org/doc/html/draft-rosenberg-oauth-aauth](https://datatracker.ietf.org/doc/html/draft-rosenberg-oauth-aauth) | [https://datatracker.ietf.org/doc/html/draft-mishra-oauth-agent-grants-02](https://datatracker.ietf.org/doc/html/draft-mishra-oauth-agent-grants-02) |

## When to use which

- Choose Agent Authorization Grant when your question is “How can a conversational AI agent, reached over a channel without browser redirect (phone, SMS), obtain a properly scoped OAuth access token without impersonating the user?” and you accept its maturity: status "Expired Internet-Draft (expired 2026-04-23)", implementation none found. It is no longer maintained; prefer its successor.
- Choose OAuth Profile for Delegated AI Agent Authorization when your question is “How can a human user delegate constrained, attenuable, revocable authority to an AI agent using standard OAuth mechanisms, with no new endpoints or claims required?” and you accept its maturity: status "Internet-Draft, individual submission, Active", implementation prototype.

Guidance is derived from the two records (question, status, implementation, prerequisites, pairings), not from opinion. Each record's page carries its numbered references.

## Read the full articles

- [Agent Authorization Grant](/protocols/aauth/): How can a conversational AI agent, reached over a channel without browser redirect (phone, SMS), obtain a properly scoped OAuth access token without impersonating the user?
- [OAuth Profile for Delegated AI Agent Authorization](/protocols/daap/): How can a human user delegate constrained, attenuable, revocable authority to an AI agent using standard OAuth mechanisms, with no new endpoints or claims required?

Ask the MCP server to compare any two: the compare-protocols prompt, or get on both ids. [Connect](/connect/).

[aauth.json](/data/protocols/aauth.json) · [daap.json](/data/protocols/daap.json) · [Markdown](/compare/aauth-vs-daap/index.md)