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.
Limits
Sources
- openapi/decart-api-openapi-original.json
- https://docs.platform.decart.ai/getting-started/client-tokens
- https://docs.platform.decart.ai/models/realtime/streaming-best-practices
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for rate limits
4 MCP tools reach this
find_rate_limitsBrowse and filter every rate limit in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/rate-limits/decart-rate-limits"curl "https://apis.io/api/v1/rate-limits?limit=25"Discovery needs no key. Ratings and market analysis are Pro.