Value & ROI

The Value API connects metered agent cost to outcomes your customers can inspect and verify. Use cases are free-form responsibilities inferred from real work—not a fixed m8tes taxonomy—so an account can measure revenue generation, revenue protection, cash savings, capacity unlocked, and operational outcomes in the language its executives already use.

Evidence before ROI

Every observation requires source evidence. Attributed and estimated dollar claims remain pending until a human confirms them; rejected claims and pending amounts never enter verified ROI. Capacity converted to money is always estimated. Unquantified outcomes remain visible without being turned into invented dollars.

Executive reporting

The report separates verified value, pending value, shared platform cost, unattributed cost, and unquantified outcomes. It also breaks value and cost down by inferred use case. Lead with revenue generated or protected and cash saved; present capacity and operational outcomes separately so a time estimate never masquerades as cash or revenue.

Use user_id on every method for an embedded end customer. List methods use the standard limit and starting_after cursor contract. See Pagination, Human-in-the-Loop, and the API Reference.