







General planning and documentation repository for the OCapN protocol suite for distributed networked objects - ocapn/ocapn
ocapn/draft-specifications/CapTP Specification.md at main · ocapn/ocapn
General planning and documentation repository for the OCapN protocol suite for distributed networked objects - ocapn/ocapn
ocapn/draft-specifications/Netlayers.md at main · ocapn/ocapn
General planning and documentation repository for the OCapN protocol suite for distributed networked objects - ocapn/ocapn
OCapN Pre-standardization Group
We are a group focused on converging and working on pre-standardization of OCapN. OCapN stands for "Object Capability Network" and provides:
Introducing OCapN, interoperable capabilities over the network — Spritely Institute
OCapN (Object Capability Network) is a new protocol to add support for secure, seamless, and distributed (often peer-to-peer) communication for networked applications.

How the Specifications Relate
OpenAPI, AsyncAPI, JSON Schema, Arazzo, Overlay, Spectral, APIs.json, MCP, A2A, GraphQL, gRPC, JSON-RPC, OAuth 2.0, OpenID Connect, Protected Resource Metadata, Dynamic Client Registration, Agent Skills, the AI Catalog, the RFC 9727 API Catalog, UCP and ORD — read from their published schemas, mapped by what each one points at, which property does which job, and how much vocabulary they share.

Capability Trees: A Protocol-Level Extension of Object Capabilities, Draft 3
This draft incorporates feedback from Brooklyn Zelenka (@expede.wtf), Daniel Holmgren (@dholms.at), and Zicklag (@zicklag.dev), and addresses questions raised in the ATProto Private Data Working Group. Draft 2 remains available for transparency.
Capability Trees: A Protocol-Level Extension of Object Capabilities, Draft 2
This draft addresses questions and feedback from the ATProto community, in particular from Zicklag (@zicklag.dev) and Brooklyn Zelenka (@expede.wtf). Draft 1 remains available for transparency.
ATsense: ATproto-style Federation for Open Sensor Networks (Draft)
ATsense: ATproto-style Federation for Open Sensor Networks (Draft) · GitHub

Capability Trees: A Protocol-Level Extension of Object Capabilities, Draft 4
This draft incorporates feedback from Brooklyn Zelenka (@expede.wtf) and Daniel Holmgren (@dholms.at), and developments in the ATProto Private Data Working Group. Previous drafts remain available for transparency.
Introduction to AT Protocol
Walkthrough of the various parts and concepts in Bluesky's AT Protocol (ATProto), the types of servers involved and how it all fits together

Introduction to AT Protocol
Walkthrough of the various parts and concepts in Bluesky's AT Protocol (ATProto), the types of servers involved and how it all fits together

atproto-crates — AT Protocol building blocks for Rust
A Rust workspace of eighteen crates for AT Protocol: content addressing, DID and handle resolution, repositories and Merkle Search Trees, OAuth with DPoP, XRPC services, and event streaming.
From ZK-first to AT Protocol — our path to DDS | Agora Citizen Network
We've been building Agora — a platform for public deliberation using Polis-style clustering — for a while now. Along the way, we've written about what we think about Nostr, AT Protocol, Polis, Community Notes, and protocol interoperability. Those posts are somewhat outdated now. This one describes w...
| Eden-Fidelis
About RO-Crate | Research Object Crate (RO-Crate)

Lea: A Social App for Researchers - ATmosphereConf 2026
Chive | Decentralized Eprint Service
What It Means for Universities to Run Their Own PDS: The Potential of DID as Academic Infrastructure - Nightflight

Standard.site - One schema. Every platform.
pub search

The AT Protocol Harkens An Old Web Ethos
at-store | Apps on the Atmosphere
Open Evnt Documentation
Lexicon Garden - ATProtocol Lexicon Browser

Standard.site Validator