The Flow Layer
Sign in Get API key

Model routing layer

Route every model through one flow layer.

Browse capable model routes, compare latency posture, and send production traffic through one API surface without locking your product to one provider.

Browse models View docs
10 featured model routes 5 language editions 4 routing signals
Route preview flow_model_router
POST /v1/chat/completions
01
Request profile

Workload, modality, cost posture, and latency budget

7 ms
02
Model selection

Pick the best available route for text, agent, or video work

18 ms
03
Fallback path

Move to a compatible alternate when health or budget shifts

ready

Model directory

Compare models before you route traffic.

Model Best for Latency Route
Seedance 2.0 bytedance/seedance-2.0-video cinematic video generation queued video route DeepSeek V4 deepseek/deepseek-v4-pro reasoning, coding, long context fast text route Qwen3-Max alibaba/qwen3-max-thinking agentic reasoning balanced text route Kimi K2.5 moonshot/kimi-k2.5 long-horizon coding balanced text route GLM-4.7 zai/glm-4.7 software agents fast text route Tencent HY 2.0 tencent/hunyuan-2.0-thinking math, coding, tool use balanced text route Doubao-Seed-1.6 volcengine/doubao-seed-1.6 low-latency product chat fast text route Claude Opus 4.7 anthropic/claude-opus-4.7 deep reasoning and review balanced text route GPT-5.5 openai/gpt-5.5 general intelligence balanced text route Gemini 3.1 google/gemini-3.1-pro multimodal analysis fast text route

Provider channels

One API layer for every model provider.

Keep provider differences behind the route layer while product teams choose models by capability, cost, and reliability.

Provider catalog Normalize model IDs, modalities, context windows, and route tags.
Routing policy Choose preferred, fallback, and blocked routes per product workflow.
Usage visibility Trace cost, latency, errors, and route decisions from one surface.
Channel handoffs Send enterprise, deploy, and docs flows to their own workstreams.

Channel architecture

Home stays the hub; each channel owns its depth.

The homepage orients users around models and routing, then hands deeper jobs to the enterprise, deploy, and docs channels.

Architecture owner Enterprise channel Controls, budgets, approvals, and audit posture for managed teams. Linked from home Deploy channel Keys, environments, rollout gates, health checks, and fallback routes. Live page Docs channel Quickstart, SDK setup, route examples, and agent framework notes.