MagicRouter logo
MagicRouter AI Gateway

Sign In

MagicRouter logo
MagicRouter AI Gateway
Workspace
Connecting…

Overview

Gateway health and 24h traffic

Provider Topology

Active Recent Error Idle

Pool quota

aggregated across every account that reports quota
—

Traffic (24h)

Recent Requests

Promotional access pool

Free Workspace

Shared free capacity across connected services. Add providers in Accounts; their free-tier access is pooled behind one compatible endpoint.

API Keys

Page 1 / 1

Routing

Endpoint

OpenAI base
Anthropic base
Gemini base
Health

Point any OpenAI/Claude/Gemini-compatible client at these URLs and use a key from the API Keys page.

Dashboard Login

Change the dashboard password. Every other session will be signed out.

RUNTIME

Feature Flags

Applied immediately to new requests
Loading…

Add Custom Model

Routes the id straight to the chosen provider

Model Catalogue

loading…
M
Playground Ready — pick a provider and model
Enter to send · Shift+Enter for a new line · replies come from your real account pool

Compression

What we send upstream

Oldest turns are dropped until the prompt fits. The current turn is always kept.

Preview


          

Savings

no traffic yet

Recent requests

◇
TUNNEL POLICY Cloudflare WARP loading…

Tunnel

Destination policy routing only — SSH and the default route stay untouched

Upstream Latency

⬡
FREE EGRESS IPv6 Address Pool Not configured
StatusOff
Active Source—
Pool0 / 50
Reshuffle300s
CONFIGURATION

Pool Settings

Free accounts only · max 50 addresses
ⓘ

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.

ADDRESSES

Pool Members

◈
OPENCODE FREE WARP Quota Pool Not configured
StatusOff
Ready Buckets0 / 0
Rotations0
Rotate on 429On
TUNNELS

Quota Buckets

BEHAVIOUR

Rotation Policy

A new WireGuard session mints a new egress /64
ⓘ

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.

Dialog