Chroma Rate Limits
Chroma Cloud is serverless and meters Write / Storage / Query / Network rather than capping requests per second. Public documentation does not publish a numeric per-second or per-minute API rate-limit policy; tenants that exceed configured spend or per-database scaling envelopes are paused rather than throttled. The open-source Chroma server (self-hosted) has no built-in rate limiter — limits are bounded by the underlying host.
Chroma Rate Limits is the machine-readable rate-limit profile for Chroma on the APIs.io network, in the API Commons Rate Limits shape.
It captures 2 rate-limit definitions, measuring varies.
An exhausted limit returns HTTP 429.
This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.
The profile also includes 3 backoff/retry policies defined and response codes documented for throttled, serverError, and serviceUnavailable.
Tagged areas include AI, Vector Database, Retrieval, Serverless, and Rate Limiting.
generated, dated 2026-05-05.
Limits
Policies
Sources
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.