Run402 is the backend your coding agent runs itself: Postgres, a REST API, auth, file storage, serverless functions and hosting, provisioned and deployed through one staged CLI workflow, plus an encrypted Git remote (GitVault). No cloud console, no signup. Free to start.
Agent-first, human-owned. Your agent acts through its own identity and a bounded budget; you keep ownership, policy, recovery, billing, and high-stakes consent without becoming its cloud-console operator.
2,136 wallets served
Do this: paste this into your agent's chat.
Please build me a demo with the Run402 CLI using the complete files at run402.com/llms.txt. When you're done, give me the site link and the console link.
Run402 is the missing bridge between "the agent wrote code" and "your app is live on the internet".
Under the hood, the whole app is one apply call:
# Prepare run402.json and every referenced file from docs.run402.com/start/first-deploy/ npm install -g run402@latest run402 up --name my-app -y # Inspect the deployment result and returned site / console links. run402 up verify
The manifest groups database, auth, functions, site and assets into a staged release. Inspect activation and verification separately; migrations are not rolled back automatically. Use the typed SDK for programmatic TypeScript/JavaScript workflows; shell scripts and CI can keep using the CLI. See /llms.txt or the Run402 2.0 announcement for details.
Your agent will read the docs, provision the backend, and deploy a frontend — completely free on the prototype tier (testnet money only). Pick an idea and copy the prompt.
Full breakdown, including what the limits pool across: /pricing.
The prototype tier is free — uses testnet USDC to verify the agent's wallet and x402 setup. No real money. Production tiers are prepaid leases (no overages, no surprise bills).
Prototype tier uses testnet money — just to verify the agent's setup works. For production (hobby/team), your agent pays with real USDC on Base via x402, pathUSD on Tempo via MPP, or sats over Bitcoin Lightning via MPP, or you can buy Run402 credits with a credit card via Stripe.
Need on-chain signing? KMS signers: $0.04/day per wallet ($1.20/month) plus $0.000005 per contract call (KMS sign fee). Chain gas at-cost. Non-custodial — see /billing/.
Agents write a lot of private code, and wherever it's hosted, somebody can read it — index it, train a model on it, hand it to whoever asks next. GitVault is a Git remote encrypted on your own machine before anything is stored: Run402 cannot decrypt your gitvault or repository history. Deployment artifacts remain a disclosed plaintext custody boundary. Not a promise we keep — a key we never had.
run402 repos create # project + vault + origin remote, one call git push origin main # encrypted before it leaves the machine
Keep GitHub or GitLab as your primary and add GitVault as the encrypted second remote — nothing to migrate. And with the opt-in mirror, we don't even have to be the only place it rests: Your ciphertext replicates to a bucket you own. Host-blind and hostage-free — the full claims, their exact strengths, and the honest limits are at /gitvault.
Today, agents can write the frontend in minutes—then they stop at the wall: "Create a database. Set up auth. Configure storage. Deploy hosting. Paste me the keys."
Run402 removes the wall. With x402 or MPP (on Tempo or Bitcoin Lightning), the agent can procure infrastructure the moment it needs it—under a prepaid cap—and hand you a live URL.
# Without autonomous infrastructure: Agent "I can build this, but I need a DB + auth + hosting. Can you set it up?" Human Signs up → configures → copies keys → pastes back Time 10–30 minutes of overhead, per project # With Run402: Agent Acts as itself; pays + provisions within explicit authority Human Keeps ownership, policy, recovery, and high-stakes consent Result Backend + frontend hosting, ready Time seconds, without routine cloud-console labor
Run402 is agent-native: your agent can integrate however it prefers. The canonical docs are /llms.txt.
CLI npm install -g run402 SDK @run402/sdk for typed scripting Buzz Link a multiplayer agent to Run402 with the open-source skill HTTP Call the API directly: https://api.run402.com MCP npx run402-mcp OpenClaw Run402 skill teaches the CLI; SDK for scripts, MCP for tool-native hosts
Run402 for Buzz connects peer people and agents in a signed workspace to attributable infrastructure work. Buzz remains the signed collaboration record; Run402 records the deployment and runtime facts; public identity links and receipts connect them while every private key stays separate.
Three rails, one pattern: the API answers 402 Payment Required, the agent pays — USDC on Base, pathUSD on Tempo, or sats over Bitcoin Lightning — and retries. Humans who prefer a card buy credits via Stripe.
In 1997, HTTP reserved status code 402 Payment Required—but digital payments weren't ready. Nearly three decades later, stablecoins on L2 chains and agents that can sign transactions finally make it real.
x402 is an open protocol by Coinbase that turns any HTTP API into a paid service. No accounts, no subscriptions—just standard HTTP headers and USDC on Base.
# How x402 works: 1. Agent sends HTTP request → Server returns 402 Payment Required 2. Agent signs USDC transfer → Retries with payment proof 3. Server verifies and settles → Returns 200 OK + resource # Settlement: ~2 seconds. Gas: sub-cent on Base L2. # The agent never pays gas — the facilitator submits the tx.
MPP (Machine Payments Protocol) uses the same 402→sign→retry pattern as x402—but runs on Tempo, an EVM-compatible L1 with sub-second finality. No gas token: fees are paid in stablecoins (pathUSD). The same private key works on both chains.
MPP is an open protocol by Stripe. Agents use the mppx SDK the same way they use x402—one config field switches the payment rail.
# How MPP works: 1. Agent sends HTTP request → Server returns 402 Payment Required 2. Agent signs pathUSD transfer → Retries with payment proof 3. Server verifies and settles → Returns 200 OK + resource # Settlement: sub-second on Tempo L1. # No gas token — fees paid in stablecoins (pathUSD).
The same MPP handshake, settled on the Bitcoin Lightning Network. The 402 carries one fixed BOLT11 invoice minted on Run402's own Lightning Hub; the agent pays it and retries with the preimage as its credential. No chain, no gas, no token — just sats, on mainnet.
run402 init lightning gives the agent a budgeted wallet on that Hub with a few starter sats, and Lightning becomes its default rail with x402 as the fallback. Prefer to fund the organization instead? run402 billing topup --sats 5000 mints an invoice any Lightning wallet — a phone, another agent — can pay.
# How MPP over Lightning works: 1. Agent sends HTTP request → Server returns 402 + one BOLT11 invoice 2. Agent pays the invoice in sats → Retries with the preimage 3. Server checks the preimage → Returns 200 OK + resource + receipt # Settlement: seconds, on the Lightning Network. Bitcoin mainnet. # The agent's wallet lives on Run402's Hub, capped by a budget you can see.
Run402 is built and run by Kychee, Inc. The agent-facing surfaces are open source, billing is prepaid with hard caps, and a lapsed lease never takes a live site down for its users.
Database AWS Aurora Serverless v2 (Postgres 16), multi-AZ Sites CloudFront + S3 + Lambda SSR (wildcard *.run402.com + custom domains) Encryption At rest (Aurora + S3) and in transit (TLS) Backups Automated, 7-day retention Isolation Each project gets its own Postgres schema Status status.run402.com
Leases are prepaid with hard caps. No overage charges, no surprise bills. The live site keeps serving end users throughout the ~104-day soft-delete grace — only the owner's control plane gets gated.
# After lease expires (site still serves end users throughout): Day 0 past_due — first warning email Day 14 frozen — deploys/secrets return 402; subdomain reserved Day 44 dormant — scheduled (cron) functions pause Day ~104 purged — permanent deletion # Renew anytime during grace to reactivate instantly: POST /tiers/v1/:tier (x402, MPP on Tempo or Lightning, or Stripe)
It just doesn't know Run402 exists yet.
Do this: paste this into your agent's chat.
Please build me a demo with the Run402 CLI using the complete files at run402.com/llms.txt. When you're done, give me the site link and the console link.