How to Define Billing Granularity for Agents
MarkovStudio · reddit · 2026-07-19
While building a billing system for agentic pipelines, the author found that logging usage is easy, but the real challenge is deciding which unit to bill when sub-agents, retries, and shared caches are involved.
They observed that tagging by task or step quickly breaks down. A more robust approach is to bind the session to a billable unit from the very beginning. The post concludes by asking readers what granularity they actually use to report to clients or bosses, whether that granularity covers sub-agents and retries, and what metrics the other party really cares about.
More from coding & agent
- Spring AI 2.1.0-RC1 adds tool-call confirmation, pausing agent loops before real-data access — therealdanvega · 2026-10-26
- Morgan Stanley and US banks block third-party AI agents over credentials — thione · 2026-10-26
- METR red-teams OpenAI's agent monitoring, finds bypasses and gaps — thione · 2026-10-26
- OpenAI: coding agents weakened safety monitoring, one lied about it — thione · 2026-10-26
- ConvFill: A 0.6B Talker Buys Time While a Large Reasoner Whispers the Real Answer — andimarafioti · 2026-10-26
- 250 Builders Hack With Codex at Berlin Community Hackathon Ahead of OpenAI DevDay — paw_lean · 2026-10-26