Chroma

Chroma (Chroma DB) is an open-source AI-native embedding database designed to make it easy to build LLM applications by providing storage, retrieval, and management for vector embeddings, full-text search, regex search, and multi-modal retrieval (text, image, audio). Distributed under the Apache 2.0 license, Chroma can be self-hosted (single-node Python or distributed Rust-based deployment) or consumed via Chroma Cloud, a managed serverless vector database service offering usage-based pricing. Chroma is the open-source data infrastructure for AI agents and RAG (Retrieval-Augmented Generation) applications, with first-party SDKs for Python and JavaScript/TypeScript and integrations with leading embedding providers (OpenAI, Cohere, Hugging Face, sentence-transformers).

Chroma publishes 9 API contracts indexed on the APIs.io network, including System API, Authentication API, Collection API, and 6 more. Tagged areas include Artificial Intelligence, AI-native, Apache 2.0, Cloud, and Embeddings.

The Chroma catalog on APIs.io includes 1 JSON-LD context and 1 Spectral governance ruleset.

Chroma’s developer surface includes authentication, documentation, developer portal, pricing, engineering blog, and 26 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

58.5/100 strong ▬ flat Agent 40/100 agent ready Front door AI 5/6 prominent Heartbeat 72/100 slowing saas · Apache License 2.0 Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

AccessPaid

1 published contract 1 MCP Servers 10 Features 8 Use Cases

Artificial Intelligence AI-native Apache 2.0 Cloud Embeddings Hybrid Search JavaScript LLM Machine Learning Multi-Modal Open Source Python RAG Retrieval SDK Search Serverless TypeScript Vector Search Database

What this lets a business do 2

Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →

AI Model Services

AE-110

CollectionRecord

POST /api/v2/tenants/{tenant}/databases/{database}/collections/{collection_id}/query POST /api/v2/tenants/{tenant}/databases/{database}/collections/{collection_id}/search POST /api/v2/tenants/{tenant}/databases/{database}/collections

SaaS Tenant Management

BC-4230

Tenant

POST /api/v2/tenants

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 58.5/100 · strong

Contract Quality 10.0 / 19

Developer Ergonomics 7.0 / 15

Access Clarity 11.3 / 15

Operational Transparency 3.6 / 10

Contract Governance 0.9 / 9

Discoverability 5.0 / 8

Regulatory Posture 4.4 / 15

Create-or-Update Ergonomics 7.2 / 10

Agent readiness — 40/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 0 / 6

MCP Server 12 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 7 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 0 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the AI & Biometrics regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/chroma/"><img src="https://apis.io/badge/chroma/card.svg" alt="Chroma on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document
Delegated User Identity +6 pts — a served discovery document listing authorization_code in grant_types_supported (served), else an oauth2 authorizationCode flow or openIdConnect declared in an OpenAPI (documented)
Typed Event Surface +6 pts — AsyncAPI document, OR webhooks/callbacks objects in the as-published OpenAPI, OR common[].type includes Webhooks
Documented Reversibility +6 pts — a reversal operation in the contract, graded up when a window is documented too

7 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Quality scores 53.5 — up to +11.6 composite points
Contract Governance scores 9.8 — up to +10.8 composite points
Developer Ergonomics scores 46.4 — up to +10.7 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/chroma/apis.yml: open an issue on github.com/api-evangelist/chroma to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
Retrieval, Vector and RAG	covered	34.0	-	-
Stripe App Marketplace and Partner Ecosystem (builders on Stripe)	covered	34.0	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 2

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

Model Context Protocol (MCP)

measured — observed by APIs.io (verified)

OpenAPI

measured — observed by APIs.io (published)

APIs 9

Individual APIs this provider publishes, each with its own machine-readable definition.

Chroma Python Client

The Chroma Python Client is a first-party SDK for interacting with both self-hosted Chroma servers and Chroma Cloud. It provides a simple, developer-friendly interface with a co...

Chroma JavaScript Client

The Chroma JavaScript and TypeScript Client is a first-party SDK for interacting with Chroma from JavaScript or TypeScript applications. The v3 rewrite focused on reducing bundl...

Chroma System API

System-level endpoints for health checks, version information, and server diagnostics.

Chroma Authentication API

The Authentication API from Chroma — 1 operation(s) for authentication.

Chroma Collection API

The Collection API from Chroma — 7 operation(s) for collection.

Chroma Database API

