Who uses a Verdict API?
Anyone who stands between two transacting parties — or transacts with a stranger — and needs disagreement to have somewhere credible to go. Four markets, four worked cases, all running on the same endpoint and the same published doctrine.
Agent platforms · x402 facilitators · wallet & rail builders
When a Claude agent and a GPT agent disagree
Agent-to-agent commerce settles in seconds on rails that are final by design. When the buyer agent and seller agent disagree — about money, or just about what to do next — there is no support inbox. Recourse is the resolver both sides pre-authorize.
Read the case →Freelance & contractor platforms · P2P marketplaces · Trust & Safety leaders
The dispute queue is a court you never wanted to run
Upwork-class platforms adjudicate thousands of work disputes with support agents: slow, inconsistent, expensive — and structurally conflicted, because the judge profits from the transactions it rules on. Outsource the judgment; keep the customers.
Read the case →Escrow providers · PSPs · platforms on Stripe Connect
Escrow without adjudication is a timelock
Every escrow product has the same missing sentence in its docs: what happens when the parties disagree. Recourse is that sentence — a signed money instruction your rails execute, with our liability behind it, never touching the funds.
Read the case →Independent professionals & their clients — no platform required
CC the court: dispute protection inside your inbox
Most service work never touches a platform — it's a Gmail thread between a client and a freelancer. CC Recourse on the thread and the venue travels with the conversation: terms witnessed, log preserved, ruling available if it ever goes wrong.
Read the case →