Idempotency and Rate Limits
Request retry behavior, throttling, and idempotent operation boundaries.
Retry only when the operation and provider contract make a retry safe.
Source boundary
Source boundary: AutoCore current main 7a504f6e430c16d4fcb03ebdea3cc3fb7816df60, checked against immutable v1.0.0-rc.1 at 9edfb109f44cc80385784c694b96392cfc04e70f.
A global throttler is configured at 100 requests per 60 seconds, with narrower route limits in selected controllers. Payment callbacks and mutation services add provider/event idempotency where the source requires it.
| Check | Source-backed expectation |
|---|---|
| Scope | A 429 is a control response; do not increase limits or replay payment requests as an improvised fix. |
| Evidence | Use placeholders, timestamps, release identity, route, status, and request ID where relevant. |
| Safe action | curl -i https://api.example.invalid/api/v1/health |
| Stop condition | Unknown authorization, destructive impact, secret exposure, or conflicting evidence. |
Verification
Run the safe check, record its result, and compare the outcome with the documented contract. If the result depends on external configuration or provider availability, mark it as configuration-dependent rather than claiming a product guarantee.
curl -i https://api.example.invalid/api/v1/health
Safety boundary
Examples are non-production and use placeholders. Do not deploy, reset, force a migration, create secrets, activate providers, replay sensitive work, or expose private data from this page.