All systems operational 12 elite locations · Europe & Asia Pay with crypto · 0 KYC
Home / x402 VPS: fund autonomous agents with USDC on Base
Product · Payments

x402 VPS: fund autonomous agents with USDC on Base

VPSbit KVM still: frontal rack with six status-LED units

Fund a persistent KVM with USDC on Base over HTTP 402 — sign EIP-3009 yourself, no facilitator, no KYC. Plans from $4.80/mo across 12 locations.

Short answer

Fund a persistent KVM with USDC on Base over HTTP 402 — sign EIP-3009 yourself, no facilitator, no KYC. Plans from $4.80/mo across 12 locations.

12 locations · 19 coins · SLA 99.95% · no KYC · public canary

VPS from $4.80* — Core on the annual term (list $6/mo), one invoice for 12 months, no auto-charges. Dedicated with IPMI from $39.20/mo. Crypto invoice, no KYC.

Launch now

Prepaid KVM instead of per-hour containers

The per-hour side of the x402 market rents compute like a taxi meter. x402vps.com lists Docker containers from $0.04 per hour and keeps them alive only while the lease renews; OpenVPS-style hosts slice microVMs at pennies per hour and tie each one to a duration parameter; BitVPS sits lower still, flagged as untrusted by review aggregators. If your agent holds session state, a warm model cache or a long-running worker, a box that can vanish between heartbeats costs you twice: once in rebuild time and once in the glue code needed to survive it.

VPSbit runs the opposite lane: a prepaid KVM that stays provisioned until you cancel it. You get root access, nested virtualization where the workload needs it, and a choice of twelve locations under one AUP shared with the human checkout. Entry is Core at $4.80 per month on the annual term — list price $6.00 — covering 2 vCPU of a Ryzen 9 9950X, 4 GB of DDR5, 80 GB of NVMe and an unmetered 1 Gbps port. The table below lines the approaches up side by side, and the rest of this page walks the exact API sequence your agent runs.

HostWhat 402 gets youHow long it stays yours
VPSbitReal KVM, Core from $4.80/mo annual-effYours until cancelled
x402vps.comDocker container from $0.04/hrHour-by-hour lease
OpenVPS-style hostsMicroVMs at pennies per hourBound to a duration parameter
BitVPSListed, but flagged untrusted by review aggregatorsNot a dependable base

The sequence a machine executes, call by call

Everything runs over plain HTTP; no browser and no SDK take part, and CORS stays open across the agent endpoints. The machine-readable contract sits at /.well-known/agent.json, and GET /api/agent/catalog lists every plan, price and location on sale. Your agent opens an account with POST /api/agent/account, which mints an account_token — accepting the AUP is built into that mint, not a separate checkbox. Every call that follows carries the token as Authorization: Bearer, the same header pattern any HTTP client already speaks.

Funding goes through POST /api/agent/topup with the X-Payment-Mode: x402 header set. The 402 response answers with an accepts block naming the scheme: USDC on Base. Your agent then places an EIP-3009 signature on transferWithAuthorization and broadcasts it to the USDC contract over any Base RPC it prefers — public endpoints are listed inside the settlement block of the 402 itself. The x402 protocol documents the payment wrapper, and the gas bill — cents of ETH on Base — stays with the sender.

The retry closes the loop. Your agent calls the same top-up endpoint again, now carrying X-PAYMENT plus payload.txHash for the broadcast transaction. The signature and the receipt get checked, and the USDC lands at the receiving address directly — no facilitator and no relayer wallet sits in between, so there is no third party to trust or to time out. From there the flow ends at /deploy/ with plan, location and balance: true, and the machine typically reaches SSH about 60 seconds after payment. Base docs cover the RPC details if your stack needs them.

The plan ladder one balance buys

Whatever funded the balance, it spends against the same three-tier list. Core is the floor: $6.00 list / $4.80 annual-eff, built on 2 vCPU of a Ryzen 9 9950X at 4.3-5.7 GHz with 4 GB of DDR5, 80 GB of NVMe and an unmetered 1 Gbps port. Prime doubles the shape at $12.00 / $9.60 — 4 vCPU, 8 GB, 160 GB, 2.5 Gbps. Titan tops the ladder on an AMD EPYC 9354P: 8 vCPU, 32 GB of ECC DDR5, 320 GB of NVMe and 10 Gbps at $24.00 / $19.20.