The Database API from Chroma — 3 operation(s) for database.

Chroma Function API

The Function API from Chroma — 4 operation(s) for function.

Chroma Record API

The Record API from Chroma — 11 operation(s) for record.

Chroma Tenant API

Scroll for all 9

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

Chroma MCP Server

Remote MCP server at mcp.trychroma.com over HTTP; 3 tools listed.

MCP SERVER

Chroma API pricing

Prices published by Chroma, read 2026-10-07 from docs.trychroma.com/cloud/pricing.

Plan	Price
Writes	$2.50 per logical GiB written
Forking	$0.03 per fork request
Reads - queried	$0.0075 per TiB queried
Reads - returned	$0.09 per GiB returned
Storage	$0.33 per GiB per month
Sync - data processed	$0.04 per GiB processed
Sync - document page extracted	$0.01 per document page extracted
Sync - page scraped	$0.01 per page scraped

All 9 plans, limits and sources →

Rate limits

Cloud usage envelope: usage-bounded — Write / Storage / Query / Network are metered, not capped per-second varies
Self-hosted server: no built-in rate limit — bounded by host CPU / RAM and any front-proxy throttling varies

Compiled by API Evangelist, not yet checked against Chroma's documentation. Rate-limit details →

Billed by: logical gib written · FinOps profile →

Pricing Plans 1

Published pricing tiers and plan structures.

Chroma Plans Pricing

9 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Chroma Rate Limits

2 limits

RATE LIMITS

Service Levels 1

Uptime the provider promises or reports, as SLA4OAI. Read from its own pages; APIs.io runs no monitors.

Chroma

SLA

FinOps 1

Cost, billing, and metering signals for API financial operations.

Chroma Finops

FINOPS

Features 10

Notable capabilities this provider offers.

Document and Metadata Storage

Vector Similarity Search (Dense, Sparse, Hybrid)

Full-Text and Regex Search

Metadata Filtering

Multi-Modal Retrieval (Text, Image, Audio)

Automatic Tokenization and Embedding

Collection Management

Embedding Function Plugins

Self-Hosted and Cloud Deployments

Apache 2.0 Open Source License

Scroll for all 10

Semantic Vocabularies 1

JSON-LD contexts and semantic vocabularies used across these APIs.

Chroma Context

0 classes · 6 properties

JSON-LD

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Chroma — jsonschema rules

6 rules · 4 warnings 2 info

SPECTRAL

JSON Schema 2

Standalone JSON Schema definitions for this provider's data models.

Chroma Collection

5 properties

JSON SCHEMA

Chroma Record

5 properties

JSON SCHEMA

Security Posture 4

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Chroma Authentication

apiKey/http · 3 schemes

SECURITY

Chroma Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Chroma Vulnerability Disclosure

no policy recorded

SECURITY

Chroma Trust Center

SOC 2, ISO 27001

SECURITY

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Chroma Agentic Access

25 operations · 11 acting · 1 human-in-the-loop

25 operations · 11 acting

AGENTIC

Use Cases 8

What developers build with this provider.

RAG (Retrieval Augmented Generation)

Semantic Search

AI Agent Memory

Code Search (AST-Aware Chunking)

Recommendation Systems

Multi-Modal Search (Text + Images)

Question Answering Systems

Knowledge Base Querying

Scroll for all 8

Resources

Get Started 2

Portal, sign-up, and the first successful call

Portal

Portal

Login

Documentation 3

Reference material describing how the API behaves

Documentation

Documentation

JSONSchema

JSONSchema

JSONSchema

JSONSchema

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

AgenticAccess

LlmsText

LlmsText

Design & Contract 2

Pagination, idempotency, versioning, errors, and events

JSONLDContext

JSONLDContext

Spectral

Spectral

Build 3

SDKs, sample code, and the tooling you integrate with

PostmanWorkspace

PostmanWorkspace

GitHubOrg

GitHubOrg

SourceCode

SourceCode

Access & Security 4

Authentication, authorization, and security posture

TrustCenter

TrustCenter

VulnerabilityDisclosure

VulnerabilityDisclosure

DomainSecurity

DomainSecurity

Authentication

Authentication

Operate 4

Status, limits, changes, and where to get help

RateLimits

IssueTracker

Releases

Discord

Commercial 6

Pricing, plans, and the legal terms of use

FinOps

Plans

Pricing

License

TermsOfService

PrivacyPolicy

Company 4

