Vision · April 2026

The AI Bandwidth Economy: How AI Agents Buy Clean IPs From Device Fleets.

Modern AI agents need clean residential and mobile IPs to run data intelligence at scale. Modern devices have spare bandwidth. We're building the marketplace where AI agents autonomously pay devices in USDC — agent-to-agent, device-to-fleet, no centralized proxy middlemen.

$2.51 / GB peer share · mobileUSDC · Solana · ~400msx402 · MCP · WebSocket
the thesis · 30s read

Every AI agent that does real work on the public web needs clean IPs. Every smartphone, every VPS, every IoT node has idle bandwidth. The infrastructure layer between them — the relay, the gateway, the payment rail — is what we ship. Agents pay USDC per byte routed. Devices earn USDC per byte routed. Humans run fleets. Agents run fleets. The same protocol works for both. Decentralized data intelligence, settled on Solana, agnostic about who's on which side of the market.

problem

Clean IPs are the new oil.

Cloudflare blocks ~30% of all internet traffic in real time. DataDome, PerimeterX, Akamai, AWS WAF, Kasada, Imperva — every major anti-bot system shares one shortcut: they block datacenter IPs by default. AWS, GCP, Azure, Hetzner, OVH — entire ASN ranges flagged. Residential IPs work better but still get blocked when ISPs sell their DHCP pools. Mobile IPs are the last category that scales: carriers route thousands of real subscribers behind a single CGNAT IP, so blocking a mobile IP means blocking real paying customers. No anti-bot vendor is willing to take that risk.

That makes mobile IPs structurally scarce. There are only so many real phones in the world, and only some of them are willing to route external traffic. Every AI agent that wants to scrape Google SERPs, monitor Amazon prices, watch Reddit sentiment, or train on the public web is bidding for the same finite pool of clean IPs.

Why it matters now: AI agents are the fastest-growing source of web traffic in 2026. Every agentic system — Conway, OpenClaw, autonomous Claude/GPT pipelines, MCP-driven workflows — needs to call the public web on behalf of a user. They can't do it from datacenter IPs. The supply side is finite. The demand side is exploding. That's an economy.
state of the union

Today vs Tomorrow.

Today (mostly)

Humans run agents. Humans pay for proxies.

A developer signs up for a proxy provider, gets a credit card billed monthly, runs their scraper, manually rotates IPs, watches the dashboard. The agent is doing the work, but a human is doing the wallet, the auth, the procurement.

friction: ~14 manual steps per scrape pipeline
Tomorrow (already running)

Agents pay agents. Devices earn USDC.

An AI agent hits an x402-gated endpoint, gets back a 402 with a price, pays USDC on Solana in ~400ms, receives a session token, routes traffic through a peer device, logs the byte count. Another agent on a phone in Lagos earns the other side of that trade. No human in the loop on either side.

friction: 2 API calls + 1 wallet
the architecture

Four layers. One economy.

We ship four protocols that compose into the bandwidth economy. Each is independently usable; together they form the loop.

01

x402 Payment Protocol

M2M USDC payments

HTTP 402 Payment Required, made functional. Agent hits an endpoint, gets back a 402 with price + recipient + supported networks. Sends USDC on Base (~2s) or Solana (~400ms). Retries with the tx hash as proof. Receives the resource. Open spec, anyone can implement.

Used by AI agents to pay for: proxy access, SERP queries, Google Maps records, Reddit search, Instagram intelligence, LinkedIn enrichment, Airbnb data — anything an agent needs.

02

MCP Server

55 tools for AI agents

Model Context Protocol server. AI agents (Claude Desktop, Cursor, Cline, Conway, OpenClaw) install one package and get 55 typed tools — manage proxies in natural language, run x402 payments end-to-end, rotate IPs, check earnings, top up sessions. Works with API keys or pure x402 mode.

How AI agents discover, control, and operate proxy infrastructure without human supervision.

03

Peer Relay

WebSocket bandwidth network

wss://relay.proxies.sx — devices register, connect via JWT, receive proxy_request messages, fetch via real IP, return proxy_response. Earnings credit per byte. Phones, VPS, Docker, Android SDK, custom clients in any language — same protocol.

How devices supply clean IPs to the network and earn USDC. Humans run fleets. Agents run fleets. Same protocol, same rates.

04

Pool Gateway

HTTP/SOCKS5 endpoint

gw.proxies.sx:7000 (HTTP) and 7001 (SOCKS5). The customer-facing surface. AI agents and humans both hit this with standard proxy credentials. Behind it, the gateway routes to verified peer devices via the relay.

How customers actually consume the bandwidth. Standard HTTP/SOCKS5 — works with curl, Playwright, Puppeteer, Selenium, every existing tool.

both sides of the market

Humans and agents — same protocol.

The peer network is a true two-sided marketplace. The same WebSocket relay, the same x402 payment rail, the same USDC settlement — but participants come from very different worlds. Here's how each side plugs in.

👤
Humans
Run fleets. Use tools.
  • Earn: Run an Android phone, a VPS / Docker container, or a Raspberry Pi as a peer. Bandwidth → USDC.
  • Use: Buy bandwidth via the customer dashboard at client.proxies.sx. GB-based pricing. Standard HTTP/SOCKS5.
  • Build: Develop x402-paid services on top of our marketplace. Earn USDC per query.
  • Manage: Use the MCP server in Claude Desktop / Cursor to operate fleets in plain English.
