Cross Domain · security identity · IETF — individual submission, part of the AAuth draft family, not yet working-group adopted

AAuth Rich Resource Requests (draft-hardt-aauth-r3)

The vocabulary layer of AAuth, which replaces the scope string with the API description a provider already publishes. Instead of inventing calendar:write, a resource declares that its authorization vocabulary is urn:aauth:vocabulary:openapi and points at its OpenAPI — from then on the unit of authorization is an operationId, or an MCP tool name, or a gRPC method. Seven vocabularies are defined, one per interface style. It also adds per-call authorization, where a resource builds a content-addressed proposal containing the concrete parameters of one pending call and the human approves that call, once.

IETF — individual submission, part of the AAuth draft family, not yet working-group adoptedGoverning body
2026First published
draft-hardt-aauth-r3 (editor's copy, ...Current version
Yes — the `r3_vocabularies` map in `/...Machine-readable schema · open
0providers in the catalog

Also known as draft-hardt-aauth-r3, Rich Resource Requests, R3.

Providers that carry AAuth R3 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 R3 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.