● Covered by 1 source · 1 reportMedium impact1 neutral
Bluesky Launches Protocol Services and Jetstream v2 for AT Protocol Developers
Key points
- Bluesky Protocol Services launched for AT Protocol infrastructure.
- New website centralizes developer documentation and service contracts.
- Jetstream v2 adds Network Replay for historical data access.
- API token now required for archive requests in Jetstream v2.
Introducing Bluesky Protocol Services
Bluesky has launched "Bluesky Protocol Services," a new brand and dedicated website for the public infrastructure it operates on the AT Protocol network. This initiative aims to improve developer experience by organizing documentation and clarifying service contracts for Bluesky-provided infrastructure, including Jetstream instances, relays, and AT Protocol API endpoints. The new site replaces the old docs.bsky.app.
Jetstream v2 Release
A key release accompanying the new services is Jetstream v2. Jetstream is designed for developers to consume network data at scale, delivering filtered data as JSON over a WebSocket. The previous version lacked the ability to provide historical data, requiring developers to backfill repositories manually.
New Historical Data Capabilities
Jetstream v2 addresses this limitation by adding Network Replay and snapshot features. Network Replay allows developers to catch up from any point in the past and transition to the live data stream without interruption. This is achieved by POSTing filters to planSnapshot, downloading sealed segments via HTTP, and then connecting to the live WebSocket. Additionally, developers can snapshot the network for a point-in-time copy of the archive over HTTP, without a live tail.
Impact on Developers
These new capabilities enable more sophisticated server-side data slicing without local backfilling. Developers can now spin up applications, perform analyses over extended periods, or recover from downtime using the same JSON format as the live data stream. This enhances the flexibility and utility of the AT Protocol for developers building on the network.
Authentication for Archive Access
To manage bandwidth and ensure service reliability, Bluesky now requires an API token for requests to access these historical archives. The live data stream remains open and unauthenticated, with no plans to introduce authentication requirements for it.
✨ This summary was generated by AI from the outlets' reporting listed below. It is not independently verified and may contain errors — check the original sources. How BrevFeed works →
The daily brief
One email each morning: the day's tech stories, clustered across outlets and summarized. No account needed.
One email a day. Unsubscribe in one click, any time.
Today's brief
Spend a few minutes, get the whole day. Every topic's top stories in one hands-free rundown — listen, watch, or read the transcript.
▶ Play today's brief
New every morning, and the back catalogue is archived by date.
Primary sources
GitHub bluesky-social/atproto GitHub bluesky-social/cookbook GitHub bluesky-social/deploy-recipes GitHub bluesky-social/jetstream npm @atproto/lexReporting from
Bluesky introduced "Bluesky Protocol Services," a new brand and website to centralize documentation and clarify service contracts for its AT Protocol infrastructure. Alongside this, Jetstream v2 was released, adding Network Replay and snapshot capabilities to allow developers to access historical network data, addressing a previous limitation of the service.