Provider Topology
Pool quota
aggregated across every account that reports quotaTraffic (24h)
Recent Requests
API Keys
Routing
Endpoint
Point any OpenAI/Claude/Gemini-compatible client at these URLs and use a key from the API Keys page.
Dashboard Login
Feature Flags
Model Catalogue
loading…Compression
What we send upstreamPreview
Savings
no traffic yetRecent requests
Tunnel
Destination policy routing only — SSH and the default route stay untouchedUpstream Latency
—Pool Settings
Each Free request uses the next source. With a /64 the upstream quota is shared by everyone in that prefix, so rotation alone cannot add capacity; with a routed /56 or /48 each address lives in its own /64, and an exhausted /64 is replaced by a fresh one automatically. Addresses use preferred_lft 0 so the host's normal IPv6 source is unchanged.
Pool Members
Quota Buckets
Rotation Policy
Each WARP tunnel carries its own /128 but Cloudflare assigns the egress prefix per session, so re-handshaking the peer produces a new /64 — and the upstream quota is keyed by that /64. A daily limit therefore burns only one tunnel: it is cooled, rotated, and the other buckets keep serving. Prefixes that already returned the daily wall are remembered and skipped. When every bucket is walled, the pool keeps rotating in the background and the request waits instead of failing, so an agent session is not aborted mid-run. Routing stays per-source (from <addr>/128); the default route and the router are never touched.