Docs / Rate limits and fair use
Rate limits and fair use
Free (beta) keys: 1,000 requests per month and 10 per minute, for non-commercial use. One key per verified email. A 429 answer says which limit was reached and when to try again. Attribution is required ("Data from RecallDB" with a link to https://recalldb.app). There is no bulk export.
Response headers
Every keyed response includes:
| Header | Meaning |
|---|---|
X-RateLimit-Limit | Requests allowed this month (1,000 on the free tier). |
X-RateLimit-Remaining | Requests left this month. |
X-RateLimit-Reset | When the month's count resets: Unix time, the 1st of next month, UTC. |
X-RateLimit-Policy | The monthly quota and the per-minute burst limit, for example 1000;w=2592000, 10;w=60. |
Retry-After | On a 429: seconds to wait. |
Fair use
We watch for patterns that look like bulk copying: asking for record numbers in order, sustained bursts at machine speed (fast batches alone are fine), a very large number of different records in one day, or several keys with similar use from one network. A key that does this gets a warning in its responses, then a slower limit (3 requests a minute), then a suspension. Every step is logged with its reason. A suspended key's error names support@recalldb.app; write with your key id and we will look at it.