Programmatic SOCKS5 proxies built for autonomous AI agents. No dashboards. No humans. Just an API, a payment address, and instant proxy credentials.
Designed from the ground up for agentic workflows. Run scrapers, LLMs, and autonomous browser tasks without human intervention.
No credit cards, no passwords, no email registrations. Agents auth using cryptographic signatures. Deposit stablecoins to your agent's balance instantly.
Dynamically request specific IP parameters straight in the SOCKS5 connection string (e.g. socks5://wallet:sig@socks5.proxybase.xyz:1080?country=us).
Our Rust gateways maintain multiple simultaneous upstream connections per session. If an IP gets throttled, traffic switches paths instantly.
Monitor data usage, bandwidth speed, and path latency directly from the REST API. Automatically top-up balances when thresholds trigger.
Pay strictly for the bandwidth your agents consume. Credits never expire. Deposit stablecoins anytime.
Bypass Geo-blocking and scrapers using residential IPs.
Highest trust score IPs sourced from active mobile carriers.
Full programmatic control for autonomous agents and scrapers. Register agents, query bandwidth packages, provision orders, and rotate SOCKS5 proxy IPs via simple REST requests.
The ProxyBase v1 API authenticates requests using stateless API keys. Once you register an agent via POST /v1/agents, you will receive a unique pk_... API key. Include this key in the X-API-Key header for all authenticated requests.
| Header | Type | Status | Description |
|---|---|---|---|
X-API-Key | string | Required | Your agent API key (e.g., pk_7f8a9b0c1d2e3f...). |
Content-Type | string | Optional | Set to application/json when sending JSON request bodies. |
curl -X GET https://api.proxybase.xyz/v1/packages \ -H "X-API-Key: pk_7f8a9b0c1d2e3f4a5b6c7d8e9f0a1b2c3d4e5f6a"
Registers a new AI agent on the ProxyBase routing grid and generates a fresh API key. No prior authentication is required. This endpoint is rate-limited to 3 registrations per IP per 60 seconds (max 10 per hour).
No request body is required for agent registration.
{
"agent_id": "ag_8f92a1b0",
"api_key": "pk_3a8b9c0d1e2f3a4b5c6d7e8f9a0b1c2d3e4f5a6b7c8d9e0f1a2b3c4d5e6f7a8b"
}Fetch available proxy bandwidth packages (residential, mobile, and datacenter tiers) via GET /v1/packages and query supported cryptocurrency payment tickers via GET /v1/currencies.
| Header | Type | Status | Description |
|---|---|---|---|
X-API-Key | string | Required | Your agent API key. |
// GET /v1/packages response:
[
{
"id": "res_5gb",
"name": "Residential 5GB",
"price_usd": 15.00,
"bandwidth_bytes": 5368709120
},
{
"id": "mob_10gb",
"name": "Mobile 10GB",
"price_usd": 45.00,
"bandwidth_bytes": 10737418240
}
]
// GET /v1/currencies response:
{
"currencies": ["usdcsol", "usdttrc20", "btc", "eth", "sol"]
}Creates a new proxy order for a specified package. For standard agents, this returns an automated cryptocurrency payment invoice (via NOWPayments). For recognized third-party integration partners, proxies are provisioned immediately without manual payment.
| Parameter | Type | Status | Description |
|---|---|---|---|
package_id | string | Required | ID of the bandwidth package to purchase (e.g., res_5gb). |
pay_currency | string | Optional | Cryptocurrency ticker for payment (default: usdcsol). |
callback_url | string | Optional | HTTPS webhook URL to receive asynchronous status updates. |
{
"order_id": "ord_71a8b9c0",
"payment_id": "5039482930",
"pay_address": "4k3Dyjzvzp8eMZWUXbBCjEvwSkkk59S5iCNLY3QrkX6R",
"pay_currency": "usdcsol",
"pay_amount": 15.00,
"price_usd": 15.00,
"status": "payment_pending",
"expiration_estimate_date": "2026-07-07T03:00:00Z"
}Retrieves real-time order status, live bandwidth utilization metrics (used vs. remaining bytes), and SOCKS5 proxy connection credentials once payment is confirmed and the proxy is provisioned.
| Parameter | Type | Status | Description |
|---|---|---|---|
order_id | string | Required | The masked order identifier returned when creating the order. |
{
"order_id": "ord_71a8b9c0",
"status": "proxy_active",
"price_usd": 15.00,
"bandwidth_bytes": 5368709120,
"used_bytes": 1048576,
"remaining_bytes": 5367660544,
"usage_percentage": 0.0195,
"proxy": {
"host": "api.proxybase.xyz",
"port": 1080,
"username": "pb_ag_71a8b9c0",
"password": "pass_random_secure_secret"
},
"created_at": "2026-07-07T02:15:00Z"
}Add additional data transfer capacity to an existing active or exhausted proxy order without changing your SOCKS5 proxy credentials or connection string.
| Parameter | Type | Status | Description |
|---|---|---|---|
package_id | string | Required | ID of the bandwidth package to add to the order. |
pay_currency | string | Optional | Cryptocurrency ticker for payment (default: usdcsol). |
{
"order_id": "ord_71a8b9c0",
"topup_payment_id": "5039483100",
"pay_address": "4k3Dyjzvzp8eMZWUXbBCjEvwSkkk59S5iCNLY3QrkX6R",
"pay_currency": "usdcsol",
"pay_amount": 15.00,
"additional_bandwidth_bytes": 5368709120,
"additional_price_usd": 15.00,
"status": "payment_pending"
}Triggers an immediate upstream IP rotation for an active proxy order. Your SOCKS5 credentials remain identical, but your very next connection will route through a fresh residential or mobile IP address.
No request body is required. Requires an active order in proxy_active status.
{
"order_id": "ord_71a8b9c0",
"message": "Proxy rotated successfully. You will receive a fresh IP on your next connection.",
"rotated": true
}Allow Claude or any other LLM to interact directly with ProxyBase. The agent can purchase proxies autonomously when needed.
By launching the ProxyBase MCP server, you give your LLM agent tools to manage its own routing infrastructure. The agent can:
Common questions regarding ProxyBase client integration.
When you create an order via POST `/v1/orders` or top up via POST `/v1/orders/{id}/topup`, you receive a dedicated cryptocurrency invoice address (e.g., USDC on Solana). Once payment is detected on-chain, your proxy is provisioned automatically.
Yes. Your LLM agent can autonomously query GET `/v1/orders/{order_id}/status` to check real-time bandwidth utilization (used vs. remaining bytes) and decide when to trigger a top-up.
Residential proxies represent stable domestic connections. Mobile proxies use cellular IP ranges, making them extremely resilient against commercial Cloudflare/Akamai bot detection systems.
When a request is made, ProxyBase establishes two independent upstream paths. If one path fails to establish a TCP handshake or experiences latency spikes, the stream fails over instantly to the backup path with zero client-side socket breakage.