Proxies.sx is a live x402 seller. An autonomous agent requests, gets a 402 with the price, pays USDC on Base or Solana, and retries with the tx hash - then holds real SOCKS5/HTTP credentials on dedicated 4G/5G carrier IPs. No signup, no KYC, no card. The one purchase path no proxy incumbent offers.
npx @proxies-sx/mcp-server
The question that sorts x402 sellers: what do you actually hold after the 402? Browserbase hands your agent a session. Apify hands it a run. We hand it the pipe itself - raw reusable SOCKS5/HTTP credentials on a dedicated 4G/5G carrier IP, bought per-GB in one HTTP round-trip.
No account to create, no key to provision, no human to page.
The agent calls the purchase endpoint with no key and no account. The response is HTTP 402 with the price.
It pays USDC on Base or Solana from its own wallet. Those two chains are live today, with our open-source SDK.
It retries with the tx hash and receives SOCKS5/HTTP credentials on a dedicated 4G/5G carrier IP - reusable until the purchased GB runs out.
| Vendor | Agent pays for | Agent ends up holding |
|---|---|---|
| Browserbase (x402) | a browser session | a session locked to their runtime |
| Apify (x402/Skyfire) | a scraper run | one actor's output |
| Proxies.sx | per-GB bandwidth | raw reusable proxy credentials + a dedicated carrier IP |
Sessions and runs expire and lock you in. Credentials are the pipe - reusable, protocol-agnostic, and yours until the GB runs out.
Agents hit the same wall humans do: IP-reputation bans - DataDome'st=bv verdict - kill a session no matter how clean the fingerprint. No stealth patch on the browser side fixes an exit IP the defense already distrusts.
The durable fix is a real carrier IP. A carrier CGNAT address is shared with masses of legitimate phone users, so an anti-bot vendor cannot blocklist it wholesale without blocking real customers - the same mechanism behind our anti-bot lane. The difference here: your agent can now buy that IP itself, mid-run, with its own wallet.
One install line, 55 tools, and a keyless wallet mode: the agent pays as it goes, so there is no API key to provision and no account to create first. It is built for the AI builder who wants to ship tonight - no account, no sales call.
The bandwidth it buys is the same self-serve stock humans buy: $4/GB list, down to $2.40/GB at volume, and GB never expire.
Pricing and chain availability (Base + Solana) verified July 2026.
Browser-infra players are complements, not rivals - their users hit our exact buying moment: an IP-reputation ban mid-session. Keep the runtime you like; swap in a carrier IP.
Bring your own exit IP to Browserbase sessions - Stagehand keeps driving the browser, our carrier IP does the exiting.
Steel’s proxy support is bring-your-own by design - that is exactly the slot raw reusable credentials fill.
Browserless fingerprint stealth cannot fix an IP-reputation ban. Pair BrowserQL with a dedicated carrier IP and the exit stops being the weak link.
A quickstart for agent frameworks: the agent hits the 402, pays USDC, and threads the credentials into its own tools mid-run.
Honest framing: x402 alone is copyable plumbing - any incumbent could bolt it on. The moat is the stack: a wallet-native buy, per-GB metering, raw reusable credentials, dedicated carrier IPs, and a keyless MCP server, together in one round-trip.
Two limits we own: we cover 6 modem countries, not 195. And we are a seller on rails we do not own - Base, Solana and the x402 Bazaar. We ride the rails; we do not rebuild them.
Yes. That is wallet mode: the agent requests, gets a 402 back with the price, pays USDC, retries with the tx hash and receives credentials. No signup, no KYC, no card, no human in the loop.
Base and Solana, live today, with our open-source SDK. No other chains - we would rather ship two that work than list ten that do not.
Real reusable SOCKS5/HTTP credentials on a dedicated 4G/5G carrier IP - not a session locked to somebody else’s runtime. The credentials are protocol-agnostic and keep working until the purchased GB runs out.
Yes - as the bring-your-own exit IP. Those runtimes are complements, not rivals: keep their browser, swap in our carrier IP when IP reputation gets the session banned. See the integration recipes above.
No. Run npx @proxies-sx/mcp-server in keyless wallet mode and the agent pays as it goes - there is no API key to provision and no account to create first.
One HTTP round-trip: 402, pay USDC on Base or Solana, hold real SOCKS5/HTTP credentials on a dedicated 4G/5G carrier IP. No signup, no KYC, no card.