Unverified50% confidenceBenchmarkExact time
On the same two-bug repair task, omitting the effort field (default max) consumes an average of 6,364 thinking tokens, 56 seconds, and $0.0045 per repair, whereas the low setting uses an average of only 591 thinking tokens, 9.5 seconds, and $0.0006.
1
Sources
50%
Confidence
Short-term (~14 days)
Relevance
10/19/2026
First Seen
Valid until: 11/2/2026
Sources
Related Entities
Related Claims
UnverifiedAt AIHubMix pricing (input $0.165, output $0.66, cache reads $0.0165 per 1M tokens), the default max setting makes thinking tokens account for 95% of output (6,364/6,673), with thinking cost more than 10 times that of the low-intensity setting and latency close to 6 times.75% similarUnverifiedIn a ten-step Agent run scenario (500-token system prompt, 200-token task description, about 780 tokens of history per step, 150-token output), using all 18 tools costs $0.150 per run, of which the Schema cost is $0.048, accounting for 32%.71% similarUnverifiedThe vendor claims a median Token count of 2700 per ticket, 1.2 API calls, an inference cost of $0.003, and a wall-clock time of 3.5 seconds.69% similarUnverifiedUnder an assumed Agent bug-fixing session of 40 calls, 1.2 million input tokens (90% cache hit rate) and 60,000 output tokens, calculated at AIHubMix list prices, Flash 1017 costs $0.118 at peak hours and $0.059 off-peak; Pro 0813 costs $0.469 at peak and $0.233 off-peak; Pro costs about four times as much per session as Flash.69% similarUnverifiedIn the warm cache case, a /compact request on a 136.4k token context costs about $0.056–$0.059, which is 1.8–1.9 times that of a normal turn (about $0.031).69% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1067174API
curl https://kongchang.com/api/v1/knowledge/claims/1067174MCP
get_claim(id=1067174)