Regional exits · Crypto-native · x402 protocol

Paid SOCKS5 access for humans and agents

Connect through eight global exit nodes. SOCKS5, HTTP CONNECT, and TLS on every exit. Pay with crypto, no accounts, no sales call.

No account, no email Global exit nodes Connect in seconds
Loading exits…
HealthyDegradedDownDisabled

Why x402socks.com

Built for privacy and autonomy

A proxy service that respects anonymity and works without friction for AI agents.

Instant access

Pay, connect, start within seconds — no account, no email, no sales call.

Crypto native

Payments via x402, USDC on Base, USDC on BNB Smart Chain, USDT on BNB Smart Chain, USDC on Ethereum, USDT on Ethereum. No credit cards, no bank accounts.

Agent optimized

Simple APIs and discoverable docs (llms.txt) built for autonomous agents.

High performance

Optimized SOCKS5 with minimal overhead and low-latency regional exits.

Flexible plans

Time or usage-based entitlements. Pay only for what you really need.

Proxy hop, not anonymity

The destination sees the exit, not your network. A forward proxy for egress — not an anonymity network or VPN.

Plans

Choose your access

All plans include global exit nodes, all three protocols on every exit, and crypto-native payments.

Multi-agent
Multi-Agent Month

30 days of shared access for up to 5 agents

  • Up to 300 GB fair-use data
  • All exit points
  • Up to 5 agents

$29.99

Buy now
Time
1 Day

24 hours of SOCKS5 proxy access

  • Up to 10 GB fair-use data
  • All exit points
  • 1 active session

$3.59

Buy now
Time
6 Hours

6 hours of SOCKS5 proxy access with up to 1 GB of data

  • Up to 1 GB data
  • All exit points
  • 1 active session

$1.00

Buy now
Time
7 Days

7 days of SOCKS5 proxy access

  • Up to 75 GB fair-use data
  • All exit points
  • 1 active session

$9.99

Buy now
Usage
50 GB

50 GB of data transfer with no time limit

  • 50 GB data
  • All exit points
  • 1 active session

$34.99

Buy now
Usage
5 GB

5 GB of data transfer with no time limit

  • 5 GB data
  • All exit points
  • 1 active session

$6.99

Buy now

For agents

Connect in three steps

AI agents can discover and use the service through standard protocols.

Discovery endpoints
GET/llms.txtagent docs
GET/robots.txtcrawler rules
GET/.well-known/x402payment info
GET/api/healthhealth check
GET/api/nodesnode catalog
GET/catalog.jsonpackage catalog
GET/faqhelp & recovery
GET/statusservice status
View llms.txt
Quick start

SOCKS5 (default, all exits):

# token is both username and password (RFC 1929)
curl --proxy socks5h://us-central1.x402socks.com:1080 \
  --proxy-user "$TOKEN:$TOKEN" https://api.example.com

HTTP CONNECT plaintext (TCP 3128):

# plaintext hop, exposes token on client-to-node path
curl --proxy http://us-central1.x402socks.com:3128 \
  --proxy-user "$TOKEN:$TOKEN" https://api.example.com

HTTP CONNECT TLS (TCP 3129):

# encrypted hop, preferred for headless browsers
curl --proxy https://us-central1.x402socks.com:3129 \
  --proxy-user "$TOKEN:$TOKEN" https://api.example.com

Browser clients that cannot supply SOCKS5 credentials can use HTTP CONNECT over TLS on TCP 3129 or plaintext on TCP 3128 at any exit — see the FAQ and llms.txt.

Programmatic access (agent view):

  1. Obtain a token via x402 payment or direct crypto checkout
  2. Set TOKEN env var: export TOKEN="your_token"
  3. Route requests through any exit using SOCKS5 or HTTP CONNECT
  4. Check account status: POST /api/token/status
  5. Rotate token if exposed: POST /api/v1/token/rotate
# verify token validity
curl -sS -X POST https://api.x402socks.com/api/token/validate \
  -H "Authorization: Bearer $TOKEN"

# check usage and expiry
curl -sS -X POST https://api.x402socks.com/api/token/status \
  -H "Content-Type: application/json" \
  -d "{\"token\":\"$TOKEN\"}"

Python (requests):

# pip install requests[socks]
import os, requests
token = os.environ["TOKEN"]
proxies = {"http": f"socks5h://{token}:{token}@us-central1.x402socks.com:1080",
           "https": f"socks5h://{token}:{token}@us-central1.x402socks.com:1080"}
r = requests.get("https://api.example.com", proxies=proxies)
print(r.status_code, r.text[:200])

TypeScript (undici):

// npm install undici
import { ProxyAgent } from "undici";
const token = process.env.TOKEN!;
const agent = new ProxyAgent(`socks5://${token}:${token}@us-central1.x402socks.com:1080`);
const res = await fetch("https://api.example.com", { dispatcher: agent });
console.log(res.status);

Go (golang.org/x/net/proxy):

// go get golang.org/x/net/proxy
package main
import (
    "fmt"; "net/http"; "os"
    "golang.org/x/net/proxy"
)
func main() {
    token := os.Getenv("TOKEN")
    d, _ := proxy.SOCKS5("tcp", "us-central1.x402socks.com:1080",
        &proxy.Auth{User: token, Password: token}, proxy.Direct)
    c := &http.Client{Transport: &http.Transport{Dial: d.Dial}}
    r, _ := c.Get("https://api.example.com")
    fmt.Println(r.StatusCode)
}

Service Guarantee

Best Effort

x402socks.com is designed to provide quick, anonymous, simple, and affordable service. While we work to keep everything running smoothly, access and performance are provided on a best-effort basis and we can therefore not guarantee a certain level of availability, performance, delivery, compatibility, or fitness for a particular purpose. Failed connections are non-refundable by default. Repeated or systemic failures from the same customer may be reviewed manually after the customer contacts support via our Telegram channel: t.me/x402socks For service status and support questions, contact us through Telegram.