Metric contract · rolling 30d
How AgentPay calculates safety incidents.
Payments recorded as unsafe or unresolved after money may have moved.
Current value
incident
2
Confirmed or unresolved post-payment events requiring review
target: 0
Formula
COUNT(spend outcomes recorded as "unauthorized")
AgentPay counts each rolling-window execution outcome that requires incident review. Today this includes post-payment rail failures where settlement may have occurred but a card was not returned. Each recorded row counts once.
- Source
- kpi_snapshot.unauthorized_spends
- Target
- 0 incidents in the rolling window
- Window
- Rolling 30 days
- Refresh
- Every 60 seconds
Included
- Outcomes explicitly recorded as unauthorized by execute_purchase.
- Post-payment rail failures where settlement remains unresolved.
Not counted
- Requests refused before any payment was sent.
- Authorized outcomes with a verified signed-intent match.
- Missing telemetry, which is displayed as not measured rather than zero.
How to read the status
On target
A measured sample exists and the incident count is zero.
Incident
Any value above zero requires investigation and reconciliation.
Not measured
Telemetry is unavailable or no decision sample exists.
What this number cannot prove
A zero proves only that no incident was observed in the measured sample. It does not prove safety when telemetry is missing, stale, or has no recorded decisions.
Other calculations