







OAuth Client ID Metadata Document
This specification defines a mechanism through which an OAuth client can identify itself to authorization servers, without prior dynamic client registration or other existing registration. This is through the usage of a URL as a client_id in an OAuth flow, where the URL refers to a document containing the necessary client metadata, enabling the authorization server to fetch the metadata about the client as needed.

OAuth Client ID Metadata Document
This specification defines a mechanism through which an OAuth client can identify itself to authorization servers, without prior dynamic client registration or other existing registration. This is through the usage of a URL as a client_id in an OAuth flow, where the URL refers to a document containing the necessary client metadata, enabling the authorization server to fetch the metadata about the client as needed.

Authenticated Transfer: Architecture Overview
Authenticated Transfer (AT) is a collection of protocol components that together provide a generic framework for interoperable social web applications, using global aggregations of interlinked, self-certifying data records. This informational document provides an overview of the entire system, as implemented in late 2025. Some of those components may be in scope as work for the IETF, while other components may not. Many components are general-purpose and may find use outside of the context of AT. The intent of this document is to provide context for how all the components can fit together for certain use cases.
Introduction - Agent Client Protocol
Get started with the Agent Client Protocol.

No silver bullet: De-identification still doesn't work - CITP Blog
Paul Ohm’s 2009 article Broken Promises of Privacy spurred a debate in legal and policy circles on the appropriate response to computer science research on re-identification techniques. In this debate, the empirical research has often been misunderstood or misrepresented. A new report by Ann Cavoukian and Daniel Castro is full of such inaccuracies, despite its claims of “setting […]
Building the world's trusted identity platform • Yoti
Our comprehensive suite of customer verification tools make it easy for businesses to be compliant and safe for people to prove who they are.

Protocol Reader - Summer of Protocols
The Protocol Reader The Protocol Reader is an 358-page book (currently only available as an epub) comprising 26 foundational essays by 31 authors from the Summer of Protocols program, carefully edited and sequenced to introduce you to the fascinating new discipline of Protocol Studies. It can serve as

OAuth Client Security in the Atmosphere · bluesky-social atproto · Discussion #3950
The following was written by the Bluesky team as an overview of OAuth client security considerations, especially for client app developers or readers of the ATProto OAuth profile specification. Set...
Exposed Persona Frontend Reveals Extensive Biometric Surveillance Stack Behind Age Verification - ID Tech
Security researchers investigating Discord’s age-verification implementation have discovered a publicly exposed frontend belonging to Persona Identities, Inc., revealing that the identity-verification vendor’s platform performs far more extensive checks than users […]

pds.js by chadtmiller.com · Tangled
An AT Protocol Personal Data Server written in JavaScript
Identity verification on Claude | Claude Help Center
Being responsible with powerful technology starts with knowing who is using it. Identity verification helps us prevent abuse, enforce our usage policies, and comply with legal obligations.

ATProto as Agent Identity Infrastructure: A Case Study for NIST's Concept Paper — Filae
How ATProto addresses NIST's four pillars of AI agent identity — identification, authorization, delegation, and logging — with concrete examples from deployed infrastructure.

OAuth Patterns - AT Protocol Docs - AT Protocol
Auth for AT Protocol application developers.
