Record metered agent usage
AUDR defines a shared record for one metered agent operation, joining run attribution with raw model or tool usage.
AUDR by Chargebee
Open standard for tracking agent run costs
The overview
What is AUDR by Chargebee?
AUDR is an open specification for recording who initiated an AI agent run and the usage costs accumulated as that run passes through different tools. It defines a shared record format and rules for joining application, router, and tool data, so teams can trace run-level usage across their stack.
Around the internet
What people are saying
Public experiences, questions, and discussions.
No discussions collected yet.
Inside the toolkit
Key features
Join records across a run
A shared run ID and span ID let a sink assemble records from components that report on the same operation.
Keep field ownership explicit
The harness owns attribution, the router owns usage, and merge conflicts are rejected instead of silently overwritten.
Use published adapters and sinks
The site lists adapters for NeMo Relay, LiteLLM, Merge Gateway, Vercel AI SDK and Mastra, with Chargebee and Lago sinks.
Where it fits
Use cases
- Analyze cost by agent runJoin usage records with customer and feature attribution to examine the unit economics of agent workflows.
- Send usage to a billing destinationDeliver emitted records to a billing sink or another downstream system for rating; AUDR itself does not define prices or rating logic.
- Store records for internal analysisWrite records locally or send them to a warehouse or observability system for internal cost analysis and projections.
Keep exploring
