Bluesky
API for the Bluesky decentralized social network built on the AT Protocol.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Bluesky the way a machine reads it — 35 machine-readable artifacts across 24 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Bluesky scores 55.1/100 (developing), with a separate agent-readiness read of 54/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
How we profile Bluesky
Each block below is one kind of artifact we hold for Bluesky. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 24
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Bluesky Jetstream
Jetstream is a simplified JSON event stream for the AT Protocol that converts CBOR-encoded MST blocks from the firehose into JSON objects over WebSocket connections, making it e...
Bluesky Actor Profiles API
Operations for managing user profiles, preferences, and actor information.
Bluesky Administration API
Administrative operations for managing accounts and invites.
Bluesky Chat Actors API
Operations for managing chat actor settings and declarations.
Bluesky Chat Moderation API
Operations for moderating chat content.
Bluesky Content Labels API
Operations for managing content labelers and label subscriptions.
Bluesky Conversations API
Operations for managing direct message conversations.
Bluesky Feeds API
Operations for managing feeds, posts, likes, and reposts.
Bluesky Identity API
Operations for identity management and DID resolution.
Bluesky Labels API
Operations for content labeling and moderation.
Bluesky Moderation API
Operations for content moderation reporting.
Bluesky Notifications API
Operations for managing user notifications.
Bluesky Ozone Communication API
Ozone moderation tool communication operations.
Bluesky Ozone Moderation API
Ozone moderation tool operations.
Bluesky Ozone Server API
Ozone server configuration operations.
Bluesky Ozone Sets API
Ozone set management operations.
Bluesky Ozone Settings API
Ozone settings management operations.
Bluesky Ozone Signatures API
Ozone signature and threat analysis operations.
Bluesky Ozone Team API
Ozone team member management operations.
Bluesky Repository API
Operations for managing AT Protocol repositories.
Bluesky Server API
Operations for server management and authentication.
Bluesky Social Graph API
Operations for managing follows, followers, blocks, mutes, and lists.
Bluesky Sync API
Operations for repository synchronization.
Bluesky Video API
Operations for video upload and processing.
Scroll within the panel for all 24 ·
Open Collections 2
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Bluesky Social API
OPEN COLLECTIONBluesky Bruno Collection
OPEN COLLECTIONPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Bluesky Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Bluesky Finops
FINOPSEvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Bluesky / AT Protocol Event Streams
AsyncAPI definition for the public event streams of the Bluesky network and the underlying AT Protocol. Three streams are documented: * **`com.atproto.sync.subscribeRepos`** - t...
ASYNCAPISpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Bluesky API Rules
SPECTRALSecurity Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Bluesky — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 1
Portal, sign-up, and the first successful call
Documentation 4
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 6
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 2
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 6
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/bluesky · machine-readable index on apis.io