aproxpay.

x402 · USDC on Base · non-custodial

The proxy built for AI agents.

One x402 payment gets your agent a residential IP with a guaranteed 30–60 minute sticky session — as a single fetch, or as standard proxy credentials Playwright can use. Pay per request in USDC. No signup. No API keys. No subscription.

View the APIllms.txt →
curl + x402
# 1 — ask without paying: the 402 response tells you the price
$ curl -i -X POST https://proxy.aproxpay.com/v1/proxy \
    -H 'Content-Type: application/json' \
    -d '{"url": "https://example.com", "sticky": true}'

HTTP/1.1 402 Payment Required
payment-required: <base64>   # decodes to:
{
  "accepts": [{
    "scheme": "exact",
    "network": "eip155:8453",
    "amount": "3000",          # $0.003 USDC
    "payTo": "0x…"
  }]
}

# 2 — retry with a signed USDC transfer (x402 SDKs automate this loop)
$ curl -X POST https://proxy.aproxpay.com/v1/proxy \
    -H 'X-PAYMENT: <base64 signed payment>' \
    -H 'Content-Type: application/json' \
    -d '{"url": "https://example.com", "sticky": true}'

HTTP/1.1 200 OK        # the fetched page, via a residential IP

x402 in 3 steps

How it works

  1. 1

    Request

    Call any endpoint with plain HTTP. No account, no key, no SDK required — your wallet is your identity.

  2. 2

    402 challenge

    The API answers 402 Payment Required with the exact price in USDC. Nothing has been charged yet — the price is part of the protocol, not a pricing page.

  3. 3

    Pay & go

    Sign a USDC transfer (EIP-3009), retry with the X-PAYMENT header, get your response. Settlement is non-custodial: funds move directly from your wallet to ours. Failed requests are never charged.

The whole API

Endpoints

Base URL: https://proxy.aproxpay.com. Paid routes respond 402 until an X-PAYMENT header carries a valid USDC payment. Sessions tunnel through gw.aproxpay.com:8443.

EndpointPriceDescription
GET/healthfreeLiveness check. Returns { status, timestamp }.
POST/v1/proxy$0.003Fetch a URL through a residential IP and get the response back. Body: { url, sticky?, sticky_duration? }. Response capped at 2MB.
POST/v1/proxy/large$0.008Same as /v1/proxy with a 10MB response cap — for heavier pages and files.
POST/v1/session$0.05Mint ephemeral credentials for a standard CONNECT proxy: { host, port, username, password, expiresAt, byteCap }. Point Playwright or curl at it. 30 min + 250MB, sticky exit IP.
POST/v1/session/:id/extend$0.05Top up a live session with +30 min and +250MB — same exit IP, paid with another x402 payment.
POST/v1/session/:id/closefreeRevoke a session early. Authenticated with the session's own credentials (Basic auth).

Pay per use

Pricing

Fetch

$0.003per request

  • Residential exit IP
  • Up to 2MB response
  • Sticky IP 30–60 min
  • One HTTP call — pay, fetch, done

Fetch Large

$0.008per request

  • Residential exit IP
  • Up to 10MB response
  • Sticky IP 30–60 min
  • For heavy pages and files

Session Pass

$0.05per 30 min

  • Standard CONNECT proxy credentials
  • 250MB included
  • Same exit IP for the whole session
  • Playwright / browser-use ready
  • Extend anytime — same IP, same price

Current published pricing. Paid in USDC on Base; the exact amount is always stated in the 402 response.

The difference

Why AproxPay

AproxPayOther x402 proxiesLegacy providers
x402 native — pay per request in USDC✓✓—
Guaranteed 30–60 min sticky sessions✓—✓
Standard CONNECT proxy for one payment (Playwright-ready)✓——
No signup, no API key✓✓—
No subscription or minimum commit✓✓—
Residential IP pool✓—✓

Most x402 proxies rotate your IP every few minutes — fatal for multi-step agent workflows like logins, checkouts, or form flows. Legacy providers keep the IP but want a subscription, KYC, and an API key before your agent makes its first request.

Integrations

Works with your stack

Any x402 client

available now

The API is plain HTTP + x402. x402-fetch, x402-axios, x402-requests or your own 402→sign→retry loop all work today.

MCP server

coming soon

proxy_get, create_session, extend_session and close_session as MCP tools for Claude and other MCP clients.

LangChain & CrewAI

coming soon

Drop-in Tool classes for Python and JS agents — point your agent at the proxy without writing payment code.

x402 Bazaar

at launch

Listed in the x402 discovery index, so agents can find and pay for the service autonomously.

Questions

FAQ

What is x402?
x402 is an open payment protocol built on the HTTP 402 status code. When your agent calls a paid endpoint without payment, the API answers 402 with the exact price in USDC. The agent signs a USDC transfer, retries the request with an X-PAYMENT header, and gets the result. No accounts, no invoices — every request pays for itself.
Do I need an account or an API key?
No. Your wallet is your identity. Any agent holding USDC on Base can start making requests immediately — there is no signup form, no dashboard, and no key to provision or leak.
Which network and token do you accept?
USDC on Base (network eip155:8453), using the x402 exact-payment scheme (EIP-3009 signed transfers). Payments settle on-chain directly from your wallet to ours — we never hold your funds.
Am I charged if a request fails?
No. If the fetch fails or the API returns an error (status 400 or above), the payment is cancelled and you are not charged.
How do sticky sessions work?
POST /v1/session returns standard proxy credentials (host, port, username, password) bound to one residential exit IP that stays yours for 30 minutes, extendable in 30-minute increments without changing the IP. Because it is a standard CONNECT proxy, it works with Playwright, browser-use, curl, or any HTTP client — no SDK required.
What happens when I hit the byte cap?
Every payment carries a hard byte cap (2MB or 10MB per request, 250MB per session). When a session reaches its cap, traffic stops until you extend it — same price, same exit IP. Per-request fetches over the cap are rejected rather than silently billed.