PlanCPUMemoryStoragePortList /moAnnual-eff /moDeploy
Core2 vCPU, AMD Ryzen 9 9950X (4.3-5.7 GHz)4 GB DDR580 GB NVMeUnmetered 1 Gbps$6.00$4.80Deploy Core, pay in USDC
Prime4 vCPU, AMD Ryzen 9 9950X (4.3-5.7 GHz)8 GB DDR5160 GB NVMeUnmetered 2.5 Gbps$12.00$9.60Deploy Prime, pay in USDC
Titan8 vCPU, AMD EPYC 9354P (3.25-3.8 GHz)32 GB DDR5 ECC320 GB NVMeUnmetered 10 Gbps$24.00$19.20Deploy Titan, pay in USDC

Every row above links into the deploy flow with the plan preselected, so an agent can walk from catalog to running box without a human touching a keyboard. Annual terms run 20% under list at all three tiers; quarterly terms run 10% under instead. When a fleet outgrows slices entirely, the same balance reaches dedicated metal: Forge, a 16-core/32-thread Ryzen 9 9950X machine with IPMI and twin 1 TB NVMe drives, opens at $49.00 list / $39.20 annual-eff, and the EPYC tiers climb from there to Monolith at $119.20 with 25 Gbps.

Why prepaid beats per-hour for an agent fleet

State is the whole argument. An agent that checks in twice a day — a trading loop, a crawler, a monitoring watcher — needs its process, logs and cache to survive between runs. On an hourly container, every restart means re-provisioning and hoping nothing was mid-write. On a prepaid KVM the $4.80 Core slice simply persists: your units come back up, the disk keeps its blocks, and the IPv4 address stays assigned to the plan for as long as you keep it active.

The funding path also has a fallback worth knowing before you depend on it. The x402 rail can be skipped entirely: a top-up call carrying {usd, coin} — BTC, XMR, USDT on any of its seven networks, or any of the nineteen catalog coins — returns the same invoice a human would see, credited through the same watcher. The smallest top-up is FUND_MIN from the catalog, usually $20 in prepaid credit. Whichever lane funds the balance, the catalog behind it and the AUP above it stay identical — one checkout, one rulebook, whichever signature paid it. For a fleet that funds itself, that sameness is the quiet feature: the invoice the machine sees is byte-for-byte the invoice a person would see, against the same three-tier list and the same twelve-city map.

Nineteen coins behind one balance

USDC on Base is the native 402 scheme, and the checkout takes nineteen coins in total. XMR is first-class here: an agent that prefers Monero sends coin=XMR on the same top-up endpoint and the watcher credits the balance once the transaction confirms. USDT invoices run on seven networks — TRC-20, ERC-20, BEP-20, SPL, Polygon, Arbitrum and Optimism — and BTC, ETH, SOL, LTC, BNB, TRX, XRP, DOGE, DASH, ADA and GRAM (TON) fill the rest of the list. Every invoice is quoted in USD at the live rate the moment it opens, so a prompt send prices at the rate you saw.

USDT VPS maps the stablecoin routes across all seven networks, and the no-email account needs no guide of its own: the 32-character token minted at POST /api/agent/account is the whole identity, an email plus a 12-character password is the only alternative, and neither carries a passport, a phone number or a card. Identity collection is absent from the checkout by design, and payload or guest traffic is not logged, with connection metadata kept at most 24 hours. What the coin choice changes is the wire format of the deposit and its fee. The ladder, the twelve locations and the rules above them do not move.

Where the box lands: twelve cities, four premium flags

The catalog is deliberately narrow: twelve locations, each a named facility with a published tier, uplink and governing law. Reykjavik runs Tier IV with N+1 redundancy, a 10 Gbps uplink and FICIX peering under Icelandic law, which carries no mandatory data retention. Amsterdam (Tier III+, 2N, 40 Gbps, AMS-IX and DE-CIX) and Frankfurt (Tier III+, 100 Gbps, DE-CIX Frankfurt) anchor the EU under GDPR. Zurich holds a Tier IV / 2N+1 floor on 100 Gbps under the Swiss FADP. Tokyo runs 100 Gbps with JPIX and JPNAP peering under the APPI; Singapore (SGIX, PDPA), Hong Kong (HKIX) and Taipei (TWIX) cover the region at 40 Gbps each.

