Reasoning effort mix · June 2026
5.5% of chat requests set a reasoning effort in June 2026. Of those, "token budget" was the most requested level at 5.3%.
Share of requests that set a reasoning effort, and the mix of effort levels among those requests.
Data through June 30, 2026Updated November 11, 2026
This is the permanent snapshot for June 2026. See the latest month (October 2026)
Share of requests that set effort, June 2026
Source: Requesty production gateway- token budget5.3%
- low4.2%
- high3.8%
- medium2.5%
- xhigh0.1%
- max0.1%
Key findings
Share of requests that set effort by month
What changed since May 2026
- medium6.6% → 2.5% (-4.2 pp)
- high5.0% → 3.8% (-1.2 pp)
- low3.8% → 4.2% (+0.4 pp)
- max0.2% → 0.1% (-0.1 pp)
What to do about it
- Set effort per task. Most traffic runs fine at low; keep high for planning and hard debugging.
- Measure cost per task before and after changing effort. Higher effort raises output tokens.
Set reasoning effort once and Requesty maps it to each provider's format.
Read about reasoningData
| Effort | Share of requests that set effort | Organizations (band) |
|---|---|---|
| token budget | 5.34% | 25-99 |
| low | 4.16% | 100-499 |
| high | 3.84% | 100-499 |
| medium | 2.46% | 100-499 |
| xhigh | 0.15% | 5-24 |
| max | 0.08% | 5-24 |
6 rows published. Rows below the floors are withheld.
Questions this answers
- What reasoning_effort do developers use most?
- 5.5% of chat requests set a reasoning effort in June 2026. Of those, "token budget" was the most requested level at 5.3%.
- How many API requests set a reasoning effort?
- 5.5% of chat requests set a reasoning effort in June 2026. Of those, "token budget" was the most requested level at 5.3%.
- Do developers use high reasoning effort?
- 5.5% of chat requests set a reasoning effort in June 2026. Of those, "token budget" was the most requested level at 5.3%.
Method and definitions
- Effort is read from the reasoning.effort or reasoning_effort request parameter. Numeric thinking budgets are grouped as token budget. Requests without the parameter count as not set.
- A row is published only when it has at least 20 requests, at least 5 distinct organizations, and no single organization above 80% of its traffic. These are the same floors /rankings uses. Rows below the floors are withheld, not estimated.
- Only shares, rates, medians and organization bands are published. Absolute request, token and spend totals stay private.
- Set effort:
- The request carried an explicit reasoning effort or thinking budget.
Caveats
- Requests that do not set an effort run at the model default, which differs by model.
- Some clients set an effort on every request even for models that ignore it.
Revision history and other months
- October 2026first published later
- September 2026first published later
- August 2026first published later
- July 2026first published later
- June 2026 (this page)first published 2026-11-11
- May 2026first published 2026-11-11
Cite and reuse
Free to reuse under CC BY 4.0. Credit "Requesty Data" and link to this page. Cite the month URL so the numbers you quote stay fixed.
APA
Click to copy
BibTeX
Click to copy
CSV
Click to copy