OAuth 2.0 Protected Resource Metadata (RFC 9728)
RFC 9728 is the Standards Track specification that lets an API describe how it is protected, in a JSON document served at /.well-known/oauth-protected-resource. It carries the resource identifier, which authorization servers issue tokens for it, supported scopes, accepted bearer methods, and whether tokens must be DPoP- or certificate-bound. A WWW-Authenticate challenge can point at it with the resource_metadata parameter, so a client that gets a 401 can discover where to go without being configured in advance.
Also known as RFC 9728, Protected Resource Metadata, PRM, oauth-protected-resource.
Measured implementing OAuth 2.0 Protected Resource Metadata 4049
These providers were observed, not self-declared: they serve /.well-known/oauth-protected-resource (RFC 9728): verified names its authorization_servers, documented carries `resource` only. Read from each provider's Kin Score agent-readiness grade. The top 300 of 4049 are shown.
verified · 3966documented · 83
Providers that carry OAuth 2.0 Protected Resource Metadata 0
Read from the API Evangelist standards directory, facts verified 2026-08-24. 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.