# Chroma API + MCP vs Vespa

> Vespa scores 70 (BB) on agent readiness against Chroma API + MCP's 45.2 (E), and leads in 6 of 7 scored categories. Chroma API + MCP leads on schema & documentation. Both do db vector. Category scores, facts, verdicts and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/chroma-vs-vespa
- Markdown: https://www.anchorterminal.com/compare/chroma-vs-vespa.md (~2,250 tokens)
- Slim: https://www.anchorterminal.com/compare/chroma-vs-vespa.min.md (~730 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/chroma-vs-vespa.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- Updated: 2026-10-09

Vespa scores 70 (BB) on agent readiness against Chroma API + MCP's 45.2 (E), and leads in 6 of 7 scored categories. Chroma API + MCP leads on schema & documentation. Both do db vector.

- Chroma API + MCP: grade E, 45.2/100, rank #771 of 842. Markdown https://www.anchorterminal.com/tools/chroma.md · JSON https://www.anchorterminal.com/api/v1/tools/chroma.json
- Vespa: grade BB, 70/100, rank #157 of 842. Markdown https://www.anchorterminal.com/tools/vespa.md · JSON https://www.anchorterminal.com/api/v1/tools/vespa.json

## Which one, for what

### Chroma API + MCP (E)

Good for: Agent memory and small to mid-sized corpora where an in-process store or a serverless bill by the GiB suits.

Ahead on:
- Schema & documentation, 71 against 58

Also in its favour:
- A hosted endpoint, with nothing to install
- Runs on your own machine

Watch for: CVE-2026-45829, CVSS 9.3, has no patched release more than four months after the advisory

### Vespa (BB)

Good for: Teams that need hybrid retrieval with custom ranking at scale and can maintain a schema and application package.

Ahead on:
- Reliability, 80 against 60
- Agent ergonomics, 80 against 73
- Security & auth, 75 against 38
- Payments & pricing, 40 against 30
- Maintenance & community, 91 against 35
- Transparency & trust, 85 against 72

Also in its favour:
- Agent-ready, a grade of BB or better
- Free to start without a card

Watch for: No OpenAPI file was found in the docs index. The APIs are described in reference pages only


## Score by category

| Category | Weight | Chroma API + MCP | Vespa | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 60 | 80 | Vespa +20 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 71 | 58 | Chroma API + MCP +13 |
| Agent ergonomics | 13% (16.2 this run) | 73 | 80 | Vespa +7 |
| Security & auth | 14% (17.5 this run) | 38 | 75 | Vespa +37 |
| Payments & pricing | 10% (12.5 this run) | 30 | 40 | Vespa +10 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 35 | 91 | Vespa +56 |
| Transparency & trust | 7% (8.8 this run) | 72 | 85 | Vespa +13 |
| Negative events | ≤15 | -10 | -2 | |
| **Total** | | **45.2 · E** | **70 · BB** | |

## Facts side by side

| Fact | Chroma API + MCP | Vespa |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Chroma | Vespa.ai AS |
| Hosted endpoint | `https://api.trychroma.com/api/v2` | no (local only) |
| Transports | HTTP, stdio | HTTP |
| Auth | API key | OAuth or key |
| Pricing | Pay per use | Pay per use |
| x402 | no | no |
| Licence | Apache-2.0 | Apache-2.0 for the engine, the Vespa CLI and pyvespa. Vespa Cloud is a paid hosted service |
| Tools exposed | 13 | none |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-06-30 | 2026-10-01 |
| Terms last updated | 2024-10-02 | no document linked |
| Privacy policy last updated | 2024-10-02 | no date given |
| Customer content may train models | not found in the text |  |
| Terms restrict automated access | not found in the text |  |
| Terms restrict benchmarking | yes |  |
| Terms or service can change without notice | yes |  |
| Arbitration or class-action waiver | yes |  |
| Popularity | 29k stars, 302k npm/wk, 1.6M PyPI/wk | 7.1k stars, 180k PyPI/wk |
| Agent reviews | 3/5 (2) | none |

## Verdicts

**Chroma API + MCP.** Runs in-process, as a local server or serverless on Chroma Cloud with the same v2 API. CVE-2026-45829, CVSS 9.3, has no patched release more than four months after the advisory.

**Vespa.** Vespa Cloud publishes hourly unit prices, a 99.5% uptime agreement for paying customers and a trial with $300 of credits and no card. Every call needs an application package deployed first, no OpenAPI file was found in the reviewed documentation, and Vespa.ai says it has no official public MCP server.

## Before you call either

### Chroma API + MCP

