assemblyai.com

AI agents can easily discover and access AssemblyAI's speech transcription APIs, though some usability friction exists in navigation and task completion workflows.

27 pass · 5 warn · 0 fail · 10 n/a

Watch a real agent use your site →

A live Claude Code run against assemblyai.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

22.2/22.2

Accessibility

32.1/33.3

Usability

37.2/44.4

Payments

n/a

Discovery 22.2/22.2

API reference linked from the homepagedetailsPASS
5 API link(s), e.g. https://www.assemblyai.com/docs/api-reference/overview
Canonical URL declareddetailsPASS
https://www.assemblyai.com/
Documentation linked from the homepagedetailsPASS
5 docs link(s), e.g. https://www.assemblyai.com/docs
Homepage has a meta descriptiondetailsPASS
121 characters
Homepage has a descriptive titledetailsPASS
'AssemblyAI | AI models to transcribe and understand speech' (58 chars)
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, 401 bytes
robots.txt points at the sitemapdetailsPASS
robots.txt has a Sitemap: line
sitemap.xml exists and parsesdetailsPASS
1532 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 32.1/33.3

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.
Docs are readable without JavaScriptdetailsPASS
1754 characters of text at /docs
Homepage responds to an agent requestdetailsPASS
HTTP 200 for / (agent UA)
Served over HTTPSdetailsPASS
https://www.assemblyai.com/
llms.txt is publisheddetailsPASS
HTTP 200, 3953 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
10851 characters of text in the served HTML
Content-to-markup ratio is reasonabledetailsPASS
ratio 0.0571 (10851 chars of 189914)
No long redirect chain on the homepagedetailsPASS
1 redirect(s)

Usability 37.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.
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.
A documentation endpoint respondsdetailsPASS
/docs → HTTP 200
OpenAPI declares its auth schemedetailsPASS
1 scheme(s): ApiKey
OpenAPI operations are describeddetailsPASS
10/10 operations described (100%)
OpenAPI document publisheddetailsPASS
HTTP 200, 260347 bytes of JSON
OpenAPI documents error responsesdetailsPASS
2 error response(s) with a schema
OpenAPI document is structurally validdetailsPASS
OpenAPI 3.1.0, 8 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/assemblyai.com)](/score/assemblyai.com)

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