This is not our API. This repository is an independent, third-party profile of a company's publicly available API surface, maintained by API Evangelist. API Evangelist does not operate, host, resell, or support this company's APIs, and is not affiliated with or endorsed by the company unless stated on the profile.
Where the information came from. Everything here is assembled from material a member of the public can reach with a browser and no credentials — the company's own website, developer portal and documentation, the specifications it publishes for public use (OpenAPI, AsyncAPI, JSON Schema,
apis.json,llms.txtand similar), its public repositories, and its public status, pricing and changelog pages. Nothing here is obtained by breaching a system, defeating an access control, or using credentials of any kind.The rating is an independent assessment. The Kin Score and Agent Readiness rating are independently calculated scores of a company's public API artifacts, produced by API Evangelist against a published rubric. They are not certifications, endorsements, security assessments, or audits, and they score published artifacts — not the quality, safety, or security of the software.
Corrections, re-scores, and removal are free. No partnership, contract, or purchase is required, and you do not need to justify the request.
- Something wrong? Open an issue on this repository, or email info@apievangelist.com.
- Published something new? Ask for a re-score and we will re-run the rating.
- Want the listing taken down? Say so and we will honor it. The profile is reduced to your company name, a factual description, and a link to your own site, and the company is recorded as unrated — never scored zero for having asked.
Response times. Acknowledgement within one business day; removal or restriction within two business days; corrections and re-scores within five business days.
Not from the company, and here with a question? You are welcome here — we would rather be the front line and point you the right way than have a good report go nowhere. What this repository can answer is narrow, though, so it is worth knowing who you are actually looking for:
- A question about how the API works, an account, billing, or a bug in the service — that is the company's own support, not us. We profile this API; we do not operate it and cannot see your account.
- A bug in an open-source project we only catalog — file it on that project's own repository. This has happened with a real and correct bug report that reached us instead of the people who could fix it, which helped nobody.
- Anything about this listing itself — the description, the tags, the rating, a missing or wrong artifact — is ours. Open an issue here.
- Not sure, or something general about API Evangelist or APIs.io — open an issue on the APIs.io Inbox and we will route it.
This repository contains no software, and we will never ask you to download anything. There is no build, release, installer, or binary here — only text and machine-readable API descriptions, so there is nothing here that can be "corrupt" or need "repairing". Any issue, comment, or email claiming otherwise and offering a download link is not from us and is hostile. Do not follow the link; it is a lure. Report it to GitHub and, if you like, tell us at info@apievangelist.com so we can take it down.
On a security or compliance team? Email info@apievangelist.com with security in the subject line and you will get a person, not a form. We will tell you exactly which public URLs this profile was built from so your team can see the same surface we did, and we will take the listing down on request while you work through it.
Full detail: Where this data comes from
The AT Protocol (atproto) is an open, federated networking protocol for social applications, originally developed by Bluesky Social PBC and the Bluesky team. It defines a decentralized architecture where user identity and data are portable across providers, anchored in DIDs, signed records, and content-addressed storage. The protocol is composed of independently operable services — Personal Data Servers (PDS), Relays (firehose aggregators), and AppViews (read-side indexers) — that communicate using XRPC and exchange records described by Lexicon schemas. Bluesky (bsky.app) is the reference application built on AT Protocol, but the protocol is designed for any social or social-adjacent application that wants user-owned identity, portable data, and an open federation model. Official and community SDKs exist for TypeScript, Go, Python, Rust, Dart, Swift, C#/.NET, Ruby, PHP, and more, and the full lexicon, network topology, and reference implementations are open source.
APIs.json: https://raw.githubusercontent.com/api-evangelist/at-protocol/refs/heads/main/apis.yml
- Type: Index
- Position: Provider
- Access: Public
- AT Protocol
- atproto
- Bluesky
- Federation
- Decentralized Social
- Social Networking
- DID
- Lexicon
- XRPC
- PDS
- Relay
- AppView
- Open Protocol
- Created: 2026-05-23
- Modified: 2026-05-29
XRPC is the AT Protocol's HTTP-based remote procedure call layer. All protocol interactions — querying records, writing records, subscribing to streams, resolving identity, moderating content — are exposed as XRPC methods defined in Lexicon schemas. PDS, Relay, and AppView services all speak XRPC, so the same client library can be pointed at different network roles. The HTTP surface uses /xrpc/{nsid} paths and JSON request/response bodies (with optional CBOR for record content).
- Human URL: https://atproto.com/specs/xrpc
- Base URL:
https://atproto.com/xrpc
- XRPC
- RPC
- HTTP
- JSON
- Protocol Surface
- Specification
- Documentation
- GitHub Organization
- Postman Collection — Postman Collection 2.1
- Open Collection — Open Collection 1.0
Lexicon is the schema definition language for AT Protocol. Every record type, XRPC method, and event subscription on the network is described by a Lexicon document, which acts as both contract and code generation source for client libraries. Bluesky publishes the app.bsky.* and com.atproto.* lexicons that power the reference Bluesky application; third parties define their own NSIDs to ship independent applications on the same network.
- Human URL: https://atproto.com/guides/lexicon
- Base URL:
https://atproto.com/lexicons
- Lexicon
- Schema
- NSID
- Record Types
- Documentation
- Specification
- Repository
- Postman Collection — Postman Collection 2.1
- Open Collection — Open Collection 1.0
The PDS hosts a user's repository of signed records and exposes the com.atproto.* XRPC methods for account creation, authentication, record CRUD, blob upload, and repository sync. A PDS is the home server for an actor; users can migrate their account (and full record history) between PDS hosts while keeping the same DID.
- Human URL: https://atproto.com/guides/self-hosting
- Base URL:
https://atproto.com/xrpc/com.atproto
- PDS
- Personal Data Server
- Repository
- Sync
- Self-Hosting
- Documentation
- Specification
- Reference
- Postman Collection — Postman Collection 2.1
- Open Collection — Open Collection 1.0
The Relay aggregates the com.atproto.sync.subscribeRepos firehose across PDS hosts and re-broadcasts the combined event stream over WebSocket. AppViews and indexers subscribe to a Relay to get a near-real-time view of every public record written on the network without polling individual PDS instances.
- Human URL: https://atproto.com/guides/glossary
- Base URL:
wss://bsky.network
- Relay
- Firehose
- WebSocket
- Streaming
- Sync
- Specification
- Reference
- AsyncAPI — AsyncAPI Specification
- Postman Collection — Postman Collection 2.1
- Open Collection — Open Collection 1.0
The Bluesky AppView indexes the firehose and exposes the app.bsky.* XRPC methods that the Bluesky client (and any compatible client) uses to render timelines, threads, profiles, notifications, search, and graph data. It is the reference AppView for the app.bsky lexicon family and the primary read API for Bluesky applications.
- Human URL: https://docs.bsky.app/
- Base URL:
https://public.api.bsky.app/xrpc
- AppView
- Bluesky
- Timeline
- Feed
- Graph
- Notifications
- Documentation
- API Reference
- Lexicons
- Postman Collection — Postman Collection 2.1
- Open Collection — Open Collection 1.0
Identity in AT Protocol is anchored in DIDs (did:plc or did:web), with human-readable handles resolved through DNS TXT records or well-known HTTP endpoints. The protocol specifies how DIDs map to PDS endpoints, signing keys, and rotation, allowing users to keep a stable identity while changing handles or migrating providers.
- Human URL: https://atproto.com/specs/did
- Base URL:
https://plc.directory
- Identity
- DID
- did:plc
- Handles
- DNS
- Specification
- Specification
- Service
- Postman Collection — Postman Collection 2.1
- Open Collection — Open Collection 1.0
- Website
- Documentation
- Specifications
- S D Ks
- GitHub Organization
- Reference Implementation
- Go Implementation
- Bluesky
- Bluesky Docs
- Blog
- Cookbook
FN: Kin Lane Email: kin@apievangelist.com