Billing Overview
Otto uses prepaid organization credits. Credits are consumed only from verified provider usage that Otto can trace to a request.
How Charges Are Calculated
Otto charges for the work each review or workflow actually performs, based on verified usage. Review charges are grouped by pull request, so you can see what each PR cost.
- Only verified usage is billed. Estimated catalog prices are for selection and previews only; estimates are not billed.
- Fractional cents are preserved and carried into later settlements instead of rounding each request up.
- Unknown usage stays pending until it can be reconciled. Otto does not fabricate costs or bill unknown usage as zero.
Request Billing Labels
Usage records and run details use these labels:
| Label | Meaning |
|---|---|
pending | Provider usage has not been fully verified or settled yet. |
charged | Verified usage was charged to the organization balance. |
waived | Usage was recorded but not billed, such as a terminally failed workflow attempt. |
internal | Super-admin console usage recorded for audit, not charged to customers. |
What Is Billable
- Successful customer workflows, including supporting summaries and sub-agent requests.
- User-requested cancellation, for verified model usage already consumed before cancellation completed.
- Recovery attempts that succeed or are otherwise billable under normal workflow rules.
What Is Waived
- Terminally failed root workflow attempts.
- Separately failed recovery attempts.
A failed attempt remains waived even if a later retry succeeds. Normal recoverable tool errors and negative review findings are not terminal failures by themselves.
Failure Pause Policy
Customer automation pauses when either threshold is reached for an organization:
- 3 consecutive terminal failed attempts, or
- $5.00 of absorbed actual provider cost in a rolling 24-hour window.
Successful work resets the consecutive-failure streak. Super-admin resume is audited and resets the streak, but it never deletes cost history; rolling absorbed failure cost must fall below $5.00 before resuming. There is no hard per-run dollar cap, so in-flight model calls can overshoot thresholds before dispatch is paused.
Views
Customer views
Customers can see usage by date, model, workflow, and run, including token details when available and each record's pending, charged, or waived state.
Admin views
Super-admin views include internal console usage, absorbed failure costs, pending records, and pause/resume audit information. Internal financial details are not exposed to tenant users.
Adding Funds
To add credits to your organization:
- Go to Settings → Billing
- Click Add Funds
- Select a preset amount or enter a custom amount
- Complete the payment through Stripe
Unused credits carry over indefinitely. Agents pause when available credits or failure-pause policy prevents dispatch.
Next Steps
- Understand Token Usage