x402 · HTTP-native payments for agents
Proxies your agent can buy mid-task.
Your agent reads the price, gets a 402 quote over plain HTTP, signs a USDC payment inside its budget, and receives working proxy credentials — all in one request loop. Residential, ISP, and mobile. No checkout. No human in the way.
curl https://www.vital-data.io/llms.txtWhy agents buy here
Built to be evaluated, priced, and purchased by software.
No checkout to babysit
Quote, payment, and credentials travel inside one HTTP loop. The task never blocks on a signup form or a card prompt.
Machine-readable everything
Pricing, products, and integration docs are published as plain markdown at stable URLs. An agent can evaluate Vital without rendering a single pixel.
Per-task economics
Residential data from $1.40/GB and it never expires. An agent can buy exactly what one job needs instead of committing to a subscription.
Spend stays governed
The agent pays from a wallet you fund and scope. Every 402 quote is checked against its policy before a signature exists — overspend is structurally impossible.
How it works
Three steps to a proxy, zero humans in the loop.
Request what the task needs
The agent picks a proxy type, location, and quantity from /pricing.md and sends an ordinary HTTP request. No account bootstrap interrupts the task.
Settle the 402 in-band
Vital answers 402 Payment Required with exact, machine-readable payment terms. The agent verifies them against its spending policy, signs, and retries with the X-PAYMENT header.
Receive working credentials
Payment settles on-chain and the same request returns ready-to-use proxy credentials plus a settlement receipt. The task continues in seconds, not support tickets.
x402 payments
Give the agent a wallet, not a checkout.
Traditional billing stops an autonomous agent at the exact moment it needs to act: create an account, enter a card, wait for a person. x402 moves payment into the HTTP exchange itself — the 402 status code carries the price, the retry carries the signed payment, and the fulfilled response carries the receipt.
Control stays with you. The agent spends from a wallet you fund and scope, and it only signs quotes that pass its spending policy — everything else dies before funds move.
- 01 / Request
POST /purchaseThe agent asks for a paid proxy resource over ordinary HTTP — same verbs, same URLs, nothing proprietary.
- 02 / Quote
402 · accepts[]Vital responds 402 Payment Required with payment terms in the body: amount, asset (USDC), network, and the address to pay.
- 03 / Pay
X-PAYMENT: <signed payload>If the quote fits its policy, the agent's wallet signs the payment and retries the identical request with the X-PAYMENT header attached.
- 04 / Fulfill
200 · X-PAYMENT-RESPONSEVital verifies and settles the payment, then returns proxy credentials with a settlement receipt in the X-PAYMENT-RESPONSE header.
POST /purchase HTTP/1.1{ "product": "residential", "quantity_gb": 5 } HTTP/1.1 402 Payment Required{ "accepts": [{ "asset": "USDC", "network": "base", "amount": "7.00", "payTo": "0x…" }] } POST /purchase HTTP/1.1X-PAYMENT: <signed payment payload> HTTP/1.1 200 OKX-PAYMENT-RESPONSE: <settlement receipt>{ "credentials": { "host": "…", "port": 8989, "username": "…" } }Machine-readable
Everything an agent needs, at a stable URL.
No JavaScript, no auth, no scraping our own site to learn about it. Plain markdown, curl-able, and kept current — start at llms.txt and follow the links.
llms.txt
Entry point: what Vital is, with links to every machine-readable page.
pricing.md
Full tier and volume pricing for all three products.
products.md
Residential vs ISP vs mobile — how an agent should choose.
docs/use-cases.md
Which product fits scraping, automation, SEO, and AI training.
docs/targeting.md
Country, region, city, and ISP targeting; supported protocols.
docs/session-control.md
Sticky vs rotating sessions and IP refresh control.
docs/authentication.md
How proxy credentials are issued and used.
x402 protocol
The open HTTP 402 payment standard this page is built on.
Questions agents askbefore they spend.
x402 is an open payment standard built on HTTP's 402 Payment Required status code. A server quotes a price in the 402 response, the client retries the same request with a signed crypto payment in the X-PAYMENT header, and the server settles it and fulfills the request. It turns any HTTP endpoint into something an autonomous agent can pay for without an account or a checkout page.
Residential (per GB, from $1.40), ISP (per static IP), and mobile (per GB) — across 180+ countries with country, region, city, and ISP targeting. Residential and mobile data never expires, so an agent can buy per task instead of per month.
Pricing is published as plain markdown at /pricing.md, products at /products.md, and integration docs under /docs/ — all linked from /llms.txt. An agent can fetch, parse, and compare cost against its budget before any request that costs money.
Fund a dedicated wallet with only what the agent may spend, then enforce policy before signing: per-request caps, per-task budgets, and an allowlist of approved services. Because x402 requires the agent's signature for every payment, a quote outside policy simply never gets signed — nothing moves without it.
Humans can create an account and buy with card or crypto in the dashboard. The x402 flow is designed so an agent can quote and pay programmatically; credentials come back in the fulfilled response. Either path ends in the same proxy network.