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
Lane order per request: IPv6 Pool → WARP Free → Proxy Pool. A lane is used only when the one before it has no usable bucket.
—Pool Settings
Each Free request uses the next source, but the upstream meters the /64 block, not the address. A /64 prefix therefore yields exactly one bucket however many addresses rotate inside it; only a routed /56 or /48 gives one bucket per /64. 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.
Proxy Buckets
Import Proxies
Each proxy is a distinct /32 quota bucket, but public lists are scraped by everyone, so most are already spent. This lane is used only after the native /64 and every WARP tunnel are exhausted. Validation is free: a request with an invalid model passes the gate but is rejected before the request counter, so thousands of candidates can be qualified without spending quota. A proxy is retried only after its own Retry-After, and two consecutive failures retire it.