Limits by endpoint
Response headers
Rate-limited responses, and SDK responses from endpoints that report usage, include these headers:Rate limited response
A rate-limited request returns HTTP429:
Limiter unavailable
If the rate-limit store is unavailable, payment and write requests fail closed with HTTP503 and
code SERVICE_UNAVAILABLE. Some read endpoints fall back to a smaller in-memory limit instead. A
503 here does not mean you exceeded a quota. Retry after a short delay.
Retry strategy
The SDK retries429 and 5xx responses only for read-only calls and writes protected by stable
idempotency. It never retries payment execution, protocol records, or admin mutations. Reconcile
their status before trying them again. See retry strategy for
the SDK’s retry limits and backoff.
For manual retries, wrap only read-only or explicitly idempotent operations. Never use a generic
retry wrapper around payment execution or another non-idempotent write.