







An implementation of a Client ID Metadata Document Service
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.

[Proposal] AT-URI for cross-service records
tl;dr non-AtprotoPersonalDataServer services might host records, let’s introduce following AT-URI syntax with optional service field to reference those non-PDS hosted data. at://tangled_knot@did:plc:user/... ^^^^^^^^^^^^ ^^^ | path can be any format | (NSID/rkey prefered, but not enforced) service name (default to "atproto_pds" when omited) In this proposal, I’m going to explain why we need cross-service reco...

How Grobid uses Crossref metadata to enrich bibliographic information - Crossref | Luca F.
Early this year Crossref and I talked about how Grobid users rely on their API, and the numbers are big: in Q1 2026 alone, GROBID clients sent more than 100 million requests to consolidate extracted bibliographic data. Crossref offers three tiers: public (anonymous, low throughput), polite (identified by email, higher throughput) and Metadata Plus (paid, for large-scale use). GROBID’s integration dated back to 2014, and it turned out it needed an update. Since 0.9.0, GROBID lets you join the polite pool or use your Metadata Plus key. Consolidation is more reliable, and it’s fairer to a shared, open service. Luis M. Montilla and I had a conversation about how Grobid uses the Crossref metadata to enrich references extracted from PDFs, that eventually become a blog post: 🔗 https://lnkd.in/egxWRAV6 And there’s a next step: for really large volumes, a local service may be more suitable than the API. On 22 October at 15:15 UTC, I’ll present biblio-glutton in the Community Highlights session of the Crossref Annual Meeting. Biblio-glutton is a local metadata search service for scholary publications using the Crossref public dump and data from other services: Pubmed, HAL, OpenAlex, etc... I built with Patrice Lopez in 2016. It provides provide lookup, structured, and unstructured metadata search. The owners of the Crossref Metadata Plus subscription can keep it in sync with regular background jobs so the data is kept up-to-date. 🔗 Annual Meeting (online, free; register for Session 2): https://lnkd.in/ew699KCw 🔗 biblio-glutton: https://lnkd.in/eR6KvmJM
CID (Content IDentifier)
Self-describing content-addressed identifiers for distributed systems

tassis/atfield-core
Framework-agnostic AT Protocol utilities for identity resolution and public record reads.

From Personal Data Server to Personal Metadata Server - Liccium
Liccium builds the fundamental infrastructure that enables creators and rightsholders to publish machine-readable declarations about their digital works that…
n0-computer/iroh-docs
Multi-dimensional key-value documents with an efficient synchronization protocol.
Evolution of AI Agent Registry Solutions: Centralized, Enterprise, and Distributed Approaches
Autonomous AI agents now operate across cloud, enterprise, and decentralized domains, creating demand for registry infrastructures that enable trustworthy discovery, capability negotiation, and identity assurance. We analyze five prominent approaches: (1) MCP Registry (centralized publication of mcp.json descriptors), (2) A2A Agent Cards (decentralized self-describing JSON capability manifests), (3) AGNTCY Agent Directory Service (IPFS Kademlia DHT content routing extended for semantic taxonomy-based content discovery, OCI artifact storage, and Sigstore-backed integrity), (4) Microsoft Entra Agent ID (enterprise SaaS directory with policy and zero-trust integration), and (5) NANDA Index AgentFacts (cryptographically verifiable, privacy-preserving fact model with credentialed assertions). Using four evaluation dimensions: security, authentication, scalability, and maintainability, we surface architectural trade-offs between centralized control, enterprise governance, and distributed resilience. We conclude with design recommendations for an emerging Internet of AI Agents requiring verifiable identity, adaptive discovery flows, and interoperable capability semantics.

How Grobid uses Crossref metadata to enrich bibliographic information - Crossref
Crossref members register around 37,000 records daily. All this metadata is openly shared with the global scholarly community through our free APIs. We receive over two billion calls to our API each month, signalling its use by hundreds of tools and services worldwide, supporting the discovery and assessment of scholarly metadata. As part of a new series in our blog, we will spotlight the diversity of tools and integrations that rely on Crossref metadata to serve the scholarly community. In this initial post, we chat to Luca Foppiano, the developer and maintainer of Grobid1, to learn about how Grobid uses Crossref metadata to improve the extraction and enrichment of bibliographic information from scholarly PDFs.

What if a PDS became more than a repository for posts? We propose using AT Protocol as a creator-controlled publication layer for declaration metadata describing digital works, making rights, provenance, and other trusted metadata independently verifiable and easier to discover.
From Personal Data Server to Personal Metadata Server
liccium.leaflet.pubJust spent a bunch of time working on the Client ID Metadata Documents internet draft to make it possible to support multiple token endpoint authentication methods — github.com/oauth-wg/draft-ietf-oauth-cli…
Document token endpoint auth methods supported by ThisIsMissEm · Pull Request #99 · oauth-wg/draft-ietf-oauth-client-id-metadata-document
github.comI've been working on an "at protocol notion". One of the things that has been holding it up has been coming to terms with the oddities of putting this data on a PDS. A document is a collection of edits, whose edits we collect will change that document pretty substantially. This is a feature