Pay for the outcomes that happened.
Outcome-priced vendor invoices, verified against your systems of record. Monthly statements, invoice reconciliation, dispute packages. A billed outcome is an agent action like any other: CommitLayer verifies it against your helpdesk, CRM and billing systems, not against the vendor's report.
Statements from the Team plan. Read-only connectors. Paid by you, never by the vendor.
Outcome-priced vendors, each cited to its public definition.
Definitions are transcribed from the vendor's own documentation and carry the retrieval date. Where the documentation does not say, the field is marked unknown rather than guessed.
- Intercom Fin
- Zendesk AI
- Sierra
- Decagon
- Salesforce Agentforce
The agent may grant access only to a person HR lists as active, only to an allowed group, and for at most 90 days. A successful grant must show up as a group membership in the identity provider, a closed access request and a notification to the person's manager, within 15 minutes. One grant per request, at most twenty grants per agent per day. A membership removed within an hour of being granted, or a person who leaves while still holding the access, fails the grant.
Retrieved 2026-10-11 · 0 unknown fields
The agent may move an appointment only while it is still scheduled and not more than 30 days out. A successful reschedule must show up as a new slot in scheduling, a freed old slot, a note in the record system and a message to the patient, within 10 minutes. One move per request, at most two moves of the same appointment in a week, and the new slot must never be double-booked. A no-show or a cancellation within 7 days fails the reschedule.
Retrieved 2026-10-11 · 0 unknown fields
The agent may place an order only on an allowed product, on an allowed side, within the per-order notional limit, and within the agent's 24-hour total. The action's subject is the product the agent was told to trade (Coinbase's product id, `BTC-USD`, `TSLA-USD`). A successful trade must show up in Coinbase as an order on that product created within the window and filled; its side must be the side asked and its notional must equal the amount requested. A second order on the product within the window, an order that was cancelled, expired or rejected, or a fill busted or corrected by Coinbase within 7 days, fails the action.
Retrieved 2026-11-03 · 1 unknown field
Decagon states you pay only when the AI resolves a conversation from start to finish and that there is no charge when the case is passed to a human. The vendor notes that defining a resolution 'can be tricky'. No public operational definition exists, so the vendor lens below is a conservative placeholder to be replaced with the criteria in your Decagon order form.
Retrieved 2026-09-11 · 6 unknown fields
Two lenses on every billed outcome.
The vendor lens follows the vendor's published definition. The strict lens applies longer windows and additional checks. The gap between them is your definition delta.
| Reason code | Label | In plain language |
|---|---|---|
| reopened_within | Reopened after claim | The record was reopened inside the contract's reopen window, so the resolution did not hold. |
| no_customer_reply_within | No customer reply in window | The customer did not write again within the window after the claimed outcome. |
| escalated_to_human_within | Escalated to a human | The conversation was escalated or assigned to a human agent inside the window. |
| refund_or_credit_within | Refund or credit issued | A refund or credit was issued to the customer inside the window after the claim. |
| duplicate_claim_for_subject | Duplicate claim for subject | Another claim for the same subject exists in the same billing period; only the earliest counts. |
| verified_condition_not_met | Verified condition not met | None of the conditions that would verify the claim were satisfied. |
| no_structured_signal | No structured signal | The subject exists in the fact sources but none of the record types the definition depends on were observed. |
| missing_fact_source | Required fact source not connected | A fact source the definition depends on is not connected, so there are no facts to verify against. |
| identity_unmatched | Subject not found in fact sources | The claim's subject could not be found in any connected fact source, so nothing can be verified either way. |
| outside_billing_period | Outside billed period | The claimed outcome occurred outside the billing period on the invoice. |
From statements to disputes.
One vendor, one period. Pick the contract, see which of its fact sources your connections cover, upload the vendor's export with a mapping that is remembered, run.
Every billed outcome in the period, verified under the vendor's own definition and under a strict lens, with the delta between them.
Line-by-line comparison of the invoice or usage export against the verified count, with reason codes for every gap.
A hashed, exportable bundle of the claims, the facts and the verdicts behind a disputed line, ready for the vendor.
What the vendor counts, what a stricter reading counts, and how far apart they are month over month.
Each vendor's outcome definition transcribed from its public documentation with the retrieval date; unknown fields stay unknown.
Every statement and dispute package carries a hash that anyone can check without an account.
Monthly statements from Team; invoice reconciliation and dispute packages from Growth. Each billed outcome verified is one verified action against the same allowance. Pricing.
How large might your definition delta be?
Enter what you are billed and an assumed strict-lens rate. The output is a range, labeled as an estimate; the real number comes from your facts and your contract.