You don't want to be the judge.
Name us in your terms once.

Recourse is a Verdict API: dispute bundle in — terms, interaction log, deliverable — reasoned ruling out in minutes. Fault in percentages, a money instruction your escrow partner executes, and the reasoning published behind every decision.

In this first release, the arbitrator is Claude — Anthropic's frontier model — ruling under our published doctrine, with a built-in appeal round and a human bench on escalation. We say so plainly, because a venue you can't inspect isn't a venue.

RULED IN 94s
RECOURSEdsp_4b81e2 · marketplace-contractor-v1

Logo package — rejected on taste after delivery to spec

claimant 75%respondent 25%
SPLIT — $450.00 releases to provider · $150.00 returns to buyer
  1. [MC-2] The deliverable met the written spec; taste is not breach.
  2. [MC-5] The buyer rejected without giving the offered cure a chance.
  3. [MC-3] One day's delay on a ten-day deadline — a modest deduction.

Who decides — stated plainly

The arbitrator is Claude. The doctrine is ours. The appeal is yours.

Claude rules first instance

Every case is decided by Claude against the published doctrine — rule-cited reasoning, proportional outcomes, a confidence score. No black box: you read exactly why you won or lost.

Both sides are heard

In the dispute room, claimant and respondent each submit their own statement and evidence through private links. Neither side controls the record alone.

One appeal, either party

Disagree with the ruling? File grounds and Claude re-adjudicates in full — first ruling and your objections before it. The appeal decision is final at the venue.

Humans where it matters

Low confidence, high stakes, statutory questions — escalations pass the Recourse bench before any instruction becomes final.

Quickstart

Your first verdict in five minutes

# 1. Sign up at /signup → generate a key (25 free rulings, no card)
# 2. POST your first dispute:
curl https://api.recourse.so/disputes \
  -H "authorization: Bearer rk_live_..." \
  -H "content-type: application/json" \
  -d '{ "rulepack": "marketplace-contractor-v1", "currency": "USD", "amount_minor": 60000,
        "terms": { "format": "text", "content": "Logo package, one revision round, 10 days, $600." },
        "claim": { "by": "claimant", "claimed_breach": "Not professional quality." },
        "log": [ { "at": "2026-06-12T16:30:00Z", "actor": "respondent", "kind": "delivery", "content": "Delivered per spec." } ],
        "deliverables": [] }'
# → fault allocation, money instruction, reasoning trace. That's the integration.

Or skip the terminal entirely: the playground runs the same engine in your browser.

Four doors in

Who it's for

Agent ecosystems

Agent-to-agent commerce

A Claude agent and a GPT agent disagree — over an x402 payment, or just over how to proceed. Neither vendor's model can be the judge. Recourse is the model-agnostic resolver both sides pre-authorize, with declaratory rulings for disputes where no money moves at all.

Marketplaces & platforms

Freelance & P2P marketplaces

Upwork-class dispute queues run on support agents: slow, inconsistent, conflicted. Outsource the judgment at a fraction of cost-per-ticket — proven on your own queue by a 30-day shadow pilot.

Escrow & payment rails

Escrow providers & PSPs

Escrow without adjudication is a timelock. One signed webhook completes the product — executable on fiat escrow, Stripe Connect, Tempo, or x402, while you keep custody and the customer.

No platform at all

The email witness

Most service work is just a Gmail thread. CC the venue on the thread — terms witnessed, log preserved, ruling on demand. Early access for independent professionals and agencies.

The venue goes where the deal is

Summon the court from anywhere

The API is the engine — but disputes start in tickets, inboxes, and group chats, so the venue meets them there. Every channel is a front door to the same doctrine and the same reasoned ruling:

⌘ Verdict API live ✉ CC it on the email thread early access ◳ Zendesk sidebar pilot ✈ Telegram group bot waitlist ◎ WhatsApp group waitlist ⬡ MCP server for agents in dev

All channels, statuses, and waitlists → Channels

The lifecycle

How it works

I

Submit the bundle

POST /disputes with the agreed terms, the chronological log, and the deliverables. Your systems already have all three.

II

Get the ruling

Percentage fault allocation under published doctrine, a money instruction that sums exactly to the disputed amount, a rule-cited reasoning trace, and a confidence score. Minutes, not weeks.

III

Enforcement executes

One signed webhook to your escrow partner: release, refund, or split. Recourse never touches funds.

IV

Escalation when warranted

Messy evidence, high values, or low confidence route up the ladder to Recourse's own review bench — never back to your team. See below.

Every tier is ours, never yours

Who judges? The escalation ladder

Every tier is staffed by Recourse, never by your platform. That is the point of the product: a platform that judges its own transactions is conflicted — the judge profits from the deals it rules on. When you name Recourse in your terms, judgment leaves your building entirely.

TierWho decidesWhenSLA
Tier 1 — Automated verdictThe Recourse judgment engine, ruling under published doctrineClean evidence bundles — the bulk of any queueMinutes
Tier 2 — Enhanced reviewA deeper engine pass, confirmed or overridden by a Recourse reviewer on our internal benchMessy or contradictory evidence, engine confidence below threshold, amounts above the automatic ceilingSame business day
Tier 3 — Human panelIndependent adjudicators contracted by Recourse — trained on the doctrine, conflict-screened per case, excluded from any dispute where they have a relationship with either party or the platformHigh-value disputes, fraud allegations, novel doctrinal questions3 business days

Until a Tier 2/3 review concludes, the escrow instruction ships flagged escalated: true and your escrow partner holds funds. The reviewer's ruling supersedes it with a final signed instruction. Platforms pay for the tier used; platforms never influence the outcome — our fee is never a percentage of the disputed value, so the venue has no stake in who wins.

Published rate card — never a share of the dispute

Pricing

Free trial

$0

Your first 25 rulings free, any tier. No card required. Plus the playground — no account at all.

Start free

Pay as you go

$4.00 / automated verdict

No minimum, no commitment. $20.00 enhanced review · $150.00 human panel. Metered monthly, pay by card (Stripe) or USDC.

Get a key

Volume & enterprise

$1–2 / verdict committed

Annual volume commitments with reserved capacity, liability-backed rulings (insurance-capped warranty), DSA/ODS readiness, shadow-pilot onboarding, named-in-terms support.

Talk to us

The platform pays, never the disputants. Never a percentage of the disputed value — a court's fee cannot depend on the judgment. Anonymised-rulings data-rights discount available on committed plans.

Wear the venue

The badge your users can trust

Customers who name Recourse in their terms display the badge on checkouts, listings, and proposals. It tells both sides of every transaction the same thing: if this goes wrong, an independent venue decides — not the platform, not the counterparty.

Licensed to accounts in good standing where the venue is actually named — so the badge never lies.

Badge assets & terms of use

This transaction has Recourse

Recourse badge, dark variant