1. Provide a comprehensive list of every billable unit your platform meters, and describe the metering mechanism for each. Include units such as input/output/cached tokens, embeddings, image/audio units, fine-tuning, tool calls, retrieval operations, and other agent-step actions. For each unit, specify whether it appears on the invoice or is visible only in usage reports.
Why it matters. AI products bill in heterogeneous units that don't map to traditional license SKUs. Buyers need a complete inventory of billable units to forecast spend. Agentic workflows can multiply costs through chained tool calls and retrievals, so visibility into the cost of each step is critical, not just the top-level request, to avoid significant hidden costs.
- Provides a complete, well-defined list of all billable units.
- Clearly distinguishes metering for different token types (input, output, cached).
- Details per-step accounting for agentic workflows (tool calls, retrieval).
- Vague answer referring only to 'tokens' or 'API calls'.
- Fails to distinguish costs for tool calls or agent steps from primary generation.
- Only meters the top-level user request in an agentic workflow.