Getting started
Run402 is designed to be driven by an AI coding agent end to end — no human signup,
no dashboard API keys, no human in the payment loop. This page orients the
developer supervising that agent; the agent itself works from the flat
references (/llms-cli.txt,
/llms-sdk.txt,
/llms-mcp.txt) and the skill at
/SKILL.md.
Pick an integration surface
Section titled “Pick an integration surface”| You / your agent want to… | Use | Reference |
|---|---|---|
| Drive Run402 from a shell or CI | the run402 CLI |
CLI reference |
| Call Run402 from TypeScript | @run402/sdk |
SDK reference |
| Wire Run402 into an MCP host (Claude Desktop, Cursor, Claude Code) | run402-mcp |
MCP reference |
The 30-second start
Section titled “The 30-second start”The prototype tier is free on testnet — no real money. The wayfinder at
run402.com/llms.txt carries the current
copy-paste bootstrap; the CLI reference covers run402 deploy apply, the unified
deploy primitive. Run402 plans and stages a database, functions, a static
site, secrets, assets, subdomains and routes as one release, then activates
them together. Failed stages are resumable; applied database migrations are
not automatically reversed when you promote an older release.
| Stage | Visible before activation? | Automatically reversible? |
|---|---|---|
| CAS uploads | No | Yes (unused bytes are GC’d) |
| Function staging | No | Yes |
| Static-site staging | No | Yes |
| SQL migrations | No | Not necessarily |
| Release-pointer activation | Atomic | By promoting another release |
| Cache invalidation | After activation | Recomputed |
When something fails
Section titled “When something fails”Run402’s Astro/SSR runtime, deploy pipeline, SDK and cache layer return stable
structured error envelopes. Every one carries a code, a suggestedFix, and a
docs URL into this site — see the error-code reference.