Atproto Rate Limits
AT Protocol enforces rate limits at multiple layers: content write operations use a points-based system per account, general API requests are throttled per IP, and specific sensitive operations (account creation, session creation, handle updates) have their own tighter limits. The Bluesky AppView offers generous limits for read-only access. The Relay (firehose relay) imposes per-second and daily throughput caps on repository stream consumers.
Atproto Rate Limits is the machine-readable rate-limit profile for AT Protocol on the APIs.io network, in the API Commons Rate Limits shape.
It captures 17 rate-limit definitions, measuring requests_per_5_minutes, write_points_per_hour, write_points_per_day, requests_per_day, and bytes_per_upload.
Limit state is signalled in the retryAfter response header, and an exhausted limit returns HTTP 429.
This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.
The profile also includes response codes documented for throttled.
Tagged areas include Rate Limiting, XRPC, Bluesky, and AT Protocol.
retryAfter
generated, dated 2026-06-12.
Limits
Sources
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.