done.

Coding Agent

Charge when the code ships.

Not when CI passes. When the code lands and sticks.

Code review agents post suggestions on every PR. Most get dismissed. Some merge. Charging per review means your customers pay for every comment that goes nowhere. Outcome-based billing means you charge only when a suggestion is accepted, the PR merges and the change holds.

Billing logic

Price$5.00
Settlement48h

Conditions

IF
occurred▾
AND
occurred▾
AND NOT
occurred▾

How it works

From signal to settled charge

Step 1

Engineer opens a PR

Step 2

Agent reviews it and posts suggestions

Step 3

Engineer accepts a suggestion

Step 4

PR merges with the change included

Step 5

Charge fires if no revert arrives within 48h

Live demo

See it run

Your customer's repoAcme Corp

Pull Request

No pull request open

Create a PR to start the outcome lifecycle

Your done. account
Price$5.00
Settlement48h

Conditions

IF
occurred▾
AND
occurred▾
AND NOT
occurred▾

Outcomes

No active outcomes

Create a PR to create your first outcome

Include in next invoice

Nothing to bill yet

Settled outcomes will be queued here

More use cases

For teams charging when work gets done

Customer Support Agent

Bill when the problem is solved.

Not when the ticket closes. When the customer doesn't reopen it.

See how it works →
Support #4821Resolved
AI
I've updated your billing settings and applied the credit.
Perfect, that's exactly what I needed!
★★★★☆Not reopened · 48h window
SRE Agent

Earn when the system is back.

Not when the runbook runs. When the incident stays closed.

See how it works →
P1 · api-latency-spikeResolved
Root causeDB connection pool exhausted
Action takenRestarted pool, scaled replica
Duration4m 12s · automated response
No recurrence after 12h · charge confirmed

Launch outcome billing without rebuilding your stack

Book a 30-minute walkthrough of how it works