Rate Limits
SW4P applies request limits to protect shared settlement infrastructure. Limits vary by route family, key tier, and wallet activity.
Response Headers
When a route is rate-limited through the shared API-key limiter, responses may include:
| Header | Meaning |
|---|---|
X-RateLimit-Limit | Window capacity |
X-RateLimit-Remaining | Remaining requests in the current window |
X-RateLimit-Reset | Window reset time |
Retry-After | Seconds to wait before retrying |
429 Response
json
{
"error": "RATE_LIMITED",
"message": "Too many requests"
}
Retry Rules
- Retry
429only afterRetry-Afterwhen present. - Use idempotency keys for transfer-style writes so client retries do not create duplicate settlement attempts.
- Avoid retry loops on wallet-signature errors. Request a fresh signature or permit when the backend reports nonce, deadline, or signature validation failures.
Current Tier Guide
| Tier | Intended use |
|---|---|
| Free | local development and low-volume pilots |
| Pro | production integrations with moderate steady traffic |
| Enterprise | custom limits and operator support |