DOCUMENTATION
Quotas & rate limits
Budget at account level, not per domain or key.
What consumes a unit#
| Situation | Metering |
|---|---|
| An admitted authorized operation subject to request units | 1 unit, including cache hits and a valid lookup returning 404 |
| Invalid key, forbidden scope, validation error, OPTIONS/HEAD, 429, server failure | Not billed; abuse limits still apply |
| GET /me/usage | 0 request units; shared account/IP/global rate limits apply |
| An admitted retry | A new request and unit |
Storage and file-transfer limits are separate from request quota. See ZIP upload limits and download limits.
Headers & waiting#
X-Quota-Limit/Remaining describe period units; X-Quota-Reset is a Unix timestamp in seconds. RateLimit-Reset is rate-window seconds. On 429 honor Retry-After; request ID is in X-Request-Id and meta.requestId.
- On 429, honor Retry-After, use jitter and bound retries. Never bypass limits by switching mirrors.
- Account dashboards may update with a delay; GET /me/usage provides current usage.
- The API returns 503 if accounting or rate-limit checks are unavailable.
Captured GET /me/usage response from a local test environment. Values show usage at the time of the request.
GET /public/v1/me/usage
HTTP response
HTTP/1.1 200
ratelimit-limit: 60
ratelimit-remaining: 58
ratelimit-reset: 60
x-request-id: 2227dfcb-83b1-494c-890e-078dc5a62bb8
cache-control: no-store
content-type: application/json; charset=utf-8
{
"success": true,
"data": {
"plan": {
"code": "free",
"name": "Free",
"priceMinor": 0,
"currency": "RUB",
"periodDays": 30,
"quota": 10000,
"rateLimit": 60,
"projectLimit": 1,
"keyLimit": 2
},
"periodStart": "2026-11-13T07:56:55.835Z",
"periodEnd": "2026-12-13T07:56:55.835Z",
"used": 3,
"limit": 10000,
"remaining": 9997
},
"meta": {
"requestId": "2227dfcb-83b1-494c-890e-078dc5a62bb8",
"apiVersion": "v1"
}
}