Getting started

Environments, authentication, and the buyer vs provider mental model.

ProxyHubb has two sides: buyers consume residential bandwidth through the edge gateway; providers run a node and earn from metered usage. Settlement is Solana-backed on public testnet (devnet).

Environments (testnet)

Override the buyer endpoint locally with PROXYHUBB_PROXY_ENDPOINT or NEXT_PUBLIC_PROXY_ENDPOINT.

Authentication

Mint API keys in the dashboard (Settings → API keys) or via POST /v1/bulk/api-keys with a JWT.

Wallet login (challenge → signed login → refresh) is the public auth path. Email/password registration is not an active runtime flow.

Two buyer paths

1. Connect session intent — dashboard JWT → POST /v1/sessions/intent → use session-intent:<token> at the buyer proxy. Best for rotating/sticky quick-start in Connect.
2. Marketplace order — create order → fund Solana escrow → GET /v1/orders/:id/credentials → username/password at the same buyer host.

Bulk pools are a third path for partners who want many endpoints under one API key.

First request checklist

1. Open Connect or mint a JWT via wallet auth.
2. Create a rotating intent (UI or SDK).
3. Smoke-test: curl -x "http://session-intent:[email protected]:8090" https://httpbin.org/ip
4. For longer-lived access, place a marketplace order and fetch credentials.

Common errors

Next steps

• Buyer proxy protocol
• Install an SDK
• Browse the API
• Run a provider node