StepFun Models
Usage
489M
2.7K
4 of 4
Which models that traffic went to
- step-3.5-flash63.0%308M
- step-3.7-flash37.0%181M
- step-3.7-flash75.9%2.1K
- step-3.5-flash23.7%648
- step-2-16k0.2%5
- stepfun-ai/step30.1%4
All 4 StepFun Models
Open in model list| Modalities | ||||
|---|---|---|---|---|
| step-3.5-flash | Takes text, vision, returns text. | 256K | $0.11$0.33/M | — |
| step-3.7-flash | Takes text, vision, returns text. | 256K | $0.22$1.32/M | $0.04/M |
| stepfun-ai/step3 | — | $1.10$2.75/M | — | |
| step-2-16k | — | $2.00$2.00/M | — |
StepFun on AIHubMix
Which StepFun model should I start with?
step-3.5-flash at $0.11/M input — the cheapest entry here that declares a token price, and it carries a 256K context. Move up to step-2-16k when answer quality matters more than cost.
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-), some are the open-weight repository form (stepfun-ai/…), 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.
How is cached input billed?
The Cache read column is the rate for input tokens served from the prompt cache — for example step-3.7-flash bills cache hits at 20% of the input rate. Cache write is the surcharge for putting a prompt into the cache in the first place, and only a few upstreams bill it separately. A dash in either column means the catalog carries no cache rate for that model, so plan on paying the full input rate.
Do I need a separate StepFun 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 StepFun in one line
One key, one endpoint, 844 models across 35 providers.
