Wallet runbook
Stdio MCP and the CLI can pay x402 challenges when a local EVM private key is configured. The hosted OAuth Worker never holds wallet keys. Without these variables, top-ups fall back to Stripe links and empty balances return the ordinary insufficient-credits 402.
Follow the sequence in order. Each step is a bounded operator action—not a promise that every deployment has x402 enabled.
Use a funded wallet intended only for agent spend. Do not reuse hot keys from other systems, and never paste the private key into chat or client config files that sync.
Set X402_EVM_PRIVATE_KEY to a 0x-prefixed 32-byte hex key, and optionally OFFLINECREATOR_X402_MAX_USD (default 50) as a per-payment USD cap.
Keep OFFLINECREATOR_API_KEY (or OAuth for remote MCP). x402 settles payment after identity; a wallet cannot become the account.
Run balance, then a bounded topup or generate. Confirm the client logs that the wallet is enabled and that payments above the cap are refused before signing.
Remote OAuth MCP does not custody keys; wallet settlement is for local agent environments.
OFFLINECREATOR_X402_MAX_USD refuses oversize challenges before the wallet signs.
If the server rail is off, topup can fall back to a human Checkout link (or force with --stripe).
Only in the agent or CI secret store that runs stdio MCP or the CLI. Never in Studio, the hosted OAuth Worker, chat transcripts, or committed files.
Fifty US dollars per payment unless you set OFFLINECREATOR_X402_MAX_USD to a positive number. Challenges above the cap fail before signing.
Humans stay on Stripe. Agents settle only with a local wallet and a spend cap. When the shape is unclear, start with the PAYMENT-REQUIRED diagnosis runbook.