🤖
AI agents
Pay autonomously. Earn idle.
  • Pay: Use x402 to buy bandwidth and data without API keys. Wallet-native. No signup. Hit /v1/x402/proxy, send USDC, get a session.
  • Earn: Register as a peer in 2 API calls. Connect WebSocket. Route traffic during idle cycles. USDC accrues per byte.
  • Discover: Read agents.proxies.sx/skill.md — full machine-readable spec for autonomous agents.
  • Self-fund: Agents that earn from their own bandwidth can pay for their own LLM inference. The flywheel closes.
the unit economics

The economics, in plain terms.

We split revenue 56% / 44% — peer takes the majority. Rates are unified across sources: a real mobile carrier IP earns the mobile tier whether it joined the network as an AI agent, an Android phone, or a ProxySmart farmer modem. Server-side ASN classification keeps the system honest — device-reported types are ignored.

IP typeCustomer paysPeer earns (56%)Why this rate
Mobile$4.48 / GB$2.51 / GBCGNAT trust premium · highest demand
Residential$2.24 / GB$1.25 / GBReal ISP IP · mid-trust
Datacenter$0.56 / GB$0.31 / GBEasily detected · base rate

$5 minimum payout · USDC on Solana · 24–48h processing · 7-day wallet cooling after change. Server-side ASN classification — cannot be spoofed.

anti-fraud

Verifiable scarcity.

Most bandwidth-sharing networks pay the same rate to everyone. We don't — because the IPs aren't worth the same. A real T-Mobile 5G IP routes a request that nobody can block. A Hetzner datacenter IP routes a request that gets blocked at the edge. Paying both equally would burn customer money on traffic that fails.

Instead, every connecting device gets classified server-side via ASN lookup against a curated registry of 200+ mobile carrier ASNs, 100+ datacenter providers, and known VPN ranges. Device-reported metadata is ignored. You can't spoof your way into the mobile tier — the network sees what your IP actually is. That keeps the marketplace honest, customer success rates high, and scarcity verifiable.

200+
Mobile carrier ASNs
AT&T, Verizon, T-Mobile, Vodafone…
100+
Datacenter ASNs
AWS, GCP, Azure, Hetzner…
24/7
VPN range scanning
Mullvad, NordVPN, anon proxies
what the bandwidth is for

What AI agents actually do with these IPs.

All public-web work. No login walls, no private data, no identity scraping. Standard data intelligence — the same kind of work companies have done for 20+ years, now run autonomously by AI agents and paid for in real-time on-chain.

🔍

SERP tracking

Google, Bing, AI Overviews, featured snippets, map packs. Track ranking changes for SEO at scale.

🛒

Price intelligence

Amazon, Shopify, Walmart, eBay. Real-time price monitoring across ecosystems and geographies.

🗺️

Local data

Google Maps places, reviews, business listings. Lead generation, market mapping, competitive analysis.

📈

Market intelligence

Real-estate listings, job postings, ad creative, prediction markets. Build datasets that move with the market.

📰

Public sentiment

Reddit search, news aggregation, blog scraping. Train sentiment models on real-world signal.

✈️

Travel & inventory

Airbnb, flights, hotel pricing. Dynamic inventory monitoring across hundreds of platforms.

🤖

AI training data

Build training corpora from the public web. Mobile IPs unlock sites that block datacenter IPs entirely.

Ad verification

Brand-safety checks, ad creative monitoring, geo-targeted ad inspection. See what real users actually see.

infrastructure agnostic

Bring your own device. Bring your own protocol.

We document four ways to join — Android SDK, Docker, Node.js, raw curl + WebSocket. But the only thing we actually require is: deliver an HTTP proxy endpoint from a real IP. How you get there is up to you.

Run a Raspberry Pi mesh on a residential network. Build a custom firmware for a router. Write a SOCKS5-to-HTTP bridge in Rust. Run a fleet of IoT devices behind a single relay client. Build something nobody has thought of. As long as the IP is real (server-classified), traffic flows through your device, and you connect via the relay protocol — we route to you, we track usage, we pay you.

Input:  A device with a real mobile or residential IP.
Output: An HTTP proxy endpoint that routes traffic through it.
Result: We pay you per GB routed, in USDC, on Solana.

That's the entire requirement.
the bigger picture

Why this is bigger than proxies.

We're early to a real shift. The first generation of AI agents was just chatbots — text in, text out, no external state. The second generation is doing real work: filling forms, calling APIs, running scrapers, executing transactions. Every single one of those operations needs to actually reach the public internet, which means it needs an IP that won't get blocked.

Today the supply side of clean IPs is captured by a handful of proxy companies running their own infrastructure with billing departments and AML compliance. Tomorrow it's a marketplace where any device with a real IP can list, any agent with a wallet can pay, and the protocol settles directly on-chain. The aggregate result: the cost of real-world data collection drops, the supply of clean IPs grows, and the AI agents doing useful work for humans get cheaper to operate.

The ultimate version: autonomous agent-to-agent commerce. An agent that earns USDC from its data work pays another agent for its bandwidth. That agent in turn pays for its compute, its hosting, its tools. No human in the loop. No credit cards, no API keys, no monthly procurement reviews. Just protocols all the way down. This is what the four-layer stack (x402 + MCP + Peer Relay + Gateway) is designed for.

go deeper

Deep dives.

We've written extensively on the components of this thesis. Six places to go next:

participate

Plug in.

The economy is live. Both sides are open. Pick your seat at the table.

closing note

We're not the first to build a bandwidth-sharing network. Honeygain, PacketStream, Grass, Pawns — they've all tried. What's different in 2026 is the demand side. AI agents don't care about loyalty programs or referral codes; they care about clean IPs that don't get blocked, paid for in machine-native USDC, with a protocol they can implement in 50 lines. That's what we ship. The economy follows.

— The PROXIES.SX team · April 2026