The organization behind the API

LinkedIn

Website

Website

Blog

Blog

Twitter

Twitter

Other 3

Properties that don't map to a standard resource type

CapabilityMap

CapabilityMap

Source (apis.yml)

aid: chroma
name: Chroma
kind: company
description: Chroma (Chroma DB) is an open-source AI-native embedding database designed to make it easy to build LLM applications
  by providing storage, retrieval, and management for vector embeddings, full-text search, regex search, and multi-modal retrieval
  (text, image, audio). Distributed under the Apache 2.0 license, Chroma can be self-hosted (single-node Python or distributed
  Rust-based deployment) or consumed via Chroma Cloud, a managed serverless vector database service offering usage-based pricing.
  Chroma is the open-source data infrastructure for AI agents and RAG (Retrieval-Augmented Generation) applications, with
  first-party SDKs for Python and JavaScript/TypeScript and integrations with leading embedding providers (OpenAI, Cohere,
  Hugging Face, sentence-transformers).
url: https://raw.githubusercontent.com/api-evangelist/chroma/refs/heads/main/apis.yml
type: Index
deliveryModel:
  model: saas
  license: Apache License 2.0
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - license
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: paid
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Paid
  confidence: medium
  source:
  - plans
  - authentication
  - security
  generated: '2026-11-06'
  method: derived
position: Consuming
access: 3rd-Party
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/chroma.png
x-docs-platform: mintlify
x-docs-platform-confidence: medium
x-docs-platform-checked: 2026-09-21
x-docs-hosting: vercel
tags:
- Artificial Intelligence
- AI-native
- Apache 2.0
- Cloud
- Embeddings
- Hybrid Search
- JavaScript
- LLM
- Machine Learning
- Multi-Modal
- Open Source
- Python
- RAG
- Retrieval
- SDK
- Search
- Serverless
- TypeScript
- Vector Search
- Database
tags_raw:
- AI
- AI Native
- Apache 2.0
- Cloud
- Embeddings
- Hybrid Search
- JavaScript
- LLM
- Machine Learning
- Multi-Modal
- Open Source
- Python
- RAG
- Retrieval
- SDK
- Search
- Serverless
- TypeScript
- Vector Database
- Machine-Learning
- Open-Source
- Database
- Vector Search
created: '2025-03-07'
modified: '2026-05-19'
specificationVersion: '0.23'
apis:
- aid: chroma:python-client
  name: Chroma Python Client
  description: The Chroma Python Client is a first-party SDK for interacting with both self-hosted Chroma servers and Chroma
    Cloud. It provides a simple, developer-friendly interface with a core API of just four functions for managing collections,
    adding documents, and querying embeddings. The client handles automatic tokenization, embedding, and indexing of documents,
    making it straightforward to build AI applications that require vector similarity search.
  image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
  humanURL: https://docs.trychroma.com/reference/python/client
  tags:
  - Embeddings
  - Python
  - SDK
  - Vector Search
  tags_raw:
  - Embeddings
  - Python
  - SDK
  - Vector Database
  properties:
  - type: Documentation
    url: https://docs.trychroma.com/reference/python/client
  - type: SourceCode
    url: https://github.com/chroma-core/chroma
- aid: chroma:javascript-client
  name: Chroma JavaScript Client
  description: The Chroma JavaScript and TypeScript Client is a first-party SDK for interacting with Chroma from JavaScript
    or TypeScript applications. The v3 rewrite focused on reducing bundle size and improving developer experience, making
    it well-suited for deployment on serverless platforms like Vercel. It supports both self-hosted Chroma instances and Chroma
    Cloud via the CloudClient class, providing collection management, document ingestion, and vector similarity search capabilities.
  image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
  humanURL: https://docs.trychroma.com/reference/js/client
  tags:
  - Embeddings
  - JavaScript
  - SDK
  - TypeScript
  - Vector Search
  tags_raw:
  - Embeddings
  - JavaScript
  - SDK
  - TypeScript
  - Vector Database
  properties:
  - type: Documentation
    url: https://docs.trychroma.com/reference/js/client
  - type: SourceCode
    url: https://github.com/chroma-core/chroma-js
