# AproxPay

> Residential proxy for autonomous AI agents. Pay per request in USDC on Base via x402 — no signup, no API keys, guaranteed 30–60 min sticky sessions.

AproxPay is a residential/mobile proxy service designed for autonomous AI
agents. There are no accounts, API keys, or subscriptions: every request is
paid individually with the x402 protocol (HTTP 402 + USDC on Base mainnet). Your wallet is your identity. Payments are non-custodial and settle
on-chain directly from the buyer's wallet; requests that fail with an error
(status >= 400) are not charged.

## API

Base URL: https://proxy.aproxpay.com

- GET /health (free): Liveness check. Returns { status, timestamp }.
- POST /v1/proxy ($0.003): Fetch 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.008): Same as /v1/proxy with a 10MB response cap — for heavier pages and files.
- POST /v1/session ($0.05): Mint 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.05): Top up a live session with +30 min and +250MB — same exit IP, paid with another x402 payment.
- POST /v1/session/:id/close (free): Revoke a session early. Authenticated with the session's own credentials (Basic auth).

CONNECT gateway for session credentials: gw.aproxpay.com:8443

## Pricing (source: fallback)

- $0.003 (3000 atomic USDC), byte cap 2097152 bytes — Per-request residential fetch, up to 2MB response
- $0.008 (8000 atomic USDC), byte cap 10485760 bytes — Per-request residential fetch, up to 10MB response
- $0.05 (50000 atomic USDC), 30 min, byte cap 262144000 bytes — Session pass: standard CONNECT proxy credentials, 30 min + 250MB; extend tops up at the same price

Payment details: network eip155:8453, asset (USDC) 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913,
scheme "exact" (EIP-3009 signed transfer). The authoritative price is always
the "amount" field in the 402 response of the route you are calling.
Machine-readable pricing: https://aproxpay.com/pricing.json

## How to pay (x402)

1. Call a paid endpoint without payment. You receive HTTP 402; the
   "payment-required" response header holds a base64-encoded JSON challenge
   whose "accepts" array describes price, network, asset, and payTo address.
2. Sign an EIP-3009 USDC transfer authorization for that amount.
3. Retry the same request with the signed payload in the "X-PAYMENT" header.
4. x402 client libraries (x402-fetch, x402-axios, x402-requests) automate
   this loop.

## Sticky sessions

POST /v1/session returns standard forward-proxy credentials
{host, port, username, password, expiresAt, byteCap} bound to one residential
exit IP for 30 minutes (extendable in 30-minute increments via
POST /v1/session/:id/extend — same IP, same price). Works with Playwright,
browser-use, curl, or any HTTP client via standard CONNECT.

## Links

- Website: https://aproxpay.com
- Terms: https://aproxpay.com/terms
- Privacy: https://aproxpay.com/privacy
- Acceptable Use: https://aproxpay.com/aup
- Contact: hello@aproxpay.com
- Abuse: abuse@aproxpay.com