Ownership
Hosting with no account and no dashboard.
x402-hosting has no sign-up form, no password, no email verification, and no dashboard session. Every operation is an npx x402-hosting command or a plain HTTP call tohttps://api.x402-hosting.com. The identity behind a project is the wallet that pays for it, not a row in an account database.
No sign-up flow at all
There is nothing to register. You do not pick a username, confirm an email address, set a password, or recover anything by mail. The first time the service hears from you is the first deploy, and the first $0.01 upload payment both creates the project and binds its owner. Removing the account removes an entire category of failure: no lockouts, no expired sessions, no verification loops.
Every operation is a command or an HTTP call
Deploy, renew, rollback, transfer, and delete are CLI subcommands, and the same operations exist as HTTP endpoints for programs that prefer to speak to the API directly. There is no web console with a parallel set of features, so nothing is only reachable by clicking. If a human can do it in a browser, that is because the browser is not involved.
This also removes the usual account-adjacent chores. There is no team management, no seat pricing, no shared login to hand a contractor, and no session to expire halfway through a CI run. Access is defined by a wallet and a payment, both of which already exist wherever the work is happening.
Status checks are free
Reading a project never requires payment and never requires authentication beyond knowing the project:
$ npx x402-hosting@latest status
The deployments command lists deployment history the same way, and both accept --json for machine-readable output. Checking on a project costs nothing and leaves no trace.
The site itself follows the same rule. Key pages exist as markdown mirrors — /index.md, /pricing.md, /auth.md — alongside /llms.txt and an OpenAPI document, so a program can read the whole interface without rendering HTML. The dashboard is not hidden behind the CLI; it was never built.
The project record lives next to your code
A successful first deployment writes x402-hosting.json to the project root with the URL, project id, owner wallet, and expiry. It contains no secret, so it belongs in the repository. That file — not a dashboard — is where you look to answer "what is deployed, where, and until when". The machine-readable surfaces listed in the documentation extend the same idea to agents.
What "no account" means in practice
- No sign-up form, password, email verification, or session
- Every operation is a CLI command or a plain HTTP endpoint
- Status and deployment-history reads are free
- x402-hosting.json records the project next to the code
- The paying wallet is the only identity the platform knows