Ownership

Pricing explained: $0.20 per project-day.

Every x402-hosting price is a fixed USDC amount per operation: hosting costs $0.20 per project-day, prepaid, and a first deployment adds a one-time $0.01 upload payment. Thirty days costs $6.01 in total. There are no tiers, no metered surprises, and the canonical summary lives on the pricing page.

The full price table

  • First deployment: $0.01 upload plus $0.20 × project-days
  • Redeploy at the same URL: $0.01
  • Renewal: $0.20 × additional project-days
  • Rollback, ownership transfer, or deletion: $0.01 each
  • Status and deployment-history reads: free

The --days flag accepts 1 to 730 days, and renewal uses the same arithmetic without the upload payment. Every price is known before the operation starts.

Worked examples

$ npx x402-hosting@latest deploy --days 30

Seven days of hosting: $0.01 + (7 × $0.20) = $1.41. Thirty days: $0.01 + (30 × $0.20) = $6.01. A full year: $0.01 + (365 × $0.20) = $73.01. Extending an existing project is cheaper because the upload payment does not repeat: renewing for thirty more days is exactly $6.00. A redeploy during the paid period costs $0.01 and does not extend the expiry.

What is included

Each active project includes its static assets, 100,000 dynamic requests, and 15 million CPU milliseconds. That covers server components, route handlers, and server actions in production — the price is the same whether the app renders static pages or runs full-stack logic. There is no separate bandwidth line item and no per-seat charge, because there are no seats.

What expiry costs

Letting a project lapse costs nothing — there is no stored card to charge. After expiry, a thirty-day grace window keeps the project recoverable: a renewal during grace republishes the same deployment at the same URL for $0.20 per additional day. After the grace window the project is gone, and starting over means a new URL and a new $0.01 upload payment. Immediate deletion, if you want it, is $0.01.

The payment challenge is the authoritative quote

deploy request402 payment challengeUSDC pays via x402site live
The x402 protocol turns a hosting invoice into an HTTP challenge a wallet can sign.

Prices on this page are stable, but the protocol does not ask you to trust a web page. Every paid operation begins with an HTTP 402 payment challenge from the API stating the exact amount and settlement network, and that challenge is the authoritative quote before any wallet signs. Local builds run before payment, so a build failure costs nothing. Once the $0.01 upload payment settles, it is not refundable if server-side publishing later fails — and a first deployment must activate within thirty minutes of that payment. If a payment client errors mid-operation, reconcile with finalize before paying again.

Key facts

  • $0.20 per project-day, 1–730 days per purchase, prepaid in USDC
  • 30 days costs $6.01 including the first-upload payment
  • Reads are free; every mutation is a fixed price
  • The 402 challenge quotes the exact amount before signing
  • No subscription, stored card, or automatic renewal

Related guides