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
When pricing depends on usage knowing where costs come from becomes pretty important.
exactly
Thank you everyone for the love and ideas to take this further. We are launching AUDR along with an initial set of adapters to get you'll going. We'd love for you to co-build adapters or share what you want us building out next.
Nemo Relay: https://github.com/openaudr/audr/tree/main/adapters/nemo-relay
LiteLLM: https://github.com/openaudr/audr/tree/main/adapters/litellm
Merge Gateway: https://github.com/openaudr/audr/tree/main/adapters/merge-gateway
Vercel SDK: https://github.com/openaudr/audr/tree/main/adapters/vercel-ai
Mastra: https://github.com/openaudr/audr/tree/main/adapters/mastra
Lago Sink: https://github.com/openaudr/audr/tree/main/sinks/lago
Chargebee Sink: https://github.com/openaudr/audr/tree/main/sinks/chargebee
lfg! and anyone can request more adapters by creating an issue here: github.com/openaudr/audr/issues
Hadn’t thought about this problem before but I can see why it’s coming up now.
thanks for the support, and they welcome contributions. see the public repo: github.com/openaudr/audr
@haozhe_li if you're launching agentic capabilities, chances are you're better off measuring the costs per run. Even if you are choosing to do a flat fee today, in the longer run it will pay off to have this instrumentation.
pricing for AI apps is moving so fast right now, flexible tiers are definitely needed.
@andrew_dale2 and that pricing flexibility can be better informed with a better grasp of AI costs.
exactly - there was a need for a standard way to track agent costs and usage. @Chargebee just fixed that.
usage based billing is such a headache to build from scratch. glad someone simplified this.
yes, and @Chargebee is a pioneer in this category!
Hi PH community, we’re really excited to launch AUDR.
The telecom industry has always had a standard, carrier-agnostic way of recording usage for each call. Today’s long-horizon agents need a similar standard that works across model routers, gateways, agent frameworks, and the wider AI stack. AUDR (Agent Usage Detail Record) is an open standard specification for recording agent usage and costs in granular detail.
At Chargebee, we help scale monetization for some of the fastest growing AI startups and enterprises. And one thing they all have in common is a granular understanding of AI costs. That understanding informs how creatively and sustainably they price. Whether it’s charging for active agent minutes, resolved outcomes, or an extremely hybrid model, they all share a deep grounding in tokenomics. AUDR is built to enable the same depth for everyone.
We’re thankful to teams at @Merge, @Mastra, and @openhumanfor their early reviews and contributions. We’ve already shipped adapters for NVIDIA NeMo Relay, Merge Gateway, Mastra, Vercel’s AI SDK, and LiteLLM.
Help us improve it at openaudr.dev
@cbkrish S/O for this new launch! psyched to see @Chargebee back on @Product Hunt. looking forward to what's next.
love it, observability becomes more important with scale, something simple like this was definitely missing.