Local prototype · simulated data
Rate limits
Limits protect the service and keep costs predictable. Every response reports where you stand.
Headers
| Header | Meaning |
|---|---|
X-RateLimit-Limit | Requests allowed in the current window. |
X-RateLimit-Remaining | Requests left in the window. |
X-RateLimit-Reset | Unix time (seconds) when the window resets. |
Retry-After | On 429 only: seconds to wait. |
Limits in the local prototype
| Scope | Limit |
|---|---|
| Per API key | 600 / minute |
| Demo endpoints, per client IP | 30 / minute |
| Waitlist, per client IP | 10 / hour |
| Waitlist, per email address | 3 / day |
Planned Limits for a hosted service and per-plan allowances will be published with pricing.
When you are limited
{
"error": {
"type": "rate_limited",
"code": "rate_limit_exceeded",
"message": "Too many requests. Try again shortly.",
"request_id": "req_0000000000000000docs",
"doc_url": "https://docs.example.com/errors#rate_limit_exceeded"
}
}
Wait for Retry-After seconds (here: 60), then retry. In an autocomplete UI, simply skip suggestions until the window resets; the shopper can keep typing.