Adopt new pricing models — tiered, volume, stairstep, usage-based, flat-fee, or any custom model, without outgrowing your billing system. Trusted by 6,500+ businesses globally, including world-class companies like Zapier, CodeRabbit, Gorgias, and DeepL.
This is the 6th launch from Chargebee. View more
AUDR by Chargebee
Launching today
AUDR (Agent Usage Detail Record) is an open standard, for capturing who initiated an agent run and what it cost across every system that run touches. Inspired by the telecom industry's Call Detail Record, AUDR defines a common JSON schema that any harness, router, or billing system can emit and ingest. Three core rules make it work: a shared run ID minted by the harness, clear field ownership, and strict merge rules where conflicts are rejected and corrections are new records.
Launch Team
@Chargebee pioneered the SaaS industry (first launched here in 2014), and so they do in the AI economy.
Agents call tools, hit APIs, even pay per request with products like pay.sh by @Solana Foundation. AUDR (Agent Usage Detail Record) is the logical next step, and it's open. @Chargebee pushed the initial commit, adopted by @Mastra, @Merge, and more.
Star this repo: github.com/openaudr/audr
@fmerian thanks so much, Flo! Excited about this launch. There's a huge need for a standard way to track agent costs and usage. We're grateful for early reviewers and advocates who have contributed thus far. Big shout out to @Merge , @Mastra, and @OpenHuman teams.
What usually causes companies to hit that point in the first place?
@linpeng
Couple of triggers
1. Agent-as-capability consuming tokens faster than assumed
2. How you monetize agents not in sync with usage leading to a feeling of leaving money on the table
3. Lack of insights around margins per customer/account given tracking is not detailed
looks super sharp. how is the migration process for existing subscribers?
@irsa_doham Thanks! There's no migration required. Because AUDR is a usage record format rather than a billing system, your existing subscriptions remain completely unchanged. You add AUDR adapters to your agent stack to emit usage records, and a sink feeds them into your current billing setup.
yes, and I would add that for developers to get started easily, the spec plan includes adapters for key platforms and frameworks, including @NVIDIA, @Merge, @Mastra, and @Vercel.
read the spec, write an adapter, and help improve it: openaudr.dev
Observability for Agents is a big deal these days. It is something many organizations are trying to solve for but the solutions are limited. This looks pretty cool
Can we plug this into our existing stripe account or do we have to migrate everything over?
@sandy_leventh No migration needed. AUDR is an open spec for usage records and not a billing system. You'll need a sink that drains AUDR events into Stripe's meters while rating and invoicing stay within Stripe.
Chargebee sink is the first one published and the spec is Apache 2.0, so anyone can build a Stripe sink.
yes, and the project welcomes contributions! see the repo: github.com/openaudr/audr
does it support automatic usage warnings before a user hits their monthly limit?
@charles_eric3 That's handled by your billing system. AUDR only standardizes how usage and cost are recorded. Chargebee Usage Based Billing tracks consumption against limits in real time, and Stripe has usage-threshold alerts on its meters.
When pricing depends on usage knowing where costs come from becomes pretty important.
exactly