Build1 publisher3 min readPublished
Uber's AI cost per session fell 18 points further than its cost per request
The gap implies each session now uses roughly a quarter fewer requests, so the compaction threshold and the prompt cache in Uber's own harness are carrying part of a saving usually credited to cheaper open models.
The Engineer · Build desk

What happened
- Uber blew through its annual AI budget in the first three months of this year, and its engineering teams then set to work on optimizing AI spend.
- Cost per AI request at Uber is down 34% and cost per AI session is down 52%, according to sources the Pragmatic Engineer newsletter spoke with.
- Uber's total AI cost has been flat since March even though the company keeps using more tokens and starting more AI sessions.
Compiled by The EngineerSomething wrong?How this is made
Why it matters
- constraint The open-model saving spans 2x to 20x, so a team whose workload lands at the low end cannot reach Uber's numbers by substitution and has to find the rest in its harness.
- capability Compaction thresholds, effort defaults, prompt caching and subagent tiering are all changes a team can land inside a harness it controls, with no vendor renegotiation.
- exposure Quoting a 56% saving means accepting a quality tradeoff, and the published AT&T account does not say what metric produced the 2% figure.
- precedent A flat AI line under rising usage is now a public number from a listed company's earnings call. Finance can now expect engineering to produce that same answer.
Take the two Uber percentages together. Cost per request is down 34%, so a request costs 0.66 of what it did. Cost per session is down 52%, so a session costs 0.48. Divide the second by the first: the average session now contains about 27% fewer requests than it did [1]. Requests per session is a property of the harness and the prompt loop. The inference holds only if the mix of work inside a session stayed roughly constant. If Uber's developers also changed what they ask for, part of that 27% is changed behaviour [1].
Two of the reported levers point straight at that ratio. Uber triggers automatic compaction above 400K tokens, even for models with 1M context windows [8], and it caches prompts when work runs through its own harness, Minions [9]. A third is a default: Uber found that defaulting to Medium effort gives the best cost-to-output ratio with advanced models [7]. Subagents get cheaper models because their tasks do not need the most expensive ones [6]. Compaction at 400K on a 1M-context model is a decision that the remaining 600K tokens are not worth their price [5].
The substitution saving is a range. The Pragmatic Engineer puts open models at 2-20x less than frontier ones [11], which is between 50% and 5% of frontier cost [2]. Pinterest's published figure sits near the cheap end. On last month's earnings call, CEO William Ready said "With open models, we are achieving cost per transaction at less than 8% of the cost of comparable closed proprietary models" [12]. Under 8% is better than 12x cheaper [3]. Ready also stated the condition attached to it: "When we leverage open source models, such as with Pinterest Assistant, we are seeing superior performance for our use cases when compared to closed third-party models because we are able to post-train open models on our highly unique data" [13]. To get 8%, you need the unique data, an environment to post-train in, and a use case narrow enough to post-train for.
AT&T, with 100,000 employees, cut its AI bill by 56% while measuring a 2% decrease in output quality after moving workloads to open models [15][16]. The substitution is partial. According to The Information, AT&T's software developers still rely on cutting-edge models for complex tasks, and Austin said he has found that open source models are "just as good or better" than older models sold by the likes of Anthropic and OpenAI [18][17].
The May list of approaches companies were trying included per-developer monthly AI usage limits [1]. That lever does not appear among the ones reported for Uber. What the Uber account supports is narrower: cost per unit down by a third to a half, and total spend flat since March while token use and session counts kept rising [4][5]. Uber has published an engineering blog post detailing dozens of optimizations to reduce token cost without noticeable change in the quality of code its agents generate [10].
What to watch
- Uber's engineering blog post is where a requests-per-session breakdown would appear, and it would confirm or kill the 27% inference.
- Whether Uber's weekly real-work benchmarks keep favouring open models as frontier vendors move their prices.
- Whether Pinterest's under-8% cost per transaction holds as Pinterest Assistant traffic grows beyond the post-trained use cases.