CLI reference
x402-hosting transfer: command reference.
transfer moves ownership of a project to another wallet. It costs $0.01, paid from the current owner wallet, and takes effect immediately while the site stays online.
Synopsis
$ npx x402-hosting@latest transfer --to 0x742d35Cc6634C0532925a3b844Bc9e7595f2bD31 --yes
Run it from the directory holding x402-hosting.json. Because ownership is cryptographic, no account settings or support tickets are involved — the paying wallet simply changes.
Flags
--to <address>— required; a 0x-prefixed 40-hex-character EVM address, validated before any payment--yes— skip the interactive confirmation; without it the command asks you to typeyes, and refuses to run non-interactively--payer/--payer-cmd— how the $0.01 is signed, as on every paid command- Cost: $0.01 in USDC from the current owner wallet
What changes, what does not
The transfer is immediate. From that moment, the old wallet loses access and only the new wallet can pay for mutations — redeploy, renew, rollback, a further transfer, or delete. A payment attempted from the old wallet is rejected before settlement, so nothing is charged. The site itself is untouched: the URL, the current deployment, and the remaining prepaid time all carry over. The local x402-hosting.json is updated with the new owner address once the operation settles.
Why confirmation is required
Transfer is irreversible — there is no wallet-loss recovery — so the CLI asks for an explicit yes unless --yes is passed. Scripts and agents should pass the flag deliberately, not habitually.
When to use it
Three common cases: selling a live site, where the buyer's wallet takes over exactly as-is; handing a project from a development wallet to a company wallet at launch; and rotating keys by moving the project to a fresh wallet you control. In every case the buyer's or successor's first action afterwards is a free status read to confirm the new owner. See pricing for what the new owner pays to keep the project running.