chroma.com

AI agents struggle discovering and understanding site content due to missing meta descriptions and no llms.txt file guiding agent interactions.

12 pass · 11 warn · 2 fail · 17 n/a

Watch a real agent use your site →

A live Claude Code run against chroma.com, streamed step by step.

Measure this with real agents →

An audit: measured success rates from repeated real agent runs, with confidence intervals and downloadable evidence.

Discovery

18/22.2

Accessibility

24.7/33.3

Usability

22.2/44.4

Payments

n/a

Discovery 18/22.2

Homepage has a meta descriptiondetailsFAIL
no <meta name="description">
Fix: Add a <meta name="description"> of 50–200 characters summarising what the product does. Agents use it as the one-line answer to "what is this site".
API reference linked from the homepagedetailsWARN
no link to an API reference in the homepage HTML
Fix: If you have an API, link its reference from the homepage. If you don't, this check is safe to ignore.
Homepage has a descriptive titledetailsWARN
title is 96 characters (truncated in most surfaces)

Badge

Shows the current scan score and grade for this domain, straight from the latest static pre-check.

[![agent ready](https://www.vorza.dev/api/badge/chroma.com)](https://www.vorza.dev/score/chroma.com)

<a href="https://www.vorza.dev/score/chroma.com"><img src="https://www.vorza.dev/api/badge/chroma.com" alt="agent readiness score" /></a>

Fix: Trim the <title> to 70 characters or fewer so it is not cut off.

Canonical URL declareddetailsPASS

https://www.chroma.com/

Documentation linked from the homepagedetailsPASS

2 docs link(s), e.g. /resources/technical-library/guides-and-instructions/cleaning-filters/

Open Graph tags presentdetailsPASS

og:title and og:description present

robots.txt allows agent crawlersdetailsPASS

all 6 agent crawlers may fetch /

robots.txt existsdetailsPASS

HTTP 200, 893 bytes

robots.txt points at the sitemapdetailsPASS

robots.txt has a Sitemap: line

sitemap.xml exists and parsesdetailsPASS

7 URL(s) listed

Brand findable in agent searchdetailsN/A

search-based checks are deferred — excluded from the score

Listed in an MCP registrydetailsN/A

registry lookup not implemented in v1 — excluded from the score rather than guessed

Accessibility 24.7/33.3

llms.txt is publisheddetailsFAIL
/llms.txt not served (HTTP 404)
Fix: Publish /llms.txt: a plain-markdown index that tells an agent what this product is and where the authoritative docs live. It is the cheapest high-leverage file you can add.
Structured data (JSON-LD) on the homepagedetailsWARN
no JSON-LD blocks on the homepage
Fix: Add a JSON-LD block (schema.org Organization or SoftwareApplication) so agents get your name, description and links as data rather than prose.
llms-full.txt is publisheddetailsWARN
/llms-full.txt not served
Fix: Optional but cheap: publish /llms-full.txt with your docs inlined as one markdown file, so an agent can read everything in a single fetch.
Serves markdown when asked for itdetailsWARN
Accept: text/markdown → text/html; charset=UTF-8
Fix: Optional but increasingly expected: honour `Accept: text/markdown` by serving a markdown rendering of the page, so agents skip HTML parsing entirely.
Content-to-markup ratio is reasonabledetailsWARN
ratio 0.0392 — 9688 readable chars in 246957 bytes of HTML
Fix: Most of what you serve is markup and inline script rather than content. Reduce inline payloads or server-render more text so the signal-to-noise ratio favours readers.
Homepage responds to an agent requestdetailsPASS
HTTP 200 for / (agent UA)
Served over HTTPSdetailsPASS
https://www.chroma.com/
Same response for agents and browsersdetailsPASS
both User-Agents got HTTP 200
Homepage has readable text without JavaScriptdetailsPASS
9688 characters of text in the served HTML
No long redirect chain on the homepagedetailsPASS
1 redirect(s)
Docs are readable without JavaScriptdetailsN/A
/docs not served (HTTP 404) — docs may live on another path or host
Links in llms.txt resolvedetailsN/A
no llms.txt
llms.txt is structured markdowndetailsN/A
no llms.txt to parse

Usability 22.2/44.4

agents.md is publisheddetailsWARN
/agents.md not served (HTTP 404)
Fix: Publish /agents.md: what an agent may do here, which endpoints matter, auth requirements, and rate limits. It is the agent-facing counterpart to a README.
A documentation endpoint respondsdetailsWARN
/docs → HTTP 404
Fix: Serve docs at the conventional /docs path, or redirect it to wherever they live. Agents try conventional paths first.
Errors are machine-readabledetailsWARN
404 returns HTML, not a machine-readable body
Fix: Content-negotiate your errors: return a JSON body with a stable `code` (and a `next_action` where recovery exists) to clients that ask for JSON.
OpenAPI document publisheddetailsWARN
/openapi.json not served (HTTP 404)
Fix: If you have an HTTP API, publish its OpenAPI document at a predictable path (/openapi.json). It is the difference between an agent reading your contract and an agent guessing it. If you have no HTTP API, ignore this.
.well-known/mcp.json advertises an MCP serverdetailsWARN
/.well-known/mcp.json not served (HTTP 404)
Fix: If you run an MCP server, advertise it at /.well-known/mcp.json so agents discover it without being told its URL.
The /api root behaves predictablydetailsN/A
/api → HTTP 404 (no API at the conventional root)
MCP server completes the initialize handshakedetailsN/A
no MCP endpoint found to probe (none in the input URL and none advertised at /.well-known/mcp.json)
MCP tool parameters are typed and describeddetailsN/A
no listed MCP tools to inspect
Every MCP tool has a descriptiondetailsN/A
no listed MCP tools to inspect
MCP server lists toolsdetailsN/A
no MCP endpoint to probe
OpenAPI declares its auth schemedetailsN/A
no parseable OpenAPI document
OpenAPI operations are describeddetailsN/A
no parseable OpenAPI document
OpenAPI documents error responsesdetailsN/A
no parseable OpenAPI document
OpenAPI document is structurally validdetailsN/A
no parseable OpenAPI document

Payments not applicable — excluded from the score

Serves a 402 payment challengedetailsN/A
no agent-payment rail published — not applicable. This layer is excluded from the score rather than counted against the site.
Declares AP2 / ACP supportdetailsN/A
no agent-payment rail published — not applicable. This layer is excluded from the score rather than counted against the site.
Publishes x402 payment metadatadetailsN/A
no agent-payment rail published — not applicable. This layer is excluded from the score rather than counted against the site.