Flux Models
Usage
4.3M
312
4 of 5
- flux-2-pro
- flux-2-flex
- flux-2-pro
- flux-2-flex
- FLUX-1.1-pro
- flux-kontext-max
Which models that traffic went to
- Flux 2 Pro67.3%2.9M
- Flux 2 Flex32.7%1.4M
- Flux 2 Pro71.5%223
- Flux 2 Flex13.1%41
- FLUX-1.1-pro10.3%32
- Flux Kontext Max5.1%16
All 5 Flux Models
Open in model list| Modalities | ||
|---|---|---|
| FLUX-1.1-pro | Takes text, vision, returns vision. | $0.04 / img |
| flux-2-flex | Takes text, vision, returns vision. | $0.05 / MP |
| flux-2-pro | Takes text, vision, returns vision. | $0.03 / MP |
| flux-kontext-max | Takes , returns vision. | $0.08 / img |
| fx-flux-2-pro | Takes , returns vision. | $0.09 / img |
Flux on AIHubMix
Why are there several entries for the same model?
Because each row is a route you can call, not a model release. Some IDs name an upstream (azure-, alicloud-, cc-), and some differ only in capitalisation, kept so older integrations keep working.
The catalog does not carry a field saying which of those a given row is, so this page does not sort them into buckets it would have to invent. Every row shows that route’s own price, context and speed — compare those directly, and open a model to see the upstreams that serve it.
Do I need a separate Flux account?
No. One AIHubMix key covers every model on this page, and switching between them is a change to the model string — billing, rate limits, and logs stay in one place.
Start calling Flux in one line
One key, one endpoint, 985 models across 49 model authors.
