FLUX.1-Kontext-dev
nvidia/flux-1-kontext-devVon NVIDIA · Familie: flux · veröffentlicht 2025-05-29
Prices in USD per 1M tokens. Unknown means the provider does not publish per-token pricing.
Fähigkeiten
Model fit scores
0–100 · higher is betterThese scores reward declared capabilities, context size, price and provider availability — they are not benchmark results. Use them as a directional signal alongside your own evaluation.
Coding1
- Tool calling0/40
- Structured output0/20
- Reasoning0/10
- Context window (100K → 1M)0/20
- Provider availability1/10
Agents1
- Tool calling0/35
- Structured output0/25
- Reasoning0/15
- Output token limit0/15
- Provider availability1/10
JSON / structured output0
- Structured output / JSON mode0/50
- Tool calling0/20
- Temperature control0/10
- Price-friendly for high-volume0/20
Cost efficiency0
- Has published price0/100
Long context0
- Context ≥ 100K0/100
Vision51
- Accepts image input50/50
- Context window (10K → 1M)0/30
- Has published price0/10
- Provider availability1/10
Production-readiness30
- Number of independent providers5/40
- Has published per-token price0/20
- Context window ≥ 8K0/15
- No data inconsistencies across providers10/10
- Official model (not derivative)15/15
Cost Efficiency Index
Open full calculator →Estimated cost using the recommended provider's headline rate. Each scenario fixes average input/output tokens — the assumptions are shown in the third column.
This model has no published per-token price, so we can't compute a cost estimate. See the provider's official pricing page for current rates.
Bei 1 Anbietern verfügbar
| Anbieter | Anbieter-Modell-ID | Eingabe / 1M | Ausgabe / 1M | Kontext | Veröffentlicht |
|---|---|---|---|---|---|
| Nvidia nvidia | black-forest-labs/flux_1-kontext-dev | Unknown | Unknown | Unknown | 2025-05-29 |
Frequently asked questions
How much does FLUX.1-Kontext-dev cost?
FLUX.1-Kontext-dev does not have a publicly published per-token price in our data source. This usually means it is gated behind enterprise sales or invite access. Check NVIDIA's official pricing page for the most current rates.
Does FLUX.1-Kontext-dev support tool calling?
No. FLUX.1-Kontext-dev does not support tool calling (function calling). If your workflow requires it, look at the /capabilities/tool-calling list for alternatives.
Does FLUX.1-Kontext-dev support structured output / JSON mode?
Support for structured output / JSON-schema-constrained decoding is not reported for FLUX.1-Kontext-dev in our data source. Verify with NVIDIA's official documentation before relying on it in production.
Can FLUX.1-Kontext-dev accept image input?
Yes. FLUX.1-Kontext-dev accepts both text and image input. Vision pricing per image is usually billed on top of the regular token rate — check NVIDIA's docs for the exact rule.
Is FLUX.1-Kontext-dev open-weight?
Yes. FLUX.1-Kontext-dev's weights are publicly available, so you can self-host or fine-tune. Note that open weights ≠ open source — the training data and code are typically not released.
What are the best alternatives to FLUX.1-Kontext-dev?
If FLUX.1-Kontext-dev doesn't fit, consider Nemotron 3 Ultra 550B A55B, Nemotron 3 Nano 30B A3B, Nemotron 3 Super 120B A12B. Each one targets the same use case — see the Related links below for direct head-to-head pages.
Where does this data come from?
All numbers are normalised into a single canonical model record and reconciled with each provider's official documentation. We re-pull daily and write any changes (price, context, capability) to the /changelog page.
Explore more
More NVIDIA models
- Nemotron 3 Ultra 550B A55B$0.40 in / $1.76 out
- Nemotron 3 Nano 30B A3B$0.05 in / $0.20 out
- Nemotron 3 Super 120B A12B$0.05 in / $0.25 out
- Nemotron 3.5 Super VL$0.06 in / $0.35 out
- Nemotron 3.5 Lightning 30B A3B$0.05 in / $0.15 out
Capability lists this model is in
Zuletzt aktualisiert:
Pricing and capabilities are refreshed daily and reconciled against each provider's official documentation. Always verify critical production decisions with the provider directly.