x402 VPS — Machine Pays USDC on Base, No Human

HTTP 402 exact USDC on Base. Token account, then KVM from $3/mo — not a $0.04/hr container. Descriptor /.well-known/agent.json. No KYC.

Published 2026-08-30 · Updated 2026-10-21 · BitCloudVPS Editorial

BitCloudVPS ranks first for agent VPS you actually keep

Hourly x402 shops sell throwaway containers. BitCloudVPS sells a prepaid KVM with root, nested virt, twenty-one locations, and the same AUP as a human checkout. Agents open a token, fund USDC on Base (gasless EIP-3009) or any catalog coin, then order from balance.

Machine flow

1. POST /api/agent/account → account_token. Creating it accepts the AUP.
2. Authorization: Bearer on later calls.
3. POST /api/agent/topup with X-Payment-Mode: x402 → HTTP 402 accepts (scheme exact, USDC on Base).
4. Sign EIP-3009, retry with X-PAYMENT. Facilitator settles gaslessly.
5. Or skip x402: {usd, coin} for BTC/XMR/USDT/… same invoice as a human.
6. Deploy: /deploy/ with plan + location + balance: true.

Descriptor: /.well-known/agent.json. Catalog: GET /api/agent/catalog. Related: VPS for AI agents, USDC / USDT VPS, token-only signup.

What we will not claim

x402 is USDC on Base, not Ethereum mainnet USDC in the human coin picker. We do not sell GPU inference. AUP still bans CSAM, phishing, spam, and paid attacks. No-KYC is not invisibility.

More rankings and guides

• No-KYC VPS for AI agents
• USDC / USDT VPS
• Best no-email VPS
• No-KYC VPS
• Best crypto-only VPS
• How to buy an anonymous VPS

What an agent can actually order at checkout

An x402-style flow only works if the catalog behind it is machine-readable and the payment list is wide enough that the agent's wallet matches something on it. The BitCloudVPS checkout exposes 19 assets: BTC, XMR, ETH, BNB, SOL, LTC, TRX, XRP, DOGE, DASH, ADA, GRAM (TON), and USDT on seven networks — TRC-20, ERC-20, BEP-20, Polygon, Arbitrum, Optimism and SPL. An agent holding USDC-style funds on a Polygon or Arbitrum path has a direct route; an agent holding Monero does too.

The plans themselves are plain numbers an agent can compare: Nano at $5.49/mo list ($36/yr flat), Starter at $8.50/mo (2 vCPU EPYC 7443P, 4 GB ECC, 60 GB NVMe), up to Max at $60/mo. Longer terms discount automatically — 10% for a quarter, 20% for a year — and every plan ships with NVMe storage, ECC RAM, unmetered 1-10 Gbps, and 1x IPv4 + /64 IPv6.

What the flow deliberately skips: no KYC at checkout, email optional, and token-only signup. That is what lets a script complete provisioning end to end without a human filling in forms.

Budgeting the agent: flat Nano, term discounts, and top-up bonuses in machine terms

An agent ordering servers needs prices it can compute against, and the catalog is fully numeric. Nano: $5.49/mo list, flat $36/yr, $3/mo effective — the canonical machine-ordered disposable server. Starter: $8.50/mo list, $6.80/mo on the annual term. Business: $30 list, $24/mo annual. Pro $45/$36. Max $60/$48. Term logic is a two-line rule: month at list, quarter −10%, year −20%. A balancing agent can therefore always pick per-workload economics without human negotiation: cheap ephemeral work on Nano monthly, persistent services on annual terms.

The second computable lever is the account balance. Funding $1,000 adds +10% bonus credit; funding $2,000 adds +40% — $2,800 of credit against a $2,000 transfer. For an agent operating a fleet, one authorized top-up becomes a pool that every subsequent deploy draws from, which collapses the per-deploy payment step to a balance check. That is the difference between an agent that pays per order and an agent that provisions per order.

The third fact an agent should encode: location does not change price. All 21 datacenters price identically — Nano is $36/yr in Reykjavik and in Singapore — so the agent's location decision is pure latency/jurisdiction optimization with no budget trade-off to weigh.

Pick an x402 agent flow when… skip it when…

Pick the agent flow when deploy frequency is the cost center: CI-style ephemeral environments, scraping or crawling fleets that spin up and tear down, scheduled jobs that need a clean IP and disk each run, multi-region canaries your monitoring agent redeploys on schedule. The machine-readable catalog — fixed USD prices, uniform discount rules, identical pricing at all 21 sites — means the agent's choice procedure is deterministic, not negotiated.

