Decart · Rate Limits

Decart Rate Limits

Decart does not publish per-second request rate limits. The throttling contract it does expose is a concurrency quota on realtime sessions, readable at runtime through GET /v1/realtime/quota, which returns the account limit, the currently active session count, and the remaining headroom. Client tokens can further constrain a single session with constraints.realtime.maxSessionDuration, and uploaded files carry a TTL. Values are account-specific and are not published as fixed numbers, so this catalog records the mechanism rather than fabricated limits.

Decart Rate Limits is the machine-readable rate-limit profile for Decart on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 5 rate-limit definitions, measuring concurrent_sessions, models, origins, and seconds.

The profile also includes response codes documented for validation, unauthenticated, and forbidden.

Tagged areas include Rate Limiting, Real Time, and Artificial Intelligence.

5 Limits
Rate LimitingReal TimeArtificial Intelligence

Limits

Concurrent realtime sessions account
concurrent_sessions · concurrent
-1
Client token allowedModels entries token
models · request
20
Client token allowedOrigins entries token
origins · request
20
Client token default lifetime token
seconds · token
60
Uploaded file TTL file
seconds · file
2592000

Sources