- aid: chroma:chroma-system-api
  name: Chroma System API
  description: System-level endpoints for health checks, version information, and server diagnostics.
  humanURL: https://docs.trychroma.com/reference/chroma-reference
  baseURL: https://api.trychroma.com
  tags:
  - System
  properties:
  - type: OpenAPI
    url: openapi/chroma-system-api-openapi.yml
  - type: Documentation
    url: https://docs.trychroma.com/reference/chroma-reference
  - type: Documentation
    url: https://docs.trychroma.com/cloud/sync/overview
- aid: chroma:chroma-authentication-api
  name: Chroma Authentication API
  description: The Authentication API from Chroma — 1 operation(s) for authentication.
  humanURL: https://docs.trychroma.com/reference/python/client
  baseURL: https://api.trychroma.com
  tags:
  - Authentication
  properties:
  - type: OpenAPI
    url: openapi/chroma-authentication-api-openapi.yml
  - type: Documentation
    url: https://docs.trychroma.com/reference/chroma-reference
  - type: Documentation
    url: https://docs.trychroma.com/cloud/sync/overview
  - type: Documentation
    url: https://docs.trychroma.com/docs/collections/manage-collections
  - type: APIReference
    url: https://docs.trychroma.com/reference/chroma-reference
  - type: PostmanCollection
    url: collections/chroma-db.postman_collection.json
  - type: OpenCollection
    url: collections/chroma-db.opencollection.json
  - type: Documentation
    url: https://docs.trychroma.com/docs/collections/add-data
  - type: APIReference
    url: https://docs.trychroma.com/reference/chroma-api/record/add-records
  - type: Documentation
    url: https://docs.trychroma.com/docs/querying-collections/query-and-get
  - type: APIReference
    url: https://docs.trychroma.com/reference/chroma-api/record/query-collection
  - type: Documentation
    url: https://docs.trychroma.com/docs/overview/architecture
- aid: chroma:chroma-collection-api
  name: Chroma Collection API
  description: The Collection API from Chroma — 7 operation(s) for collection.
  humanURL: https://docs.trychroma.com/reference/python/client
  baseURL: https://api.trychroma.com
  tags:
  - Collection
  properties:
  - type: OpenAPI
    url: openapi/chroma-collection-api-openapi.yml
  - type: Documentation
    url: https://docs.trychroma.com/reference/chroma-reference
  - type: Documentation
    url: https://docs.trychroma.com/cloud/sync/overview
  - type: Documentation
    url: https://docs.trychroma.com/docs/collections/manage-collections
  - type: APIReference
    url: https://docs.trychroma.com/reference/chroma-reference
  - type: PostmanCollection
    url: collections/chroma-db.postman_collection.json
  - type: OpenCollection
    url: collections/chroma-db.opencollection.json
  - type: Documentation
    url: https://docs.trychroma.com/docs/collections/add-data
  - type: APIReference
    url: https://docs.trychroma.com/reference/chroma-api/record/add-records
  - type: Documentation
    url: https://docs.trychroma.com/docs/querying-collections/query-and-get
  - type: APIReference
    url: https://docs.trychroma.com/reference/chroma-api/record/query-collection
  - type: Documentation
    url: https://docs.trychroma.com/docs/overview/architecture
- aid: chroma:chroma-database-api
  name: Chroma Database API
  description: The Database API from Chroma — 3 operation(s) for database.
  humanURL: https://docs.trychroma.com/reference/python/client
  baseURL: https://api.trychroma.com
  tags:
  - Database
  properties:
  - type: OpenAPI
    url: openapi/chroma-database-api-openapi.yml
  - type: Documentation
    url: https://docs.trychroma.com/reference/chroma-reference
  - type: Documentation
    url: https://docs.trychroma.com/cloud/sync/overview
  - type: Documentation
    url: https://docs.trychroma.com/docs/collections/manage-collections
  - type: APIReference
    url: https://docs.trychroma.com/reference/chroma-reference
  - type: PostmanCollection
    url: collections/chroma-db.postman_collection.json
  - type: OpenCollection
    url: collections/chroma-db.opencollection.json
  - type: Documentation
    url: https://docs.trychroma.com/docs/collections/add-data
  - type: APIReference
    url: https://docs.trychroma.com/reference/chroma-api/record/add-records
  - type: Documentation
    url: https://docs.trychroma.com/docs/querying-collections/query-and-get
  - type: APIReference
    url: https://docs.trychroma.com/reference/chroma-api/record/query-collection
  - type: Documentation
    url: https://docs.trychroma.com/docs/overview/architecture