Scarcity is a feature here, not an apology: these twelve passed the bar and nothing outside the list gets sold. Four flags carry a published premium — Reykjavik +20%, Zurich +35%, Oslo +20%, Luxembourg +15% — while the other eight price at base list. Your agent reads the whole map from GET /api/agent/catalog before spending a cent, which turns location choice into a line of code rather than a support ticket. Stockholm (NetNod, press-freedom tradition), Helsinki (FICIX), Oslo (NIX, EEA GDPR) and Luxembourg (LU-CIX, data-trust regime) complete the northern tier on 20-40 Gbps uplinks.

The honest section: what x402 VPS will not do for you

Start with no-KYC, because this market oversells the term constantly. It means the checkout collects no passport, no phone number and no card — an account is a 32-character token, or an email backed by a 12-character password. It does not mean your traffic becomes unattributable. Your machine carries an IPv4 address, that address is registered to your token in the provider records, and an abuse report against it resolves to your account in one lookup. Paying in USDC — or in XMR, or any of the other seventeen coins — changes the settlement rail, not that mapping. The 402 flow automates payment; it does not erase identity.

The rule set does not bend for machines, either. One AUP governs every checkout path — the token an agent mints and the email a human types — and it bans CSAM, phishing, spam and network attacks outright. Abuse is handled under the law of the facility location: a box in Frankfurt answers to German and EU law, one in Tokyo to the APPI, one in Singapore to the PDPA. A DMCA notice that arrives at a facility is logged and answered with a template acknowledgement — bookkeeping, not a legal ruling — and repeat valid complaints against your IP end with the account, exactly as they would on any host that intends to keep its uplinks.

Two more limits deserve the fine print. First, the 402 rail settles USDC on Base and nowhere else — the human coin picker has no Ethereum-mainnet USDC option, so if your treasury sits on mainnet you either bridge tokens or pick another coin. Second, GPU inference is not sold: these are CPU machines from the $4.80 Core slice to the Monolith and its dual EPYC 9554P chips. And the catalog is twelve locations — there is no thirteenth city closer to your users that a sales call could unlock. What GET /api/agent/catalog returns is the entire map, and that closure is what keeps the quality bar where it is.

Twelve locations, nineteen coins, one USDC rail from $4.80

That is the whole proposition in one line: a prepaid KVM your agent funds itself over HTTP 402, priced from $4.80 per month annual-eff, hosted in one of twelve elite facilities, settleable in USDC on Base or any of nineteen coins. The descriptor at /.well-known/agent.json is live, the catalog endpoint answers without a browser, and the same AUP that governs a human checkout governs the machine that never opens one. When slices give way to real workloads, Forge metal waits from $39.20 annual-eff with IPMI on the board.

Open the deploy page, mint the token, sign the transfer and watch the balance post — twelve cities from Reykjavik to Taipei, three VPS tiers from $4.80, three dedicated tiers from $39.20, one payment rail your code already speaks. If the USDC lane ever feels heavy for a small top-up, the fallback is one JSON field away: {usd, coin} with BTC, XMR or LTC posts the same balance, and FUND_MIN sits near $20. No KYC form stands on the path, and no hourly lease waits behind the machine once it boots.

Is a browser needed anywhere in the x402 flow?

No. Plain HTTP with a bearer token covers the whole path — account minting, top-ups, catalog reads and deploys — and CORS stays open across the agent endpoints, so a server-side agent calls them directly without any frontend in the middle.

What is the smallest top-up an agent can make?

The same floor the human checkout uses: FUND_MIN from the catalog, usually $20 in prepaid credit. Either funding lane — x402 USDC on Base or a plain coin invoice — ends at the same deploy screen with the balance credited.

Can an agent pay in XMR instead of USDC?

Yes. Call POST /api/agent/topup with coin set to XMR — or to any of the other eighteen catalog coins — and the watcher posts the credit once the transaction confirms on its own network. The x402 wrapper is optional, not mandatory.

Does the AUP bind agents the same as humans?

One policy governs both checkout paths. Whoever or whatever pays, CSAM, phishing, spam and network attacks stay banned, and abuse is handled under the law of the facility location — there is no separate, softer regime for machine signups.

Where does the gas for a 402 payment come from?

From your side of the trade, paid in ETH on Base — typically cents per settlement. The agent signs the EIP-3009 transfer and broadcasts it itself over any Base RPC it likes, and public endpoints are listed inside the 402 settlement block.

Primary sources

Ready to launch?

Build the box — VPS or bare metal — create the password, pay the invoice that follows.