Quick answer
Stripe documents special endpoint limits as Files: 20 read + 20 write/s; Search: 20/s. These endpoint families are separate from the basic default endpoint limiter.
Verified Aug 22, 2026Official source
Current limits
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| special endpoint limitsThese endpoint families are separate from the basic default endpoint limiter. | Files: 20 read + 20 write/s; Search: 20/s | Special endpoints | StripeAug 22, 2026 |
Why does this limit matter?
Upload-heavy workflows should budget reads and writes independently.
This value is scoped to Special endpoints; a different plan, runtime, model, endpoint, region, or account can produce a different effective constraint.
What should you check?
- Tag Files read, Files write, and Search traffic separately in client metrics.
- Confirm the exact plan, model, runtime, endpoint, region, and account that serve the failing workload.
- Record the observed value, response headers or configuration, timestamp, and source without logging secrets.
Important caveats
- Concurrency and resource-specific limits can still reject requests below these rates.
- Treat the official source and live account configuration as authoritative if they differ from this verified snapshot.
HyperObserve reports the documented platform constraint. Your application, SDK, gateway, provider, region, or account can impose a lower effective limit.
Related