Rate limits
There are no published per-key rate limits yet. Keys do not authenticate during the beta, so there is nothing to meter per key, and quoting a number here that no code enforces would only mislead the client you write against it.
Direct API access is not open during the beta. API keys created in the dashboard authenticate nothing — no request anywhere is accepted with one — and screenshots are captured from the dashboard instead.
These pages describe the capture service the dashboard talks to. Read every request below as the shape of the interface that will open, not as a call you can make today.
What bounds usage today
- Your credit balance. One completed screenshot is one credit — see Credits.
- Capture capacity. When the queue is saturated the service answers
503and the dashboard asks you to try again in a moment.
Backing off
A throttled request answers 429 with a Retry-After header in seconds. Wait at least that long, then retry with exponential backoff. That header is the only rate-limit signal the service sends today — there are no X-RateLimit-* headers to read.
HTTP/1.1 429 Too Many Requests Retry-After: 12
Limits will be published here, per API key, before direct access opens. If you are planning volume that would need them, talk to us first.