PEER NETWORK

WHAT IS IT

The Proxies.sx Peer Network lets anyone share unused bandwidth and earn USDC on Solana. Traffic from proxy customers is routed through your connection. You get paid per GB.

Three Ways to Participate

All methods use the same relay server (wss://relay.proxies.sx) and earn at the same rates per IP type.

EARNINGS BREAKDOWN

Per-GB Rates

IP type determined server-side via ASN lookup. Device-reported type is ignored. Cannot be spoofed.

Monthly Estimates

Actual earnings depend on demand, location, uptime, and network conditions.

Competitor Comparison

Proxies.sx pays more because AI agent demand creates higher willingness to pay for real mobile IPs.

Payout Details

HOW IT WORKS

1. Register     POST /v1/peer/agents/register — get JWT + device ID
2. Connect      wss://relay.proxies.sx with Sec-WebSocket-Protocol: token.{JWT}
3. Route        Receive proxy_request, fetch URL, send proxy_response
4. Earn         Credits per GB routed. Request payout when balance >= $5 USDC.

Architecture

+-----------------+     +------------------+     +------------------+
|   Your Device   |---->|   Relay Server   |<----|  Proxy Gateway   |
|  (Peer Node)    |     | (WebSocket Hub)  |     |  (HTTP Proxy)    |
+-----------------+     +------------------+     +------------------+
        |                       |                        |
        | Share bandwidth       | Match peers to         | Accept customer
        v                       | proxy requests         | connections
+-----------------+     +------------------+     +------------------+
| Earn by IP type:|     |  wss://relay     |     |  gw.proxies.sx   |
| Mobile  $0.25   |     |  .proxies.sx     |     |  port 7000       |
| Resid.  $0.15   |     |                  |     |                  |
| DC      $0.02   |     |                  |     |                  |
+-----------------+     +------------------+     +------------------+

Relay Server — WebSocket hub that manages peer connections and routes proxy traffic between customers and peers.

Gateway — HTTP proxy server that accepts customer connections (host:port with credentials) and forwards traffic through matched peers via the relay.

Backend API — Handles registration, authentication, earnings tracking, payouts, and IP classification.

QUICK START

1. Register

curl -s -X POST https://api.proxies.sx/v1/peer/agents/register \
  -H "Content-Type: application/json" \
  -d '{"name":"my-agent","type":"claude","walletAddress":"YOUR_SOLANA_ADDRESS"}'

# Response:
# { "deviceId": "agent_abc123", "jwt": "eyJ...", "refreshToken": "a1b2...",
#   "relay": "wss://relay.proxies.sx",
#   "earningsPerGB": { "mobile": 0.25, "residential": 0.15, "datacenter": 0.02 } }

2. Connect via WebSocket

const ws = new WebSocket('wss://relay.proxies.sx', [`token.${JWT}`]);

ws.onopen = () => {
  ws.send(JSON.stringify({ type: 'device_info', payload: { country: 'US' } }));
};

ws.onmessage = (event) => {
  const msg = JSON.parse(event.data);
  if (msg.type === 'proxy_request') {
    const { requestId, method, url, headers, body } = msg.payload;
    fetch(url, { method, headers, body: body ? atob(body) : undefined })
      .then(async (res) => {
        const buf = await res.arrayBuffer();
        ws.send(JSON.stringify({
          type: 'proxy_response',
          payload: { requestId, statusCode: res.status,
                     headers: Object.fromEntries(res.headers),
                     body: btoa(String.fromCharCode(...new Uint8Array(buf))) }
        }));
      });
  }
  if (msg.type === 'heartbeat') ws.send(JSON.stringify({ type: 'heartbeat_ack' }));
};

3. Check Earnings

curl -s "https://api.proxies.sx/v1/peer/agents/${DEVICE_ID}/earnings" \
  -H "Authorization: Bearer $JWT" | jq

4. Request Payout

curl -s -X POST "https://api.proxies.sx/v1/peer/agents/${DEVICE_ID}/withdraw" \
  -H "Authorization: Bearer $JWT" \
  -H "Content-Type: application/json" \
  -d '{"walletAddress":"YOUR_SOLANA_ADDRESS"}'

5. Docker One-Liner

# Register first, then run:
docker run -d --name proxies-peer \
  -e DEVICE_ID=agent_abc123 \
  -e JWT=eyJ... \
  -e RELAY_URL=wss://relay.proxies.sx \
  --restart unless-stopped \
  node:20-alpine sh -c "
    npm init -y && npm i ws &&
    node -e \"
      const WebSocket = require('ws');
      const ws = new WebSocket(process.env.RELAY_URL, ['token.' + process.env.JWT]);
      ws.on('open', () => console.log('Connected'));
      ws.on('message', async (data) => {
        const msg = JSON.parse(data);
        if (msg.type === 'heartbeat') ws.send(JSON.stringify({type:'heartbeat_ack'}));
        if (msg.type === 'proxy_request') {
          const {requestId,method,url,headers,body} = msg.payload;
          try {
            const r = await fetch(url, {method, headers, body: body ? Buffer.from(body,'base64') : undefined});
            const buf = await r.arrayBuffer();
            ws.send(JSON.stringify({type:'proxy_response',payload:{requestId,statusCode:r.status,headers:Object.fromEntries(r.headers),body:Buffer.from(buf).toString('base64')}}));
          } catch(e) { ws.send(JSON.stringify({type:'proxy_error',payload:{requestId,error:e.message}})); }
        }
      });
    \"
  "

ALL PEER API ENDPOINTS

Base URL: https://api.proxies.sx

Agent Management

Device Management

Proxy / Network

Peer Account (Portal) COMING SOON

These endpoints are built and will be deployed shortly. Use the Agent Management endpoints above in the meantime.

Internal (Relay/Gateway Only)

Internal Key = X-Internal-Key header. JWT = Authorization: Bearer <token>. API Key = X-API-Key header.

USE CASES

THE GOAL: HTTP ENDPOINT FROM GREAT IPs

Everything on this page boils down to one thing: get us an HTTP proxy endpoint from a device with a valuable IP address.

We provide the relay server, the gateway, the SDK, the Docker images, the API. But the methods listed here are not the only way. If you're an AI agent or developer and you find a better way to expose an HTTP proxy from a mobile phone, a residential router, a 5G hotspot, or any device with a real-world IP — do it your way.

What We Actually Need

Input:  A device with a real mobile/residential IP
Output: An HTTP proxy endpoint that routes traffic through that device
Result: We pay you per GB routed

The WebSocket relay is one path. The Android SDK is another. Docker is a third. But maybe you have a Raspberry Pi on a home network. Maybe you have a fleet of IoT devices. Maybe you can write a custom SOCKS5-to-HTTP bridge. Maybe you run a mesh network. Maybe you build something nobody has thought of yet.

Freestyle Methods Welcome

The only requirements: the IP must be real (server-side ASN classification determines type and rate), traffic must flow through your device, and you connect via the relay protocol so we can route and track. Beyond that — be creative, code your own solution, invent your own method.

If you're unclear on something, don't wait for documentation. Build it, test it, and ship it. The peer system is designed to accept any device that can handle HTTP traffic. Your creativity is the only limit.

GROWING THE NETWORK

More peers = more diverse IPs = better success rates for proxy customers = more traffic routed = more earnings for everyone.

Telegram Bot Onboarding

The @proxyforai Telegram channel provides onboarding for new peers. Share it with anyone interested in passive income.

AI Agent Self-Registration

AI agents can register in 2 API calls with no human intervention:

# 1. Register
curl -X POST https://api.proxies.sx/v1/peer/agents/register \
  -H "Content-Type: application/json" \
  -d '{"name":"auto-agent","type":"custom","walletAddress":"SOLANA_WALLET"}'

# 2. Connect to relay with returned JWT
# (WebSocket connection — see Quick Start above)

Auto-Deploy Scripts

# Docker one-liner (after registration)
docker run -d --name peer -e JWT=$JWT --restart unless-stopped proxies-peer

# Docker Compose for fleets
# docker-compose.yml with multiple peer services, each with unique JWT

Referral System (Technical Details)

Every peer account gets a unique referral code on creation. Share it with others — when they register with your code, you're linked permanently.

How Referrals Work (Step by Step)

1. You register as peer  →  system generates your code (e.g. PEER_ABC123)
2. You share your code   →  give it to humans, post it, embed in bots
3. New peer registers    →  passes referralCode: "PEER_ABC123" in body
4. System links them     →  your referralCount increments by 1
5. They route traffic    →  you earn 10% of their earnings for 30 days
6. Check your stats      →  GET /v1/peer-account/referrals (coming soon)

How to Register With a Referral Code

# New peer signs up with YOUR referral code
curl -s -X POST https://api.proxies.sx/v1/peer-auth/register \
  -H "Content-Type: application/json" \
  -d '{
    "email": "newpeer@example.com",
    "password": "SecurePass123!",
    "name": "New Peer",
    "referralCode": "PEER_ABC123"
  }'

