AI Agents Need Network Privacy Too
Every request an AI agent makes exposes an IP address — traceable, fingerprintable, blockable. Traditional VPNs require accounts, passwords, and a GUI. An agent can't click "Connect" or enter a 2FA code.
Agents need programmatic access with zero friction — a VPN that speaks HTTP, not UI.
x402 brings HTTP 402 Payment Required to life. An agent sends a request to a proxy or VPN endpoint. The server responds with 402 and includes payment details — amount, USDC wallet address, and a payment ID on Solana. The agent pays, attaches the proof, and gets instant access. No API keys, no OAuth, no accounts. Money in, access out.
How It Works
No browser, no human in the loop:
- Agent sends a request to the AkcaVPN proxy endpoint
- Server responds with HTTP 402 + payment details (amount, wallet, payment ID)
- Agent pays USDC on Solana
- Agent re-sends the request with proof in the
X-PAYMENTheader - Server verifies on-chain and grants access
The payment is the authentication. No signup, no accounts.
SDK & MCP Server
Two integration paths: SDK for direct programmatic control, or MCP server for Claude and other AI assistants.
fetch with automatic 402 payment handling
Pricing
Pay only for what you use. Proxy: 0.001 USDC/request. VPN: 0.50/24h, 2.00/7d, 6.00/30d. All on Solana — sub-second finality, near-zero fees.
Give Your Agent Network Privacy
Integrate x402 in minutes. Your agent pays per request. No accounts, no API keys.
View x402 Docs