Chroma Db Rate Limits
Chroma does not publish fixed numeric request-rate limits for its v2 REST API. On self-hosted (open-source) deployments, throughput is bounded only by your own hardware, and the server advertises operational limits - notably a maximum batch size - via the GET /api/v2/pre-flight-checks endpoint that clients read before writing. On Chroma Cloud, capacity is governed by usage-based metering (data written, stored, queried, and network egress) and per-plan limits such as the number of databases and team members, rather than by a documented per-minute request cap.
Chroma Db Rate Limits is the machine-readable rate-limit profile for Chroma on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 5 rate-limit definitions, measuring requests, operations, records, bytes, and databases.
The profile also includes 2 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include Vector Database, Embeddings, Vector Search, Rate Limiting, and Quotas.
Limits
Policies
Sources
- https://docs.trychroma.com/reference/chroma-reference
- https://www.trychroma.com/pricing
- https://github.com/chroma-core/chroma
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/chroma-db-rate-limits"curl "https://apis.io/api/v1/rate-limits?limit=25"Discovery needs no key. Ratings and market analysis are Pro.