Resolution layer

A resolution layer is the infrastructure that turns a stream of agent events into settled, billable outcomes. It sits between the agent and the payment processor. The agent does the work and emits events. The resolution layer interprets those events against billable conditions and contract terms, manages settlement, handles reversals and resolves what actually became billable. The payment processor then charges for it.

Why it exists

Traditional metering records consumption and assumes every recorded event is final. Agent outcomes behave differently: they accumulate state across many events and can be reversed before they are real. Billing them correctly requires a stateful system that evaluates conditions over time, waits out reversal windows and resolves conflicting signals. That system is the missing layer in most AI agent billing stacks.

What it must guarantee

• Determinism. The same events in the same order always produce the same charges.
• Exactly-once effects. Duplicate, late or out-of-order events never double-charge or corrupt state.
• Separation from the hot path. The agent emits fire-and-forget events and never blocks on billing logic.
• Auditability. Every charge traces back to the triggering events, the condition it satisfied and the settlement moment.

Teams that build this in-house discover they are maintaining a second product with financial correctness requirements. The engineering trade-offs are covered in How We Built witn's Outcome Resolution Layer.

Frequently asked questions

Related

• Outcome lifecycle in the docs
• Outcome-based pricing
• How witn works