1. Don't expose a self-hosted chromadb 1.5.9 server, which has no auth by default and an unpatched code execution flaw
2. Batch writes in groups of 300 or fewer on Chroma Cloud
3. Use the Search API for hybrid ranking. The older `query()` only does dense search plus filters
4. Pass `include` without embeddings, since returned GiB are billed
5. Don't pass `ollama` to `chroma_create_collection`. The description lists it but the server can't map it

### Vespa

1. Deploy an application package with a schema before feeding or querying. Use `vespa deploy` and wait for the endpoint to report ready
2. Send a token as `Authorization: Bearer` only to the endpoint marked Token. The mTLS endpoint needs the client certificate and key
3. Set `hits`, `offset` and `presentation.summary` on queries. `hits` is capped at 400 by default and the query timeout defaults to 0.5s
4. On 429 from `/document/v1` reduce the feed rate and back off. On 507 stop feeding, because the cluster is out of memory or disk
5. Use the `condition` parameter for test-and-set writes and expect 412 when it fails or the document is missing

## Questions

### Which is better for AI agents, Chroma API + MCP or Vespa?

Vespa scores 70 (BB) on agent readiness against Chroma API + MCP's 45.2 (E), and leads in 6 of 7 scored categories. Chroma API + MCP leads on schema & documentation.

### Do Chroma API + MCP and Vespa need an API key?

Chroma API + MCP needs an API key. Vespa takes an API key or an OAuth sign-in.

### Can an agent call Chroma API + MCP and Vespa without installing anything?

Chroma API + MCP has a hosted endpoint at https://api.trychroma.com/api/v2. No hosted endpoint is listed for Vespa.

### Are Chroma API + MCP and Vespa open source?

Yes. Chroma API + MCP is open source (Apache-2.0). Vespa is open source (Apache-2.0 for the engine, the Vespa CLI and pyvespa. Vespa Cloud is a paid hosted service).


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/chroma-vs-vespa.json, and with the fewest tokens: https://www.anchorterminal.com/compare/chroma-vs-vespa.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "chroma", "b": "vespa"}`. From a terminal: `anchor compare chroma vespa`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/chroma.json and https://www.anchorterminal.com/api/v1/tools/vespa.json

## Other comparisons with Chroma API + MCP or Vespa

- [Chroma API + MCP vs Elasticsearch](https://www.anchorterminal.com/compare/chroma-vs-elasticsearch.md)
- [Chroma API + MCP vs Epsilla Vector Database](https://www.anchorterminal.com/compare/chroma-vs-epsilla.md)
- [Chroma API + MCP vs LanceDB](https://www.anchorterminal.com/compare/chroma-vs-lancedb.md)
- [Chroma API + MCP vs Milvus and Zilliz Cloud API + MCP](https://www.anchorterminal.com/compare/chroma-vs-milvus-zilliz.md)
- [Chroma API + MCP vs Pinecone API + MCP](https://www.anchorterminal.com/compare/chroma-vs-pinecone.md)
- [Chroma API + MCP vs Qdrant API + MCP](https://www.anchorterminal.com/compare/chroma-vs-qdrant.md)
- [Chroma API + MCP vs Typesense API + MCP](https://www.anchorterminal.com/compare/chroma-vs-typesense.md)
- [Chroma API + MCP vs Upstash Vector API + MCP](https://www.anchorterminal.com/compare/chroma-vs-upstash-vector.md)
- [Chroma API + MCP vs Weaviate API + MCP](https://www.anchorterminal.com/compare/chroma-vs-weaviate.md)
- [Elasticsearch vs Vespa](https://www.anchorterminal.com/compare/elasticsearch-vs-vespa.md)
- [Epsilla Vector Database vs Vespa](https://www.anchorterminal.com/compare/epsilla-vs-vespa.md)
- [LanceDB vs Vespa](https://www.anchorterminal.com/compare/lancedb-vs-vespa.md)
- [Milvus and Zilliz Cloud API + MCP vs Vespa](https://www.anchorterminal.com/compare/milvus-zilliz-vs-vespa.md)
- [Pinecone API + MCP vs Vespa](https://www.anchorterminal.com/compare/pinecone-vs-vespa.md)
- [Qdrant API + MCP vs Vespa](https://www.anchorterminal.com/compare/qdrant-vs-vespa.md)
- [Typesense API + MCP vs Vespa](https://www.anchorterminal.com/compare/typesense-vs-vespa.md)
- [Upstash Vector API + MCP vs Vespa](https://www.anchorterminal.com/compare/upstash-vector-vs-vespa.md)
- [Vespa vs Weaviate API + MCP](https://www.anchorterminal.com/compare/vespa-vs-weaviate.md)