Bolt.new
Bolt.new is StackBlitz's in-browser AI full-stack app builder. From a natural language prompt it generates, edits, runs, and deploys complete web applications inside the user's browser tab using StackBlitz's WebContainer runtime — a WebAssembly-based Node.js operating system that boots a real filesystem, npm/pnpm/yarn package manager, terminal, and live preview without a remote VM. The product targets product managers, entrepreneurs, marketers, agencies, and non-engineer builders with conversational app creation, design-system import from Figma and component libraries (Material UI, Chakra UI, Shadcn/ui), built-in database and authentication, one-click deploy to Netlify or bolt.host, custom domains, GitHub version control, and integrations with Supabase, Stripe, Expo, and MCP servers. Bolt.new itself is a hosted, UI-driven product metered in monthly AI tokens with Free, Pro, Teams, and Enterprise tiers — there is no public REST/HTTP developer API or CLI. StackBlitz separately ships the WebContainer API as a JavaScript/TypeScript SDK (npm @webcontainer/api) for embedding the same in-browser dev environment in third-party sites, plus a StackBlitz SDK (@stackblitz/sdk) for programmatically opening projects. The Bolt.new reference codebase is open source under MIT at github.com/stackblitz/bolt.new as a foundation for building custom AI dev agents; the hosted commercial product is closed source.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles Bolt.new the way a machine reads it — 5 machine-readable artifacts, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Bolt.new scores 23.9/100 (emerging), with a separate agent-readiness read of 7/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Bolt.new
Each block below is one kind of artifact we hold for Bolt.new. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Bolt New Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Bolt New Finops
FINOPSSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for Bolt.new — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 1
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Learn 2
Tutorials, courses, talks, and written guidance
Operate 2
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 5
The organization behind the API
Other 7
Properties that don't map to a standard resource type
Scroll within the panel for all 7 ·
← All providers · Data indexed from github.com/api-evangelist/bolt-new · machine-readable index on apis.io