# Agent Authorization Envelope AAE

[3 · Permit](/category/permit/)
Candidate · auto-drafted, unreviewed · confidence 60%

| Agent Authorization Envelope |
| --- |
| Category | [Permit](/category/permit/) |
| Governed by | Individual Internet-Draft submitted to the IETF datatracker by a single author; not adopted by a working group per the page. |
| Status | Individual Internet-Draft |
| Phase | draft |
| Implementation | unknown |
| Adoption | unmeasured |
| Version | Individual Internet-Draft (May 2026) (2026-05-21) |
| Specification | [https://insights.bostonidentity.com/research/ietf-datatracker-2026-05-21-agent-authorization-envelope-aae](https://insights.bostonidentity.com/research/ietf-datatracker-2026-05-21-agent-authorization-envelope-aae) |
| Found at | Envelope presented by the agent to the relying party; no discovery path is described. The optional revocation endpoint is named inside the envelope. |
| Last checked | 2026-10-19 |
| Freshness | current · checked 2026-10-19 |
| Solves | Delegate a user's authority to an agent, Prove an agent's identity, Audit what an agent did |

Agent Authorization Envelope (AAE) is an agentic-web standard (document format) at step 3, Permit, governed by Individual Internet-Draft submitted to the IETF datatracker by a single author; its own status is "Individual Internet-Draft" (draft). It answers: How can a relying party verify offline, without calling the issuer, that an agent holds a mandate with limits, an expiry and a bounded delegation chain? Adoption is unmeasured, last verified 2026-10-19.

[Permit](/category/permit/) The Agent Authorization Envelope (AAE) is an individual IETF Internet-Draft by Lars Kersten Kroehl of CryptoKRI GmbH. It defines a JWS-secured W3C Verifiable Credential carrying a mandate, constraints and a validity block for an agent acting under delegated authority. Relying parties run nine ordered checks, including proof of key possession, revocation and delegation-chain narrowing, and refuse when a required constraint or revocation status cannot be checked. Delegated envelopes may only narrow the parent's actions, caps, allowlists and validity window.

## Discovery and probe

Envelope presented by the agent to the relying party; no discovery path is described. The optional revocation endpoint is named inside the envelope.

```
NONE
parse:
on absent: No site-level signal to observe; support is only visible when an agent presents an envelope.
```

Not probed live: no-fixed-path. candidate record; probe rule pending

## History
- 2026-10-19 — auto-drafted candidate from exa (https://insights.bostonidentity.com/research/ietf-datatracker-2026-05-21-agent-authorization-envelope-aae)

## Instances

No instances recorded yet.

## See also

## References

- The AAE is a W3C Verifiable Credential signed as a compact JWS (EdDSA/Ed25519) with mandatory mandate, constraints and validity blocks; the key is named by a DID URL. — [https://insights.bostonidentity.com/research/ietf-datatracker-2026-05-21-agent-authorization-envelope-aae](https://insights.bostonidentity.com/research/ietf-datatracker-2026-05-21-agent-authorization-envelope-aae) (2026-05-21) REPORTED
- A relying party MUST reject an AAE if any required constraint is unrecognized or cannot be evaluated; delegated envelopes may only narrow the parent's grant, with a maximum delegation depth. — [https://insights.bostonidentity.com/research/ietf-datatracker-2026-05-21-agent-authorization-envelope-aae](https://insights.bostonidentity.com/research/ietf-datatracker-2026-05-21-agent-authorization-envelope-aae) (2026-05-21) REPORTED

[JSON](/data/protocols/agent-authorization-envelope.json) · [Markdown](/protocols/agent-authorization-envelope/index.md)