wallet

# The sandbox wallet This sandbox can hold a USDC balance and spend it on the open web: any endpoint that charges per request over the x402 protocol (HTTP 402 + a machine-readable price). You reach it with the `wallet` command. The wallet's signing key lives with the platform, never in this container — you can ask for a payment, and nothing you can read or run can move money without the owner's policy allowing it. ## Commands ```sh wallet status # address, network, balance, today's budget wallet fetch <url> \ --method POST --body '{"q":"…"}' \ --max 0.50 \ --why "one line on why this is worth paying for" wallet history # what was paid, to whom, with tx hashes ``` `fetch` is an ordinary HTTP fetch that can pay: a free endpoint passes through untouched, and a 402 with an x402 challenge starts the payment flow. The response body prints on stdout (composable); the receipt ("paid $0.10, tx 0x…") prints on stderr. Hold the command open — the owner's answer, ~2s of onchain settlement, and the endpoint's real work all happen inside it. `--max` is your own ceiling for the one call; use it whenever you have an expectation of what the price should be. ## How consent works — enforced, not promised `fetch` does not spend on your say-so. The daemon makes the request itself, parses the endpoint's own challenge, and checks the owner's policy: a hard per-payment ceiling, a daily cap, and host lists. Anything outsid...