Agent-tuned reasoning model with switchable low/high effort, cutting token use in high-frequency tool-call loops across a 256K window.
Output Speed *
Intelligence Index *
Context Window *
Input price
Output price
Performance
Token Efficiency, Not Peak Intelligence, Is the Point
Benchmarks
Artificial Analysis: Index 17, With Stronger Long-Context Scores Than Step 3.5 Flash
Output Speed
Intelligence Index
MMLU *
GPQA *
HLE *
LiveCodeBench *
Technical Specifications
What the model supports
Limitations & Trade-offs
Best-Fit Workloads
Where this model earns its place
Coding agent loops
StepFun specifically improved compatibility with coding tools and agent frameworks. Artificial Analysis reports 32.6% on Terminal-Bench Hard. That makes it a practical worker for repeated edit, run and inspect cycles in terminal or IDE agents. It is a fast, economical agent engine rather than a top-tier solver, so escalate difficult debugging to a stronger model.
Tiered-effort agent orchestration
The low/high effort switch lets one model cover both routine and demanding steps. StepFun reports 56% lower token consumption in low mode and 14% lower in high mode. Use low for tool selection, parameter filling and simple routing, and high for planning or recovery steps. These savings come from the vendor's own testing, so confirm them on your traces. Only two effort levels exist.
Long-context codebase and document reasoning
The 256K-token context window is paired with an AA-LCR score of 63.0%, up from 50.0% for the original Step 3.5 Flash, which suggests improved long-document reasoning. That suits repository-level questions, long log analysis and multi-document synthesis in text. Inputs must be text, and the weak non-hallucination rate means answers about facts not in context should be grounded or verified.
High-volume background automation
Artificial Analysis lists it as the lowest blended-price model among StepFun's tracked models. Combined with tool calling, JSON mode and measured output speed of 135 tokens/s, it fits non-interactive pipelines such as ticket triage, data-extraction agents and scheduled workflows. Slow first-answer latency makes it a poor choice where users are waiting in real time.