Published outcome data
Published outcome definitions
A dated, sourced registry of published outcome definitions, states, prices, review windows, and correction rules.
View as MarkdownWho decides whether the outcome happened?
A vendor rule says what counts in the vendor's own terms. Vendor verification means the vendor runs an additional check. A buyer-defined rule lets the customer set the test. An external authority, such as an issuer or program triage team, makes the decision outside the vendor.
Vendor verification
| Vendor and outcome | Class | Unit | Price | Authority | Policy details | Source | Last verified |
|---|---|---|---|---|---|---|---|
| Horizon3 NodeZero finding retest | Vulnerability finding | asset | Not publishedInferredprice per asset, not per outcome | Vendor verification | Source | ||
| PostHog self-driving pull request | Code change | pull request | $15.00Published list | Vendor verification | Window: soak window Correction rule: refunded if it "wasn't worth paying for" Refund and credit policy: refunded if it "wasn't worth paying for" | Source | |
| Zendesk AI agents assisted escalationAwaiting verification | Support handoff | assisted escalation | $0.00Observedfree | Vendor verification | Source | ||
| Zendesk AI agents contained resolutionAwaiting verification | Support resolution | contained resolution | $0.00Observedfree | Vendor verification | Source | ||
| Zendesk AI agents verified resolutionAwaiting verification | Support resolution | verified resolution | $1.50Observed$1.50 on a committed pack, $2.00 pay as you go, reported second-hand; tiers verified | Vendor verification | Window: 72 hours | Source |