Ownership

Free status reads for every project.

Reading project status and deployment history on x402-hosting costs nothing. Only the operations that change something — deploy, renew, rollback, transfer, delete — carry a payment. The service is built in Amsterdam, deploys take one command, hosting runs $0.20 per project-day, and no account is involved in any of it.

Status reads cost nothing

The status command returns the project's URL, owner wallet, expiry, and current deployment. With --json the output is machine-readable, so a script or an agent can parse it directly instead of scraping text.

$ npx x402-hosting@latest status --json

Because the read is free, checking a project a hundred times a day costs the same as checking it once: zero. There is no read quota and no API key metering the requests. The command reads the record written by the first deploy, x402-hosting.json, so it works from the project directory with no extra flags.

Deployment history for scripts and agents

The deployments command lists past deployments. Use --limit to cap the list, --all to fetch the full history, and --json for structured output.

$ npx x402-hosting@latest deployments --all

Each entry in the history is also the identifier a rollback needs, so a recovery script can read the list, pick a known-good deployment, and act on it without any paid call in between.

Free monitoring loops

A monitor that polls status --json on a schedule can track expiry across many projects at no cost. The natural pattern is a cron job or an agent loop that reads every project daily and warns when expiresAt approaches. Nothing on the platform side charges for that polling, and nothing requires authentication, because status is public information about a public URL. The same loop can detect an expired project inside its 30-day grace window, where a renew still republishes at the same URL — so free reads are also the early-warning system for recovery.

Only mutations are paid

The paid surface is deliberately small. Deploying is the one that starts a project:

$ npx x402-hosting@latest deploy --days 30
  • First deployment: $0.01 upload plus $0.20 × project-days
  • New deployment at the same URL: $0.01
  • Renewal: $0.20 × additional project-days
  • Rollback, ownership transfer, or deletion: $0.01
  • Status and deployment-history reads: free, always

Why free reads matter for ownership

The wallet that pays the first upload owns the project, and every later paid mutation must settle from that same wallet. Free reads complete that model: the owner can verify state before paying for anything, and anyone else — a teammate, a monitor, an agent evaluating the project — can confirm what is live without holding the wallet. Verification is a read, reads are free, and paid actions stay rare and deliberate. The full price list is on the pricing page.

Related guides