crewai.com

AI agents can navigate CrewAI's site well but lack complete error response documentation in OpenAPI specs, limiting integration reliability.

22 pass · 8 warn · 1 fail · 11 n/a

Watch a real agent use your site →

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

Test this with real agents →

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

Discovery

19/22.2

Accessibility

31.9/33.3

Usability

30/44.4

Payments

n/a

Discovery 19/22.2

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 meta descriptiondetailsWARN
description is only 32 characters
Fix: Expand the meta description to at least 50 characters.
Homepage has a descriptive titledetailsWARN
title is only 6 characters: 'CrewAI'
Fix: Expand the <title> to 10–70 characters naming the product and what it does.
Canonical URL declareddetailsPASS
https://crewai.com
Documentation linked from the homepagedetailsPASS
3 docs link(s), e.g. https://docs.crewai.com/
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, 134 bytes
robots.txt points at the sitemapdetailsPASS
robots.txt has a Sitemap: line
sitemap.xml exists and parsesdetailsPASS
86 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 31.9/33.3

Content-to-markup ratio is reasonabledetailsWARN
ratio 0.0165 — 4361 readable chars in 263978 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://crewai.com/
Structured data (JSON-LD) on the homepagedetailsPASS
1 valid block(s) (Organization)
llms-full.txt is publisheddetailsPASS
HTTP 200, 4888 bytes
llms.txt is publisheddetailsPASS
HTTP 200, 2827 bytes
Links in llms.txt resolvedetailsPASS
5 sampled link(s) all resolve
llms.txt is structured markdowndetailsPASS
has headings and markdown links
Serves markdown when asked for itdetailsPASS
Accept: text/markdown → text/markdown; charset=utf-8
Same response for agents and browsersdetailsPASS
both User-Agents got HTTP 200
Homepage has readable text without JavaScriptdetailsPASS
4361 characters of text in the served HTML
No long redirect chain on the homepagedetailsPASS
0 redirect(s)
Docs are readable without JavaScriptdetailsN/A
/docs not served (HTTP 404) — docs may live on another path or host

Usability 30/44.4

OpenAPI documents error responsesdetailsFAIL
no 4xx/5xx responses documented on any operation
Fix: Document your error responses with codes and schemas. Undocumented failures are where agent integrations silently break.
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.
.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.
OpenAPI declares its auth schemedetailsPASS
2 scheme(s): OAuth2, ApiKeyAuth
OpenAPI operations are describeddetailsPASS
5/5 operations described (100%)
OpenAPI document publisheddetailsPASS
HTTP 200, 3744 bytes of JSON
OpenAPI document is structurally validdetailsPASS
OpenAPI 3.1.0, 5 path(s)
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

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.

Badge

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

[![agent ready](/api/badge/crewai.com)](/score/crewai.com)

<a href="/score/crewai.com"><img src="/api/badge/crewai.com" alt="agent readiness score" /></a>