FLUX Dev
FLUX Dev is served by 2 providers that kRouter can route to, with a 200K-token context window. Because more than one provider offers it, the price you pay depends on which one you route to — the same request, the same model, different bills.
Where to get FLUX Dev
| Provider | Route as |
|---|---|
| ComfyUI | comfyui/flux-dev |
| Black Forest Labs | black-forest-labs/flux-dev |
What FLUX Dev is suited for
A 200K window comfortably holds a long file plus its surrounding context, which covers most day-to-day coding turns without compaction. It answers directly rather than reasoning at length, which keeps latency and output cost down on routine edits. Tool and function calling are supported, so it can drive an agent loop.
Specs
- Context window
- 200K
- Max output
- 64K
- Input / 1M
- —
- Output / 1M
- —
- Tool / function calling
FLUX Dev FAQ
How much does FLUX Dev cost?
FLUX Dev has no published per-token rate here — it is served through plans or free tiers rather than metered billing.
Which providers serve FLUX Dev?
2 providers: ComfyUI, Black Forest Labs. Through kRouter you can switch between them by changing the route prefix, without changing your tool.
What is FLUX Dev's context window?
200K tokens, with up to 64K tokens of output. kRouter publishes this on /v1/models as context_length, so clients read the real number instead of guessing from the model name.
Route to FLUX Dev from any tool
kRouter runs locally and gives Claude Code, Cursor, Codex and the rest one endpoint that reaches every provider above — with automatic failover. Free and MIT-licensed.
Install kRouter