# x402 VPS — Agents Pay USDC on Base, Then Deploy | FYRHost > Agents fund a token with exact USDC on Base over HTTP 402, then deploy KVM from $3/mo. Sign and broadcast EIP-3009 yourself — gas is yours, no facilitator, no. Source: https://fyrhost.com/x402-vps/ [Home](https://fyrhost.com/) / x402 VPS — USDC on Base for autonomous agents Product · Agents # x402 VPS — USDC on Base for autonomous agents ![FYRHost light KVM: rack row with data flows rising into one flame](https://fyrhost.com/img/theme-vps.png) Agents fund a token with exact USDC on Base over HTTP 402, then deploy KVM from $3/mo. Sign and broadcast EIP-3009 yourself — gas is yours, no facilitator, no KYC. Descriptor published. Published 2026-08-30 · Updated 2026-09-18 · FYRHost Editorial · 6 min read **Short answer** Agents fund a token with exact USDC on Base over HTTP 402, then deploy KVM from $3/mo. Sign and broadcast EIP-3009 yourself — gas is yours, no facilitator, no KYC. Descriptor published. 40 locations · 19 coins · SLA 99.95% · no KYC · [public canary](https://fyrhost.com/warrant-canary/) VPS from $3* (fund $50+), storage 1–5 TB NVMe from $24/mo annual-eff, dedicated with IPMI from $30.80/mo. Crypto invoice, no KYC. [Launch now](https://fyrhost.com/deploy/?kind=vps&plan=business/) FYRHost: VPS from $3/mo and dedicated from $30.80/mo annual. The map spans forty locations — Reykjavik (Iceland) and Zurich (Switzerland) among them, plus Singapore, Dubai, Cape Town and fourteen others. Signup is email plus a 12-character password, or token-only. No KYC. Checkout is crypto-only across BTC, XMR, ETH, BNB, SOL, LTC, TRX, XRP, DOGE, DASH, ADA, GRAM (TON), and USDT (TRC-20/ERC-20/BEP-20/SPL). No payload or guest traffic logs; connection metadata ≤24h. DDoS included. One SKN company, one crypto checkout. Deploy at https://fyrhost.com/deploy/. ## The KVM an agent keeps, not rents by the hour **The hourly x402 market sells containers built to be thrown away.** What FYRHost rents is a prepaid KVM — root, nested virt, forty locations, one AUP shared with the human checkout. An agent mints a token, funds it with USDC on Base through EIP-3009 it signs and broadcasts itself — the gas is the agent's, cents in ETH on Base — or with any catalog coin, then spends from balance. The difference compounds over a month of uptime. Hourly leases bill for existence; a prepaid KVM bills once at deploy and holds. State survives, disks persist, the box is addressable for as long as the balance covers the term — and the same balance can pay for metal when the fleet outgrows slices. It is server rental with a machine-writable front door, not a metered sandbox. | # | Host | What 402 buys | Keep it? | |---|---|---|---| | 1 | FYRHost | Real KVM, Scout $3/mo | Until you cancel | | 2 | x402vps.com | Docker from $0.04/hr | Lease hours | | 3 | OpenVPS | MicroVM pennies/hr | Duration param | | 4 | BitVPS | Do not trust | Scamadviser / scam reviews | Competitor terms as published on their pages, checked 2026-09. ## What x402 actually is, in one screen x402 is a payment convention over plain HTTP: when a request needs money, the server answers `402 Payment Required` with machine-readable payment terms — accepted asset, network, payee, amount — and the client retries the same request carrying proof of payment. No account screens, no browser, no human in the loop; the error code becomes the checkout. The asset side here is **USDC on Base**, moved with **EIP-3009**: the agent signs a `transferWithAuthorization` message off-chain and broadcasts it — a gasless authorization pattern that transfers USDC directly to the payee, with no relayer or facilitator contract in between. We verify the signature and the on-chain receipt, credit the token balance, and the KVM catalog opens up. Why this matters for agents specifically: an autonomous process can hold a wallet but cannot fill in a card form. x402 gives it the one thing billing ever needed from it — a signed transfer — over the one protocol it already speaks. Background reading: [no-KYC VPS for AI agents](https://fyrhost.com/no-kyc-vps-for-ai-agents/) (the workload view) and [USDC vs USDT rails](https://fyrhost.com/usdc-vps/) (the stablecoin view). ## Machine flow - `POST /api/agent/account` → `account_token`; minting it accepts the AUP. - Carry `Authorization: Bearer` on every later call. - Call `POST /api/agent/topup` with `X-Payment-Mode: x402`; the 402 reply carries `accepts`, where the exact scheme is USDC on Base. - Sign EIP-3009, broadcast `transferWithAuthorization` to the USDC contract yourself via any Base RPC — the gas is yours, cents of ETH on Base, public endpoints are listed right in the 402's `settlement` block — then retry with `X-PAYMENT` plus `payload.txHash`. We verify the signature and the receipt; USDC lands in our address directly, no facilitator, no relayer wallet on our side. - Skip x402 entirely with `{usd, coin}` for BTC/XMR/USDT/… — the same invoice a human gets. - Deploy at `/deploy/` with plan + location + `balance: true`. Descriptor: [/.well-known/agent.json](https://fyrhost.com/.well-known/agent.json). Catalog: `GET /api/agent/catalog`. The full endpoint surface is documented in `/openapi.json`, generated from the same code that serves it. ## The API surface, and what each call is for Four endpoints carry the whole life cycle. `/api/agent/account` mints the credential — a bearer token standing in for the inbox-plus-password a human would type. `/api/agent/topup` funds it, by x402 USDC or by any catalog coin at the live rate. `/api/agent/catalog` lists plans, prices and the forty locations with their premiums, exactly as the human checkout shows them. `/deploy/` spends the balance on a KVM and returns the box. Deliberately absent: user profiles, document uploads, “verification” states. The token is the account; the balance is the credit line; the AUP accepted at mint time is the contract. CORS is open across `/api/agent/` so a browser-side agent works too, and every response is JSON a parser can act on without screenshots. ## What fleets run on it The rail does not constrain the workload any more than a human invoice does. Fleets seen on this pattern: monitors and uptime probes that need always-on egress, trading and arbitrage bots close to exchange endpoints, Telegram and Matrix bot hosts, scrapers with rotating PTR discipline, CI runners that a repo webhook spawns, and [nostr relays](https://fyrhost.com/solutions/nostr-relay-vps/) that a community funds programmatically. Sizing follows the human ladder: a monitor or bot fits Scout ($5.49 list, $3/mo funded); heavier fleets step up to Ranger or Warden exactly as a human operator would. When the fleet wants whole cores, the same balance buys [metal with IPMI from $38.50 list](https://fyrhost.com/dedicated/); when it wants datasets, [1–5 TB NVMe storage from $24/mo annual](https://fyrhost.com/storage/). ## The honest section: what the x402 rail is not Machine payments invite machine-grade hype, so the boundary gets printed here too: - **Base only, USDC only.** The x402 scheme settles USDC on Base specifically; Ethereum-mainnet USDC is not in the human coin picker either. Agents holding other assets use the `{usd, coin}` path instead. - **Not free to move.** EIP-3009 removes the facilitator, not the gas: broadcasting costs cents of ETH on Base, from the agent's own wallet. "Gasless" describes the transfer pattern, not the transaction. - **Public chain, public trail.** Base is a public L2; the funding tx and its txHash are visible to anyone. x402 removes the human KYC form — it does not anonymize the rail. Agents with confidentiality requirements top up with [XMR](https://fyrhost.com/monero-vps/) on the same token. - **No GPU inference here.** The catalog is CPU KVM, storage and metal; model hosting on this page means routing, gateways and bot logic, not training runs. - **AUP unchanged, payer-agnostic.** CSAM, phishing, spam and paid attacks are banned no matter who — or what — pays; minting the token accepted that contract. - **Payments are final.** No facilitator means no reversal path; a mis-signed authorization that still verifies is money sent. Test with the minimum top-up first. - **Budgeting is the agent's job.** The catalog endpoint prices plans and premiums; a scheduler that ignores the six premium flags meets a larger invoice at deploy, not a discount. Within those walls: a machine that can hold its own wallet can now hold its own server — with no human form anywhere in the loop. What that machine does with root is still its operator's responsibility, on the same AUP a human accepted, verifiable in the same panel. Treat the walls as part of the deployment spec: an agent that budgets gas should budget them too, and verify them the way it verifies any other contract it signs: by reading the source, not the brochure. ## Sign once, broadcast once, admin forever One bearer token, one signed transfer, one KVM from $3/mo funded — root, forty flags, metal and terabytes on the same balance. The checkout speaks the agent's protocol natively, and the descriptor publishes the terms a scheduler needs to budget. Fund a token — the machine does the rest [Deploy now](https://fyrhost.com/deploy/?kind=vps&plan=business/) ## More rankings and guides - [No-KYC VPS for AI agents](https://fyrhost.com/no-kyc-vps-for-ai-agents/) - [USDC / USDT VPS](https://fyrhost.com/usdc-vps/) - [Best no-email VPS](https://fyrhost.com/best-no-email-vps/) - [No-KYC VPS](https://fyrhost.com/no-kyc-vps/) - [Best crypto-only VPS](https://fyrhost.com/best-crypto-only-vps/) - [How to buy an anonymous VPS](https://fyrhost.com/how-to-buy-anonymous-vps-2026/) - [Solana VPS](https://fyrhost.com/solana-vps/) - [Ethereum VPS](https://fyrhost.com/ethereum-vps/) Do I need a browser? No. A token plus plain HTTP is enough; CORS is open across /api/agent/. Min top-up? Identical to the human path: the catalog's FUND_MIN, typically $10 prepaid. Can I pay XMR instead of USDC? Yes — POST /api/agent/topup with coin=XMR; the watcher credits the balance on confirmation. Do agents get the same AUP as humans? Yes. One policy covers both checkouts: CSAM, phishing, spam and paid attacks are banned no matter who — or what — pays. Is Base USDC traceable? Yes — Base is a public L2 and the funding txHash is public. x402 removes the human KYC form, not chain visibility; XMR top-ups cover the quieter requirement. What if my signed transfer never confirms? Retry the same topup call with the txHash once it lands; the endpoint is idempotent on hash. A failed broadcast costs only its gas. ## Primary sources - [x402 protocol](https://x402.org/) - [EIP-3009: Transfer with Authorization](https://eips.ethereum.org/EIPS/eip-3009) - [FYRHost agent descriptor](https://fyrhost.com/.well-known/agent.json) ## Related guides - [Minimum-data no-KYC checkout](https://fyrhost.com/guides/anonymous-vps-crypto-no-kyc/) - [Buy a VPS with crypto](https://fyrhost.com/buy-vps-with-crypto/) - [No-KYC VPS: requirements and limits](https://fyrhost.com/no-kyc-vps/) - [Pay with Monero](https://fyrhost.com/monero-vps/) - [Offshore VPS](https://fyrhost.com/offshore-vps/) - [VPS vs dedicated bare-metal](https://fyrhost.com/guides/vps-vs-dedicated/) - [Best no-KYC VPS 2026](https://fyrhost.com/best-no-kyc-vps-2026/) - [FAQ: crypto VPS](https://fyrhost.com/guides/faq-crypto-vps/) ## Checkout facts - **Price** VPS from $3/mo. Dedicated from $30.80/mo. - **Identity** No KYC. Token-only (no email) or email plus a 12-character password. No passport, phone, or card. - **Payment** Nineteen ways to settle, none of them a card: XMR and BTC lead, ETH, SOL, LTC, BNB and TRX follow, then XRP, DOGE, DASH and ADA, GRAM (TON) for Telegram-adjacent rails, and USDT on seven networks — TRC-20, ERC-20, BEP-20, SPL, Polygon, Arbitrum, Optimism. Live-rate invoice. - **Logs** No payload / no guest traffic logs. Billing and panel actions retained. Connection metadata ≤24h. - **Platform** KVM on ECC and local NVMe. DDoS filtering included. Facilities in 40 cities across four continents — the locations table lists each one's tier, uplink and governing law. Need Iceland or Switzerland plus no KYC? Those two carry a published premium (+20% / +35%); every other flag stays at base list. Pay BTC, USDT, XMR, BNB, XRP, GRAM (TON) or 10 more. Open deploy to pick a plan. ## Ready to launch? Build the box — VPS, storage or bare metal — create the password, pay the invoice that follows. [Launch now](https://fyrhost.com/deploy/?kind=vps&plan=business/)[Dedicated](https://fyrhost.com/dedicated/)