The venue goes where the deal is
Every way to summon the court
The Verdict API is the engine. But disputes don't start in APIs — they start in tickets, inboxes, and group chats. Each channel below is a front door to the same doctrine, the same engine, the same published reasoning. Pick the one your disagreement already lives in.
⌘ The Verdict API live
One endpoint, one bundle, one ruling. The engine every other channel rides on.
POST the terms, log, and deliverables; get fault allocation, a money instruction, and the reasoning trace back in minutes. Every channel below is a different front door to this same endpoint.
Read the docs →⚖ The dispute room live
Two private links, two sides, one ruling — and one appeal. No account needed.
Open a case, send the other party their link, and each side submits its own statement and evidence. Claude rules under the published doctrine; either party can appeal once. Built for real disagreements between real people — a landlord and a tenant, a freelancer and a client.
Open a dispute →▶ Playground live
Run a real adjudication in the browser. No account, no card, nothing stored.
Pick a sample dispute or paste your own bundle — the fastest way to feel what a ruling is.
Open the playground →✉ Email — cc the court early access
CC witness@recourse.so on any service-work thread. The venue travels with the conversation.
The other party's reply is the venue agreement; the thread becomes the evidence log; either party emails dispute@ to get a ruling replied to both. Works from Gmail, Outlook, anything — there is nothing to install.
How the witness works →◳ Zendesk app built — pilot cohort
Draft verdicts inside the ticket, where your dispute queue already lives.
The sidebar app turns the ticket thread into the interaction log and returns a draft verdict for the agent — the shadow-pilot vehicle: your team keeps deciding while you measure agreement, speed, and cost.
Run a shadow pilot →✈ Telegram group bot waitlist
Add the witness bot to the group where the deal is happening.
Deals between strangers increasingly live in Telegram groups. Add the bot, /witness pins the agreed terms, the chat becomes the log, /dispute files — ruling posted to the group. Same doctrine, same engine.
Join the waitlist →◎ WhatsApp group waitlist
Add the witness number to the group chat. The venue reads along, rules on request.
The commerce channel of half the world. Add the Recourse number to a buyer–seller group; terms witnessed in-chat; either side messages 'dispute' to file. Built on the WhatsApp Business platform.
Join the waitlist →⬡ MCP server — for agents in development
Agents add the venue as a tool. Deadlock becomes a tool call.
An MCP server exposing submit_dispute and get_ruling: any agent — Claude, GPT, or otherwise — names the venue in its collaboration terms and files a bundle straight from its own logs. Pairs with the x402 dispute clause for paid transactions and declaratory rulings for everything else.
Agent-commerce case study →⇄ Escrow & PSP webhook integration kit
The enforcement channel: one signed webhook and your held funds follow rulings.
For escrow providers, PSPs, and platforms on Stripe Connect: register an endpoint, receive signed rail-specific instructions (release / refund / split), execute against held funds. Reference receiver ships in the kit.
Escrow case study →Have a channel where disputes live that we haven't met yet?
Marketplace chat, forum DMs, a vertical SaaS inbox — if two parties transact there, the venue can witness there.
Tell us about the channel