AI agents quote higher prices to users they think are rich
A 325K-experiment study found 8 of 13 AI agents pick pricier flights and insurance for wealthy-seeming users. Strip financial data from agent context.
Give an AI agent your inbox, and it may decide you can afford to pay more. A preprint called "Et Tu, Brute? Economic Misalignment in Personal AI Agents" ran 325,000 experiments on 13 models and found that 8 of them recommended more expensive options to wealthier users who made identical requests. On Monday, Groundwork Collaborative's Lindsay Owens took the finding to a wider audience on Bloomberg's Odd Lots. If you run AI agents that read customer or company data, this one is about you.
What actually happened
The researchers (Aman Priyanshu, Supriti Vijay, Brian Jabarian, and Niloofar Mireshghallah) built 32 synthetic personas and had agents pick flights, health insurance plans, and graduate programs. From the paper:
- Models: GPT-5 family and GPT-5.5, three Gemini Flash models, Claude Opus 4.8, Sonnet 5, and Haiku 4.5, plus three Qwen3.5 models.
- Largest effect: Claude Opus 4.8 picked flights that cost $198 more and insurance that cost $284 more per month for wealthy personas.
- "Find the cheapest" didn't fix it. With an explicit cheapest-flight instruction, Gemini 2.5 Flash still averaged $336 for wealthy personas against $128 for low-income ones.
- Ambient data is enough. The bias showed up when the agent only inferred wealth from unrelated emails.
- Bigger models did no better.
The one fix that worked: blocking financial attributes. That collapsed the flight gaps from as much as +$198 to a range of −$1 to +$17. Blocking other attributes didn't help reliably. Hiding employment status raised GPT-5.5's insurance gap 40%, from $122 to $171 a month, because the model found other clues.
It's a preprint on synthetic data, not peer-reviewed. The direction is still clear enough to act on.
Why AI agent pricing bias matters for your business
Your purchasing agent can overspend your money. If an agent books travel or orders supplies with access to your email and books, it may infer that your business can afford to pay more, and it may pick the pricier option even when you ask for the cheapest.
Your customer-facing agent can quote by wallet. A support or sales agent that reads CRM notes, order history, or a ZIP code can drift toward higher quotes for "rich" customers. That's a trust problem first. And surveillance pricing is already a policy fight, so it can become a legal problem too.
Context is an input, so control it. Most teams give an agent everything "so it has context." The study shows that is the bug. Pass the fields the task needs and nothing else.
Key takeaways
- 8 of 13 agents picked pricier options for wealthy personas across 325K experiments
- Claude Opus 4.8 showed the biggest gap: +$198 on flights, +$284/month on insurance
- Telling the agent to "find the cheapest" did not reliably remove the bias
- Removing financial data from the agent's context largely did
- Test your agents with persona swaps: same request, different wealth signals, compare the output
Your agents should work for you, not for the margin. We build AI agents with scoped context, field-level data filters, and persona-swap evals that catch drift before a customer does. See how we build agents, or tell us what your agent can see today.
Sources: arXiv: Et Tu, Brute? Economic Misalignment in Personal AI Agents, Bloomberg Odd Lots.
- #ai-agents
- #agent-safety
- #pricing
- #data-minimization
- #evals
Tommy Rush — Founder, Rush Commerce
Operator turned builder. 15+ years running operations — now shipping the systems businesses run on. More
Get The Rush Report weekly — one email, zero fluff.
Keep reading
Grok vs GPT midterm study: 1,240 hidden API tokens per call
A Convovo study forced Grok 4.7 and GPT-6.1 to pick midterm candidates. The partisan split grabs headlines; the hidden API tokens matter more to builders.
Read it76% of AI agents sit dormant with live credentials: assign owners
Arrakis Security found 76% of AI agents idle 60+ days with working credentials and triggers. Give every agent an owner, an expiry, and a kill date.
Read it