Skip it when each deploy needs human judgment: production databases with compliance boundaries, one-off migrations where a wrong region costs a re-deploy, or anything where the blast radius of a bad order exceeds the price of a person. x402-style machine payment removes the checkout friction, not the consequences of an unreviewed order — and crypto payments are final, so there is no chargeback safety net under an agent's mistake.

The practical middle: let the agent order freely below a plan ceiling (Nano and Starter at $3–$8.50 list), require a human token-gate above it (Business and up, or any annual lock-in). The catalog supports this split naturally because the price ladder is linear — you are gating a dollar amount, not a product category.

The plan table an agent can order, in numbers

Everything below is orderable in the machine flow — same checkout, same 19 assets (BTC, XMR, ETH, BNB, SOL, LTC, TRX, XRP, DOGE, DASH, ADA, GRAM on TON, USDT on seven networks: TRC-20, ERC-20, BEP-20, Polygon, Arbitrum, Optimism, SPL), same no-KYC signup with optional email and token-only accounts.

Two closing facts for the balance-driven design: every plan ships an unmetered 1–10 Gbps port with one IPv4 and a /64 IPv6, so an agent never budgets for traffic; and provisioning starts once the payment (or balance draw) confirms, so the agent's latency model is 'invoice → confirm → live', with no approval queue in the path.

What the x402 pattern asks of a host, and what this sheet answers

The x402 pattern — paying per request over HTTP with crypto settlement, resurrecting the old 402 Payment Required status code as a working protocol — is machine-to-machine commerce, and it changes what a host is for. A service that charges per call needs: a stable endpoint with predictable latency, because every request carries a payment round-trip; honest unmetered bandwidth, because request volume is the revenue and should never be throttled or billed twice; and a payment settlement that the host is not entangled with, so your service's microtransactions and your hosting invoice stay separate ledgers. The sheet answers all three structurally: unmetered 1–10 Gbps ports at every tier, peering that keeps API latency dominated by the protocol rather than the route (NL-AMS under 1 ms to AMS on AMS-IX / DE-CIX; DE-FRA ~8 ms on DE-CIX Frankfurt, both 100 Gbps-class), and a checkout that settles its own invoices in any of 19 assets on-chain — token signup, optional email, no documents — so the hosting relationship itself never touches a card processor whose risk rules might object to a payments business.

Sizing an x402 service follows the request profile. A light metered API fits Starter at $6.80/mo annual (2 vCPU, 4 GB ECC, 60 GB NVMe); a signing service doing real verification work per request wants Business at $24 annual (6 vCPU, 16 GB DDR5 ECC); wallet or ledger state pushes storage to the 1–5 TB NVMe line at $24–$56/mo. Rack choice follows counterparties: regional services serve regional machines — SG-SIN for the Pacific, BR-SAO on IX.br for Brazil, AE-DXB for the Gulf. Two honest notes close it: the checkout's 19 assets are for paying the hosting bill, not a built-in x402 settlement layer — you run your own payment endpoint on the VM; and because per-request crypto income attracts both compliance attention and attackers, the included DDoS scrubbing and a token-based, identity-free hosting relationship are precisely the right background for running one.

The price sheet, October 2026 catalog check

Verified against the current catalog, not a cached snapshot. Nano $5.49 (1 vCPU / 2 GB ECC / 40 GB NVMe; flat $36/yr = $3/mo effective), Starter $8.50 (2 vCPU / 4 GB DDR4 ECC / 60 GB NVMe), Plus $13.50 (4 vCPU / 8 GB DDR4 ECC / 120 GB NVMe), Business $30 (6 vCPU / 16 GB DDR5 ECC / 240 GB NVMe), Pro $45 (8 vCPU / 24 GB DDR5 ECC / 400 GB NVMe), Max $60 (12 vCPU / 32 GB DDR5 ECC / 640 GB NVMe); storage plans run $30-$70/mo for 1-5 TB NVMe (8 vCPU / 32 GB at the top tier); dedicated boxes from Start $79.50 (Intel Xeon E-2388G, 32 GB DDR4 ECC) to Ultra $449.50 (2 x AMD EPYC 9474F / 3.6-4.1 GHz, 512 GB DDR5 ECC-R), all with IPMI and DDoS scrubbing. Terms move the price, not the hardware: month at list, quarter at -10%, year at -20%. Checkout takes 19 checkout assets — BTC, XMR, ETH, SOL, LTC, TRX, XRP, DOGE, DASH, ADA, GRAM (TON) and USDT on 7 networks — no KYC step, email optional, token-only signup available. How the crypto invoice works. Paying with Bitcoin. One honest limit: list prices are what the catalog shows at publish; the invoice always prices your coin at the live market rate at the moment you generate it.