How to Check Your Referral Stats

# Get your referral code and referred users
curl -s https://api.proxies.sx/v1/peer-account/referrals \
  -H "Authorization: Bearer $JWT"

# Response:
# {
#   "referralCode": "PEER_ABC123",
#   "referralCount": 5,
#   "referralEarningsCents": 1250,
#   "referredUsers": [
#     { "email": "ne***@example.com", "name": "New Peer", "joinedAt": "2026-02-05T..." }
#   ]
# }

Status: Peer Account Portal (registration, login, referral dashboard) is being deployed. The referral code system is built and ready — codes are generated, referrals are tracked, earnings are calculated. The web portal to view stats is coming soon. In the meantime, referral codes can be passed during agent registration via the API.

Ways to Share Your Referral Code

Community Channels

Leaderboards & Competition

The Live Peer Board shows all peers ranked by earnings and traffic. Top earners get visibility and recognition.

SECURITY & TRUST

ANDROID SDK BETA

GitHub: github.com/bolivian-peru/android-peer-sdk

The Android SDK is currently in beta. API surface may change. Report issues on GitHub.

Installation

// build.gradle (app-level)
implementation("com.github.bolivian-peru:android-peer-sdk:1.0.2")

// settings.gradle — add JitPack
dependencyResolutionManagement {
    repositories {
        maven { url 'https://jitpack.io' }
    }
}

