Decision models take 26% of requests; Anthropic now wins new teams 2:1
Vercel’s October gateway data shows decision models taking 26% of requests but 0.53% of spend, while model use shifts quickly. Treat routing and model choice as workloads to revisit, not fixed defaults.
In Vercel’s October 2026 gateway data, decision models handled **26% of requests** and **0.53% of spend**; they classify, score, or choose rather than generate text. About 11% of paid teams used voice models, and more than half of language-model requests went to models under 60 days old.
For agent builders, consider routing simple classification or selection steps to decision models, and budget time to reassess model choices as releases change. Vercel reports that teams processing at least 10 million tokens a month often changed their most-used model between September and October.
In Vercel’s October 2026 gateway data, decision models handled **26% of requests** and **0.53% of spend**; they classify, score, or choose rather than generate text. About 11% of paid teams used voice models, and more than half of language-model requests went to models under 60 days old. For agent builders, consider routing simple classification or selection steps to decision models, and budget time to reassess model choices as releases change. Vercel reports that teams processing at least 10 million tokens a month often changed their most-used model between September and October. The report covers anonymized traffic routed through Vercel AI Gateway, not the whole market. Spend is estimated at list prices, and the vendor’s model classifications and customer mix shape the results.
This gateway snapshot adds a large request share but small spend share for decision models, alongside evidence of rapid model turnover among heavy-usage teams. It supports separating selection and classification workloads from generation and revisiting routing choices, while remaining a vendor-specific traffic sample rather than a market-wide account or quality comparison.