Autonomous agents do not respect per-call pricing. They loop, branch, and spin up tools without supervision. The fix is selling AI agent credit packs that map to measurable automation units. Here’s how we structure them inside UsageBox.
Define the Agent Meter
Agent loops combine LLM tokens, tool invocations, and human approvals. We expose three native meters:
- Agent run: Every full workflow execution, tagged with depth and success rate.
- Tool minute: External API or workflow runtime billed per minute.
- Supervision slot: Human-in-the-loop checkpoints measured in decisions per hour.
Packaging Credit Packs
- Starter: 10K agent runs + 50K tool minutes, ideal for pilots. Includes built-in guardrails from the enforcement article.
- Growth: 100K agent runs, burst multipliers, and revenue-share triggers for automation above 60% adoption.
- Mission Critical: Unlimited tool minutes with dedicated support, premium SLAs, and shared FinOps dashboards described in the AI FinOps dashboard guide.
Enforcement Patterns
Credit packs only work if enforced. UsageBox policies watch:
- Run replay: Agents that retry more than 3× consume extra credits automatically.
- Agent depth: Additional branch depth (chain-of-thought steps) maps to multipliers so long reasoning is monetized.
- Outcome gating: Credit refunds only apply when supervisors flag false positives within 24 hours.
Revenue Experiments
Sales teams pair agent credit packs with outcome-based bonuses. Examples:
Support Automation
Charge per agent-assisted resolution plus an NPS lift bonus.
Sales Co-Pilots
Bundle 500 agent runs/month with revenue-share on meetings booked.
Launch Checklist
- Attribute historic agent telemetry into the UsageBox staging environment.
- Model pricing experiments with the pricing experiment toolkit.
- Ship customer-facing ledgers showing agent runs consumed vs. outcomes generated.
Once customers can visualize the automation ROI, credit packs become the default upsell motion.
For the memory side of agentic workflows (what the agent already learned, retried, or charged for in prior sessions), see memnode, purpose-built MCP memory pairs naturally with credit-pack billing.