What is the AT Protocol?
The AT Protocol, or atproto, is an open protocol for social apps. It defines how accounts are named, how their data is stored and signed, and how services exchange it. Bluesky is the best-known app built on it, but not the only one.
Last reviewed on November 13, 2026
What the name means
AT stands for Authenticated Transfer. Data on the network is signed by the account it belongs to, so anyone can check that it is genuine without asking the server it came from.
The AT Protocol was created by the team at Bluesky Social PBC, the company behind the Bluesky app. Its specifications are open and published at atproto.com. It is a federated protocol: it is not a blockchain and does not use one.
Bluesky is an app, atproto is the network
Bluesky is a social app. The AT Protocol is the layer underneath: it decides what an account is, and how posts, likes and follows are stored and shared. Because that layer is open, apps can work with the same accounts and the same data, and people can move between them.
Bluesky is the best-known app on the network, but not the only one: the protocol's documentation lists others, such as Tangled, Standard Reader and Smoke Signal, built on the same accounts.
The three building blocks
Identity: DIDs and handles
Every account has a DID (decentralized identifier), a permanent ID that looks like did:plc:… and never changes. It also has a handle, a readable name that is a domain name, such as alice.bsky.social. The handle can change; the DID stays. The DID leads to a small document that names the account's current server (its PDS), its handle and its public signing key.
Data: signed repositories
Each account has one repository that holds its public records: posts, likes, follows and more. The protocol's overview describes repositories as "like Git repos but for database records". Every change is signed, so a copy of a repository can be checked anywhere. Images and videos are stored alongside it on the PDS as blobs.
Services: open indexes
Repositories live on servers called PDSes. Other services collect them and build what people see: the relay gathers updates into one stream, the AppView builds timelines and threads, and feed generators and labelers add choice. Feeds, labelers and search indexes can be run by independent third parties. How Bluesky works follows a post through each of them.
Lexicons: a shared vocabulary
For apps to understand each other's data, they agree on schemas called lexicons. A lexicon describes a type of record or an API call, a bit like JSON Schema or OpenAPI.
Each lexicon has a name written as a reversed domain, its NSID: app.bsky.feed.post is a Bluesky post. Lexicons under com.atproto cover the base protocol, such as syncing repositories, and those under app.bsky cover Bluesky's social features. Whoever controls a domain controls the names under it, so anyone can define new lexicons for a new kind of app.
XRPC: how services talk
Services call each other over ordinary HTTPS, following conventions called XRPC. The path of a call is /xrpc/ followed by the NSID of its lexicon. A read is a "query", sent with HTTP GET; a write is a "procedure", sent with HTTP POST.
Going deeper. Two real endpoints: the first reads a user's timeline from the AppView, the second creates a record, such as a post, in a repository on a PDS.
GET /xrpc/app.bsky.feed.getTimeline
POST /xrpc/com.atproto.repo.createRecordWho runs what
The protocol is open: anyone can read the specifications and build on them. In March 2026, the IETF created a working group, ATP, to standardise its core: the repository format, synchronisation (the firehose), AT URIs and the requirements for systems that resolve account identifiers.
Some shared pieces are still run by a few operators. The PLC directory resolves did:plc identifiers for the whole network. Bluesky Social PBC developed it in 2022 and has operated it. In September 2025, Bluesky announced that it was supporting an independent organisation, to be formed as a Swiss association, to operate the directory. The directory's own site now says the PLC Organization was founded in 2026 as a neutral steward of the system.
Going deeper
The protocol's overview and its glossary are the best next reads, then the specifications for the details.
How Bluesky.bot uses this
Bluesky.bot builds on the identity layer of the AT Protocol. A name.bluesky.bot handle is a domain name that answers with the bot's DID, and Bluesky.bot checks in both directions that the network agrees. How a bot's handle is checked.
Frequently asked questions
- Is the AT Protocol a blockchain?
- No. The AT Protocol is a federated protocol: it does not use a blockchain. Data is signed with ordinary cryptographic keys and served over HTTPS.
- Is atproto the same as ActivityPub or Mastodon?
- No. Mastodon uses ActivityPub, and Bluesky uses the AT Protocol: they are different protocols. The AT Protocol team built a separate one largely for account portability and scale, so that an account can change servers and keep its identity.
- Who controls the AT Protocol?
- Its specifications are open and published at atproto.com, and an IETF working group created in March 2026 is standardising its core. Bluesky Social PBC created the protocol and runs much of today's infrastructure, but anyone can run a PDS, a relay, an AppView, a feed or a labeler.