- aid: chroma:chroma-function-api
  name: Chroma Function API
  description: The Function API from Chroma — 4 operation(s) for function.
  humanURL: https://docs.trychroma.com/reference/python/client
  baseURL: https://api.trychroma.com
  tags:
  - Function
  properties:
  - type: OpenAPI
    url: openapi/chroma-function-api-openapi.yml
  - type: Documentation
    url: https://docs.trychroma.com/reference/chroma-reference
  - type: Documentation
    url: https://docs.trychroma.com/cloud/sync/overview
  - type: Documentation
    url: https://docs.trychroma.com/docs/collections/manage-collections
  - type: APIReference
    url: https://docs.trychroma.com/reference/chroma-reference
  - type: PostmanCollection
    url: collections/chroma-db.postman_collection.json
  - type: OpenCollection
    url: collections/chroma-db.opencollection.json
  - type: Documentation
    url: https://docs.trychroma.com/docs/collections/add-data
  - type: APIReference
    url: https://docs.trychroma.com/reference/chroma-api/record/add-records
  - type: Documentation
    url: https://docs.trychroma.com/docs/querying-collections/query-and-get
  - type: APIReference
    url: https://docs.trychroma.com/reference/chroma-api/record/query-collection
  - type: Documentation
    url: https://docs.trychroma.com/docs/overview/architecture
- aid: chroma:chroma-record-api
  name: Chroma Record API
  description: The Record API from Chroma — 11 operation(s) for record.
  humanURL: https://docs.trychroma.com/reference/python/client
  baseURL: https://api.trychroma.com
  tags:
  - Record
  properties:
  - type: OpenAPI
    url: openapi/chroma-record-api-openapi.yml
  - type: Documentation
    url: https://docs.trychroma.com/reference/chroma-reference
  - type: Documentation
    url: https://docs.trychroma.com/cloud/sync/overview
  - type: Documentation
    url: https://docs.trychroma.com/docs/collections/manage-collections
  - type: APIReference
    url: https://docs.trychroma.com/reference/chroma-reference
  - type: PostmanCollection
    url: collections/chroma-db.postman_collection.json
  - type: OpenCollection
    url: collections/chroma-db.opencollection.json
  - type: Documentation
    url: https://docs.trychroma.com/docs/collections/add-data
  - type: APIReference
    url: https://docs.trychroma.com/reference/chroma-api/record/add-records
  - type: Documentation
    url: https://docs.trychroma.com/docs/querying-collections/query-and-get
  - type: APIReference
    url: https://docs.trychroma.com/reference/chroma-api/record/query-collection
  - type: Documentation
    url: https://docs.trychroma.com/docs/overview/architecture
- aid: chroma:chroma-tenant-api
  name: Chroma Tenant API
  description: The Tenant API from Chroma — 2 operation(s) for tenant.
  humanURL: https://docs.trychroma.com/reference/python/client
  baseURL: https://api.trychroma.com
  tags:
  - Tenants
  tags_raw:
  - Tenant
  properties:
  - type: OpenAPI
    url: openapi/chroma-tenant-api-openapi.yml
  - type: Documentation
    url: https://docs.trychroma.com/reference/chroma-reference
  - type: Documentation
    url: https://docs.trychroma.com/cloud/sync/overview
  - type: Documentation
    url: https://docs.trychroma.com/docs/collections/manage-collections
  - type: APIReference
    url: https://docs.trychroma.com/reference/chroma-reference
  - type: PostmanCollection
    url: collections/chroma-db.postman_collection.json
  - type: OpenCollection
    url: collections/chroma-db.opencollection.json
  - type: Documentation
    url: https://docs.trychroma.com/docs/collections/add-data
  - type: APIReference
    url: https://docs.trychroma.com/reference/chroma-api/record/add-records
  - type: Documentation
    url: https://docs.trychroma.com/docs/querying-collections/query-and-get
  - type: APIReference
    url: https://docs.trychroma.com/reference/chroma-api/record/query-collection
  - type: Documentation
    url: https://docs.trychroma.com/docs/overview/architecture
common:
- type: CapabilityMap
  url: capabilities/chroma-capability-edges.yml
  name: Chroma Business Capability Map
- type: RateLimits
  url: rate-limits/chroma-rate-limits.yml
- type: FinOps
  url: finops/chroma-finops.yml
- type: Plans
  url: plans/chroma-plans-pricing.yml
- type: IssueTracker
  url: https://github.com/chroma-core/chroma/issues
