doclight — ai Readiness Report
bolt.new
Pages analyzed (12)
llms.txt found
AI READINESS SCORE
0 /100
Bolt (bolt.new) is an AI-powered website and app builder by StackBlitz that lets users prompt, run, edit, and publish web and mobile apps directly in the browser. Users describe what they want to build in natural language and Bolt generates the code, with integrations for Figma, Expo, GitHub, Supabase, Stripe, Netlify, and MCP servers. It includes hosting, databases, custom domains, and team collaboration features, with usage metered in AI tokens.
Dimension Breakdown
Discoverability
80
The product is clearly named, described, and indexed with an llms.txt documentation index, making it easy to find and categorize.
Comprehension
85
It is very clear that Bolt is an AI app/website builder, with extensive prose explaining its capabilities and integrations.
Setup clarity
55
Getting started is conversational (prompt-based) and documented for integrations, but no programmatic onboarding or account setup steps are exposed for an agent.
Documentation
75
Rich human-readable documentation exists with quickstarts, tutorials, and integration guides, plus a markdown-friendly llms.txt index.
Pricing clarity
80
Pricing tiers, token limits, and feature differences are clearly laid out, though token-to-cost conversion remains somewhat ambiguous.
Integration examples
40
Tool integrations (Figma, Expo, GitHub, Stripe) are documented as UI workflows, but there is no public API, SDK, or code examples for programmatic use.
Agent Journey
Discover
Understand
!
Setup
Setup is entirely UI/chat-driven with no programmatic account creation or API key flow, so an autonomous agent cannot self-onboard without a human.
!
Use
There is no public API or OpenAPI spec, so an agent cannot programmatically invoke Bolt beyond a human-facing chat interface.
Confusion Points
Missing Information
Improvements
  1. Serve llms.txt and llms-full.txt as actual plain-text/markdown content instead of an HTML app shell so agents can parse them.
  2. Publish a public API reference with an OpenAPI/Swagger spec covering project creation, build, and publish operations.
  3. Document an authentication flow (API keys/OAuth) that allows non-interactive, agent-driven access.
  4. Provide code examples and SDK snippets for common operations and integrations (GitHub, Supabase, Stripe).
  5. Add a clear token-cost calculator or worked examples mapping token usage to project size and dollar cost.
  6. Include machine-readable pricing data (e.g., JSON) so agents can parse and compare plans deterministically.