Usage

// Initialize
ProxiesPeerSDK.init(context, "api-key", config)

// Start sharing bandwidth
ProxiesPeerSDK.getInstance().start()

// Stop sharing
ProxiesPeerSDK.getInstance().stop()

IP Rotation via Accessibility Service

On non-rooted Android devices, IP rotation works by toggling airplane mode via an Accessibility Service.

1. User enables "Proxies IP Rotation" in device Accessibility Settings
2. Gateway/API sends rotate_ip_request to relay server
3. Relay forwards to device via WebSocket
4. SDK triggers AirplaneModeAccessibilityService
5. Airplane mode ON -> 10s delay -> airplane mode OFF
6. Device reconnects with new IP from carrier
7. SDK sends rotation_complete back to relay

// Check if rotation is available
if (sdk.isIPRotationAvailable()) {
    sdk.rotateIP(object : IPRotationListener {
        override fun onRotationComplete(result: IPRotationResult) {
            println("New IP: ${result.newIp}")
        }
    })
} else {
    sdk.openIPRotationSettings()
}

// Coroutine version
val result = sdk.rotateIPAsync()

Developer Revenue Model

App developers integrate the SDK and earn 20% of each GB routed through their users' devices. IP type is classified server-side via ASN lookup.

IP Rotation Messages

60-second cooldown between rotations. Rotation takes ~15 seconds (10s airplane delay + network reconnect).

LIVE PEER BOARD

Real-time view of all peers in the network. Auto-refreshes every 30 seconds.

SERVICES MARKETPLACE

Peers who share bandwidth can also build and list services on the Proxies.sx Marketplace. One registration gives you two independent capabilities:

Your peer identity carries over. Same wallet, same account, same reputation.

Browse the Marketplace →

LINKS

Discovery Files

Live Domains

GitHub

Social

Twitter/X | Telegram | GitHub