Static pre-check · Fri, 07 Aug 2026 06:48:55 GMT
bolt.new
AI agents struggle to discover integration methods and API specifications due to missing documentation, llms.txt file, and OpenAPI schema.
Watch a real agent use your site →
A live Claude Code run against bolt.new, 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 18/22.2
Documentation linked from the homepagedetailsFAIL
no link to documentation found in the homepage HTML
Fix: Link your docs from the homepage with visible anchor text ("Docs", "Documentation", "Developers"). An agent that cannot find your docs from your homepage will guess your API.
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.
Canonical URL declareddetailsPASS
https://bolt.new
Homepage has a meta descriptiondetailsPASS
105 characters
Homepage has a descriptive titledetailsPASS
'Bolt AI builder: Websites, apps & prototypes' (44 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, 92 bytes
robots.txt points at the sitemapdetailsPASS
robots.txt has a Sitemap: line
sitemap.xml exists and parsesdetailsPASS
63 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 28.3/33.3
llms.txt is structured markdowndetailsFAIL
/llms.txt returns HTML, not markdown
Fix: Serve /llms.txt as text/plain or text/markdown. An HTML error page at this path is worse than a 404: it looks like content.
Links in llms.txt resolvedetailsWARN
llms.txt contains no resolvable links
Fix: Add markdown links to your actual docs pages — a description with no links leaves the agent where it started.
Serves markdown when asked for itdetailsWARN
Accept: text/markdown → text/html
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.023 — 2693 readable chars in 116914 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.
Docs are readable without JavaScriptdetailsPASS
4089 characters of text at /docs
Homepage responds to an agent requestdetailsPASS
HTTP 200 for / (agent UA)
Served over HTTPSdetailsPASS
https://bolt.new/
Structured data (JSON-LD) on the homepagedetailsPASS
2 valid block(s) (WebApplication, Organization)
llms-full.txt is publisheddetailsPASS
HTTP 200, 71372 bytes
llms.txt is publisheddetailsPASS
HTTP 200, 71373 bytes
Same response for agents and browsersdetailsPASS
both User-Agents got HTTP 200
Homepage has readable text without JavaScriptdetailsPASS
2693 characters of text in the served HTML
No long redirect chain on the homepagedetailsPASS
0 redirect(s)
Usability 20.1/44.4
OpenAPI document publisheddetailsFAIL
/openapi.json is served but is not valid JSON
Fix: Serve a parseable OpenAPI document at /openapi.json. What is there now cannot be read by any tooling.
agents.md is publisheddetailsWARN
/agents.md returns HTML
Fix: Serve /agents.md as markdown (text/markdown or text/plain). An HTML page here is probably your SPA catch-all route.
The /api root behaves predictablydetailsWARN
/api → HTTP 200 text/html
Fix: Serve JSON from API paths, with an accurate content-type.
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
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.
Badge
Shows the current scan score and grade for this domain, straight from the latest static pre-check.
[](/score/bolt.new)<a href="/score/bolt.new"><img src="/api/badge/bolt.new" alt="agent readiness score" /></a>