one endpoint,
every model

DreamRouter routes a single request across 374 models and 34,654 live targets. It swaps model names, picks healthy endpoints, and retries bad keys across thirteen providers.

one request in,
the best live target out

DreamRouter resolves the model name, round-robins to a healthy target, swaps in the upstream model id, forwards, and streams the reply back. If a key returns 401, 429, or 5xx, it cools that target for sixty seconds and retries the next one. Up to five attempts, across thirteen providers.

0
models
one name, many live targets
0
targets
subnet nodes + api keys
0
providers
merged into one endpoint

one request, a gentle journey

The router takes your call, finds a healthy target, and forwards. If something is off, it floats on to the next one.

1

You send one request

POST /v1/chat/completions with any model name. No provider-specific urls, no key juggling.

2

It resolves and round-robins

The model name maps to a pool of targets. A thread-safe cursor picks the next healthy one, spreading load evenly.

3

It swaps and streams back

Your model name is rewritten to the target's upstream id, the key is injected, and the reply streams straight back to you.

4

It retries on trouble

On 401, 429, or 5xx the target cools for sixty seconds and the router tries the next. Up to five attempts.

thirteen providers, one sky

Each one drifts into the same endpoint. Size shows how many targets it carries.

NVIDIA8,554
DashScope7,785
OpenRouter4,758
Gemini4,114
Claude subnet3,479
MiniMax2,392
Ollama1,848
GLM602
DeepSeek442
ZAI238
Kimi170
MiMo167
xAI105

Browse all 374 models →

quietly engineered

The bits that keep it calm under load.

Streaming, filtered

SSE replies pass through a filter that strips comment and event lines, so finicky parsers keep up. Non-SSE replies buffer and forward untouched.

Round-robin load spread

A thread-safe cursor hands out the next healthy target on every call, so traffic spreads evenly across the whole pool.

Idempotent cooldowns

A bad target is skipped for sixty seconds. Re-failing it never resets the timer, so flapping targets recover instead of looping.

Auth and IP gate

Public paths stay open; everything else needs a bearer token. An optional IP allowlist keeps it locked to your subnet.

ready to route?

Point your client at one endpoint. The router handles the rest.

https://apiarium-labs.hf.space/v1/chat/completions
Endpoint copied