Ownership
Transfer a live website to a new owner.
Handing off a live site on x402-hosting is one command and one $0.01 payment: transfer --to moves the project to another wallet immediately. The URL and the current deployment stay online throughout — ownership changes, hosting does not.
One command, no downtime
Because ownership on x402-hosting is cryptographic — the wallet that pays owns the project — transferring it means recording a new owner wallet, not migrating infrastructure. The site keeps serving from the same URL with the same deployment, and the prepaid time already on the project carries over. Nothing is rebuilt, repointed, or taken offline.
$ npx x402-hosting@latest transfer --to 0x0000000000000000000000000000000000000000 --yes
The --yes flag skips the confirmation prompt, which makes the operation scriptable. The $0.01 payment settles from the current owner wallet, and the HTTP 402 challenge quotes the amount before anything signs, as with every operation on the pricing page.
Use cases
Selling a project is the obvious one: the buyer gives you a wallet address, you transfer, and the deal is done at the infrastructure level. Agency handoff is the quieter one — build and host the site under the agency wallet during development, then transfer to the client's wallet at delivery, and the client owns renewals from that point. The third is internal: moving a project from a hot wallet to a colder one without redeploying.
In each case the mechanics are identical, because there is exactly one kind of ownership to move. The seller does not export anything, the buyer does not import anything, and neither side touches a DNS record or a deployment setting. The payment is the handoff.
Compare that with the conventional path: adding the buyer as a collaborator, transferring a repository, re-creating the project under their account, re-pointing the domain, and hoping nothing breaks in between. Here the project, the deployment, and the URL are indivisible, and they move together in a single atomic step.
What changes after the transfer
From the moment the transfer settles, only the new wallet can pay for mutations. Renew, redeploy, rollback, further transfers, and deletion attempted from the old wallet are rejected with wallet_not_owner. The x402-hosting.json record should move with the project so the new owner's tooling can find the URL, project id, and expiry. Reads stay free for everyone, as covered in the documentation.
Before you transfer
Two things are worth checking first. Confirm the destination address character by character — ownership is cryptographic, so a typo sends the project to a wallet nobody controls, and no support process can reverse it. And confirm the project's expiry with the free status command, so the new owner knows how much prepaid time they are receiving. The transfer itself takes one payment and one confirmation.
Key facts
- transfer --to 0x… moves ownership immediately for $0.01
- The URL and current deployment never go offline
- Remaining prepaid time carries over to the new owner
- After transfer, only the new wallet can pay for mutations
- The $0.01 payment must settle from the current owner wallet