Docs
Billing outcomes
Hand a client a one-page invoice that defends every billable AI minute. Per-client / contractor invoice export (CSV + print-to-PDF), proof-of-work line items, consent-mode watermark, outcomes panel. Reuses /api/billing/by-account.
See it in motion
Where to find it
- Localhost:
/billing-outcomes.html?repo=<id> - API:
GET /api/billing/per-client/outcomes?repo=<id> - Keyboard: ⌘ K then
invoice - Navigation: LLM Cost Metrics in the sidebar, then Billing outcomes under All tools, in the Cost receipts group
What it does for you
Configure
Each session's cost is its tracked LLM API spend, summed from raw token counts. Human time is priced separately. An owner or admin sets a developer's hourly rate on the hosted team overview (paid plans, effective-dated), and the invoice carries a per-day labor section beside the session rows. With no rate set, those hours export as unpriced rather than as zero. The proof-of-work column is built from the session's causal links (each defect with its commit SHA and confidence band) and the lessons those defects produced; there is no free-text field to fill in.
Use it well
At the end of the billing cycle, filter by client + date range. Skim the proof-of-work column on the exported invoice: each session lists the defects it fixed under AI did, and the lessons that came out of it under I cleaned up. A session with no recorded causal link shows none in both columns, so decide whether it belongs on the invoice before you send it.
Read more
Last updated