FLUX.2 Klein 4B
nearai/flux-2-klein-4b出品方： nearai · 系列: flux · 發布 2026-01-14
Prices in USD per 1M tokens. Unknown means the provider does not publish per-token pricing.
能力清單
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.
Coding3
- Tool calling0/40
- Structured output0/20
- Reasoning0/10
- Context window (100K → 1M)2/20
- Provider availability1/10
Agents16
- Tool calling0/35
- Structured output0/25
- Reasoning0/15
- Output token limit15/15
- Provider availability1/10
JSON / structured output26
- Structured output / JSON mode0/50
- Tool calling0/20
- Temperature control10/10
- Price-friendly for high-volume16/20
Cost efficiency55
- Headline price (log-scaled)55/95
- Has prompt-cache pricing0/5
Long context45
- Context window (100K → 2M)35/90
- Has published price for full window10/10
Vision78
- Accepts image input50/50
- Context window (10K → 1M)17/30
- Has published price10/10
- Provider availability1/10
Production-readiness65
- Number of independent providers5/40
- Has published per-token price20/20
- Context window ≥ 8K15/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.
| Scenario | Cost | Assumption |
|---|---|---|
RAG answer per 1,000 RAG answers | $5.50 < $0.01 per request | 5K input tokens (query + 4 retrieved chunks of ~1K each) and a 500-token answer. Typical SaaS knowledge-base bot. |
Support ticket triage per 10,000 tickets | $11.00 < $0.01 per request | 1K input tokens (ticket body + system prompt) and a 100-token JSON classification reply. High-volume customer support. |
Data extraction per 1,000 documents | $2.50 < $0.01 per request | 2K input tokens (a single document page) and a 500-token JSON extraction. ETL / invoice / form pipelines. |
Code review per 1,000 PRs | $9.00 < $0.01 per request | 8K input tokens (diff + surrounding files) and a 1K-token review comment. PR-bot workloads. |
Agent step per 1,000 steps | $12.60 $0.01 per request | 12K input tokens (long-running tool history) and a 600-token tool-call decision. Cost per agent step. |
定價詳情
推薦定價來自 nearai · black-forest-labs/FLUX.2-klein-4B
於 1 家供應商可用
| 服務商 | 服務商模型 ID | 輸入 / 1M | 輸出 / 1M | 上下文 | 發布日期 |
|---|---|---|---|---|---|
| NEAR AI Cloud nearai | black-forest-labs/FLUX.2-klein-4B | $1.00 | $1.00 | 128K | 2026-01-14 |
Frequently asked questions
How much does FLUX.2 Klein 4B cost?
FLUX.2 Klein 4B costs $1.00 per 1M input tokens and $1.00 per 1M output tokens, sourced from nearai. Cache reads, audio tokens and >200K-context tiers (where applicable) are listed in the Pricing detail block above.
What is the context window of FLUX.2 Klein 4B?
FLUX.2 Klein 4B has a context window of 128K tokens, with a max output of 128K tokens per reply. This is the total combined size of prompt + completion.
Does FLUX.2 Klein 4B support tool calling?
No. FLUX.2 Klein 4B does not support tool calling (function calling). If your workflow requires it, look at the /capabilities/tool-calling list for alternatives.
Does FLUX.2 Klein 4B support structured output / JSON mode?
Support for structured output / JSON-schema-constrained decoding is not reported for FLUX.2 Klein 4B in our data source. Verify with nearai's official documentation before relying on it in production.
Can FLUX.2 Klein 4B accept image input?
Yes. FLUX.2 Klein 4B accepts both text and image input. Vision pricing per image is usually billed on top of the regular token rate — check nearai's docs for the exact rule.
Is FLUX.2 Klein 4B open-weight?
Yes. FLUX.2 Klein 4B'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.
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
Capability lists this model is in
最近更新：
Pricing and capabilities are refreshed daily and reconciled against each provider's official documentation. Always verify critical production decisions with the provider directly.