# Amazon — How Airbnb uses cost per task to operate coding agents on Amazon Bedrock

- Company: Amazon (amazon.com)
- Announced: 2026-11-18T21:48:19+00:00
- Category: not stated
- Coverage: not counted
- Announcement: no
- Group: routine
- Source: https://aws.amazon.com/blogs/machine-learning/how-airbnb-uses-cost-per-task-to-operate-coding-agents-on-amazon-bedrock/
- Record: https://forck.live/items/38283-how-airbnb-uses-cost-per-task-to-operate-coding-agents-on-amazon-bedrock
- Subject: Bedrock / Nova

Airbnb runs coding agents for thousands of engineers through an internal LLM gateway on Amazon Bedrock, and uses cost per task to pick which models those agents default to. The company says eight new models arrived in about five weeks, and by mid-October roughly two thirds of the requests its engineers sent through coding agents went to those new models. Because each release can shift output tokens, cost, latency and capacity at once, Airbnb runs evals on its own engineering tasks before a rollout to measure each model's score and cost per task, defined as the list-price cost of all tokens an agent uses to finish one task. After a rollout, CloudWatch metrics in the AWS/Bedrock namespace show what changed in production, including InvocationLatency, TimeToFirstToken, InvocationThrottles and token counts for uncached input, cache reads, cache writes and output. Airbnb uses the eval results to set each default, the model and reasoning effort its coding tools use unless an engineer picks another, and each effort ceiling, the highest effort allowed for a model. The gateway records the model, client, team and user for each request, and Airbnb says it uses those records only in aggregate, for cost and capacity planning.

## Evidence

Verbatim from https://aws.amazon.com/blogs/machine-learning/how-airbnb-uses-cost-per-task-to-operate-coding-agents-on-amazon-bedrock/:

> Amazon Bedrock provides access to foundation models from multiple providers through a common API, with AWS managing the model infrastructure. It integrates with AWS access controls and monitoring, and processes prompts, code, and model responses within AWS.
> 
> As coding agents move into production, changes in models and usage can affect latency, capacity, and cost. Amazon Bedrock runtime metrics in Amazon CloudWatch help teams investigate latency increases, throttling, and changes in token consumption. Evaluations, or evals, complement these operational metrics by assessing the quality of an agent’s work on a fixed set of representative tasks.
> 
> In this post, we show how Airbnb evaluates models for coding agents and monitors their use on Amazon Bedrock. We explain how cost per task guides model selection and how production data helps us revisit those choices as usage changes. We also describe the runtime signals used to investigate latency, throttling, and spend.
> 
> At Airbnb, thousands of engineers and engineering-adjacent people use AirChat, our internal tool for running coding agents, every week.

---

Record: https://forck.live/items/38283-how-airbnb-uses-cost-per-task-to-operate-coding-agents-on-amazon-bedrock
Catalogue: https://forck.live/llms.txt
Current issue: https://forck.live/feed.md