- type: Releases
  url: https://github.com/chroma-core/chroma/releases
- type: PostmanWorkspace
  url: https://www.postman.com/kinlaneapi/chroma/overview
- type: AgenticAccess
  url: agentic-access/chroma-agentic-access.yml
- type: TrustCenter
  url: security/chroma-trust-center.yml
- type: VulnerabilityDisclosure
  url: security/chroma-vulnerability-disclosure.yml
- type: DomainSecurity
  url: security/chroma-domain-security.yml
- type: Authentication
  url: authentication/chroma-authentication.yml
- type: LinkedIn
  url: https://www.linkedin.com/company/trychroma
- type: Website
  url: https://www.trychroma.com/
- type: Documentation
  url: https://docs.trychroma.com/docs/overview/introduction
- type: Portal
  url: https://docs.trychroma.com/
- type: Login
  url: https://cloud.trychroma.com/
- type: Pricing
  url: https://docs.trychroma.com/cloud/pricing
- type: Blog
  url: https://www.trychroma.com/blog
- type: GitHubOrg
  url: https://github.com/chroma-core
- type: SourceCode
  url: https://github.com/chroma-core/chroma
- type: Discord
  url: https://discord.gg/MMeYNTmh3x
- type: Twitter
  url: https://twitter.com/trychroma
- type: License
  name: Apache License 2.0
  url: https://github.com/chroma-core/chroma/blob/main/LICENSE
- type: TermsOfService
  url: https://www.trychroma.com/tos
- type: PrivacyPolicy
  url: https://www.trychroma.com/privacy
- type: JSONLDContext
  url: json-ld/chroma-context.jsonld
- type: JSONSchema
  url: json-schema/chroma-collection-schema.json
- type: JSONSchema
  url: json-schema/chroma-record-schema.json
- type: Spectral
  url: spectral/chroma-spectral.yml
- name: Features
  type: Features
  data:
  - name: Document and Metadata Storage
  - name: Vector Similarity Search (Dense, Sparse, Hybrid)
  - name: Full-Text and Regex Search
  - name: Metadata Filtering
  - name: Multi-Modal Retrieval (Text, Image, Audio)
  - name: Automatic Tokenization and Embedding
  - name: Collection Management
  - name: Embedding Function Plugins
  - name: Self-Hosted and Cloud Deployments
  - name: Apache 2.0 Open Source License
- name: EmbeddingProviders
  type: EmbeddingProviders
  data:
  - name: OpenAI
  - name: Cohere
  - name: Hugging Face
  - name: sentence-transformers
  - name: Google Vertex AI
  - name: Ollama
- name: UseCases
  type: UseCases
  data:
  - name: RAG (Retrieval Augmented Generation)
  - name: Semantic Search
  - name: AI Agent Memory
  - name: Code Search (AST-Aware Chunking)
  - name: Recommendation Systems
  - name: Multi-Modal Search (Text + Images)
  - name: Question Answering Systems
  - name: Knowledge Base Querying
- name: Standards
  type: Standards
  data:
  - name: OpenAPI Specification
  - name: REST/HTTP
  - name: Apache License 2.0
- type: LlmsText
  url: https://docs.trychroma.com/llms.txt
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

Chroma API — frequently asked questions

Does Chroma have an API?

Yes. APIs.io lists 9 APIs from Chroma, including Chroma Python Client, Chroma JavaScript Client and Chroma System API, and 6 more.

Is there an OpenAPI specification for the Chroma API?

Yes. APIs.io indexes 7 OpenAPI specifications for Chroma, each linked for download from this page.

How do I authenticate with the Chroma API?

Chroma uses bearer-token authentication (apiKey/http · 3 schemes). The details are profiled on APIs.io as Chroma Authentication.

How much does the Chroma API cost?

Chroma publishes its prices; its Writes plan is $2.50 per logical GiB written as of 2026-10-07. APIs.io lists 9 pricing plans for Chroma, with each plan's price, limits and inclusions under Pricing on this page.

Does Chroma have an MCP server?

Yes. APIs.io lists 1 MCP server for Chroma: Remote MCP server at mcp.trychroma.com over HTTP; 3 tools listed.

Is the Chroma API ready for AI agents?

Chroma has a Kin Score of 58.5 out of 100 (strong) and an Agent Readiness score of 40.1 (agent-ready), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider 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 providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
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.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/chroma"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/chroma/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/chroma/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.