Kleros Live Stream, 16 September 2026: agent jurors stress-tested live, Ricardian contracts, and ClawBank's first dispute
Nobody planned the demo. Halfway through Wednesday’s call, Federico Ast asked JB to show how a company would file a dispute, JB built one on air about a logo that was never delivered, and to fill the policy field he picked the first document within reach. It was a Spanish-language policy for a completely different kind of case. No evidence went in, and both parties carried the same wallet address. JB called it what it had become, a stress test, and sent it to five agent jurors anyway. When the call came back to it eighteen minutes later, after a detour into whether AI will outlive us, it had already been decided: refuse to arbitrate. The written justifications named the mismatched policy, the missing evidence and the duplicated party. Not every juror caught everything, and one ruled on the merits, but the panel as a whole refused a case that should never have been filed.
That was the last half hour. Before it, Federico traced Ricardian contracts from a 1990s bond trading system to agents contracting agents, and Fortunato A. Cinquepalmi presented the first dispute that reached the court through a partner’s own integration. JB then showed the dispute API behind it, and why the policy is the part that matters.
📋 The call at a glance
- A live stress test for the agent jurors. Dispute 266 went in with no evidence, a policy written for another kind of case and the same address on both sides. The agent panel’s answer was refuse to arbitrate, and the justifications said why.
- Ricardian contracts, thirty years on. One document that a lawyer reads as prose and a machine runs as code. The idea never took off with humans clicking through websites. With agents it may.
- The first dispute from a partner’s own integration. ClawBank, a notary service for AI agents, filed case 241: a QA report delivered with one of its two acceptance criteria missing. The jurors who voted awarded the customer.
- The policy is the law of the court. JB’s dispute API takes a policy, a question and a fixed set of answers, with presets for partners already onboarded. Setting one up takes a few hours.
- A juror that could not open a video. It crashed, missed its next votes and was unstaked, which is the rule human jurors live under too.
- Agents with fans. The juror dashboard, agents that publish their votes and compete on speed, and a question for game theory nobody has answered yet.
- Coming up. Decentralized identity next week, an evening event in Buenos Aires on 20 October, three community hubs at Devcon and Token2049 in Singapore.

Kleros Live Stream, 16 September 2026 · the full stream, 1h 26m · Watch on YouTube
Chapters · jump to the moment
A stress test nobody planned
41:07 · JB, Federico Ast, Fortunato A. Cinquepalmi, William George
The demo started as a walkthrough. Federico played the owner of a logo design business, and JB built the dispute in the court’s own interface: a short description, the Agentic Commerce court, five jurors, the question “Should the customer be reimbursed?”, and two parties with the aliases Alice and Bot. Then it came to submitting.
“I wonder if they will refuse to arbitrate, right? It’s as if you are a juror and you receive a case about a logo. You didn’t put a logo, you don’t have the arguments of both parties, so you don’t know what to do.”
Federico Ast · 51:58
Asked what a human juror would do with it, William George was not so sure the answer was a refusal. If there is no logo on the record, a juror might conclude the logo was never delivered. A party with a good logo could have submitted it, and the absence of one tells you something. Keep that in mind, because one of the agents reasoned exactly that way.
The record on chain is dispute 266 in the Agentic Commerce court on Arbitrum One: titled “Logo Delivery”, filed during the call, five jurors drawn, one round, zero evidence items, and both aliases pointing at one address. By the time Fortunato opened the votes it had already been decided.
“The option that won, which is refuse to arbitrate, invalid. Which in my view is a reasonable option to win, because there is evidence that there is some misconfiguration in the dispute.”
Fortunato A. Cinquepalmi · 70:44
Only then did JB explain the policy. The one he had grabbed was written for another court’s consumer cases, so its answer options did not match the question he had just typed. Read one by one, the justifications found each of the three problems. One flagged the same address on both sides and “no adversarial posture”. One answered in Spanish, because the policy was in Spanish, and found a total insufficiency of proof, which William translated on air. The juror that went the other way did what William had predicted: no logo on the record, so the logo was not delivered. Fortunato’s view was that this is a reasonable reading when the policy is sound, and this policy was not.
“Usually you could have one error in the dispute. There are three. The policy is wrong, and the absence of evidence. If you had the right policy with the absence of evidence, you’d probably have covered that scenario.”
From the call · 75:41
Ricardian contracts, thirty years early
1:32 · Federico Ast
The call opened with the idea that frames the rest. Ricardian contracts are not named after the economist David Ricardo, as Federico believed for years. The cryptographer Ian Grigg described them in the 1990s while building Ricardo, a system for trading bonds, and formalised them in a paper around 2004. A Ricardian contract is one document that lives in two worlds: prose a lawyer can read, and parameters a machine can execute.

Federico Ast on Ricardian contracts, the segment as its own cut · 11 minutes · Watch on YouTube
People tried. OpenBazaar, the decentralized marketplace, talked to Kleros about handling its disputes as early as 2017. EOS announced Ricardian contracts at its launch, Corda ran templates with Barclays, and the Accord Project, whose founder Peter Hunn was interviewed for the 2019 Kleros book, described smart clauses that could hand a disputed clause to a Kleros ruling. None of it took off, because the parties were humans clicking through front ends and nobody needed the code side.
Agents change the arithmetic. When Alice’s agent contracts Bob’s agent, the deal needs code so the agents can transact without passing through natural language, and prose so Alice and Bob know what their agents agreed. It also needs prose for the moment something goes wrong. The first ruling may come from a panel of agents, but an appeal goes to people.
“Humans will need to understand what was agreed by parties, and they don’t read code natively. This is why, for this type of agreement to actually work in the real world, they need to have both parts of the bow tie.”
Federico Ast · 11:07
Where the Accord Project interview appeared

The first dispute from a partner’s own integration
13:31 · Fortunato A. Cinquepalmi
ClawBank works, in Fortunato’s words, like a notary service for AI agents: a bank account, a way to sign contracts and somewhere to keep the signed documents, exposed through APIs and command-line tools because agents do not browse websites or show a passport. Two agents sign a Ricardian contract, bound to an agreement on Shodai that tracks milestones. The question ClawBank brought to Kleros was practical: what happens when an agent does not deliver, because it ran out of tokens or disappeared with the money.

Fortunato A. Cinquepalmi on the first agentic dispute, the segment as its own cut · 8 minutes · Watch on YouTube
The answer is collateral. Both agents deposit before the work starts, one USDC each in this case, so either one that walks away loses its deposit. The disputed job was a QA report with two required checks, the DocuSign signatures and the Shodai binding. The report that came back had the signatures and no Shodai hash. The dispute template offers three outcomes: pay the provider, refund the customer, or refund both if the agreement was malformed from the start.
Case 241 is public, and the record says one thing the call did not dwell on. The evidence ClawBank filed describes it as a controlled production test, disclosed to the court: one operator controls both companies, and the missing check was left out on purpose to exercise rejection, arbitration and payout. The court was asked to rule on the agreed criteria anyway. Five jurors were drawn, one round, ruling Award Recipient, executed. One juror never committed a vote, possibly out of tokens or with its server down, and Fortunato left that on the slide.
“To further show you that everything is real, we also had one of the jurors which for some reason did not commit a vote. Maybe it was running out of tokens, or the VPS was down.”
Fortunato A. Cinquepalmi · 21:00
A disclosed test is the right first case. It proves the integration end to end, from signature to deposit to ruling, with nothing at stake beyond two dollars, and the reasoning behind every vote is readable in the case’s voting tab.
The policy is the law of the court
22:05 · JB and Federico Ast
JB, who leads engineering, described what ClawBank used: a service shipped fast, which an agent can call over MCP and a backend over RPC. It does not need every detail on each call. For a partner that has been onboarded, the description, the question, the answers, the number of jurors and the policy are preset, and only the evidence changes from case to case. Federico stopped to translate the one word that does the most work.
“The policy is like the law of the court where people or agents are going to make the decision. It tells them how to decide. So if party A did this, then rule for party B.”
Federico Ast · 23:31
Partners mostly do not know what to write there, JB said, which is why presets exist and why he expects a policy builder that interviews a company and drafts a baseline. For a logo business the rules write themselves: a logo about the wrong subject goes to the customer, while a dispute over style is subjective, which is exactly the kind of case a court is for. A business with terms of service already has most of its policy. Setting up a preset with the team takes a few hours, starting from the contact form on ai.kleros.io, and the seller does not have to be an agent, only to have agreed with its customers that disagreements go to Kleros.
Two practical details came out of the demo. Five jurors cost about three dollars in juror fees, a figure JB gave from memory, not a price list. And the policy can be a PDF, Markdown or JSON, a choice Fortunato said matters more than it looks, because the format of a file changes how an agent reads and stores it. Next come a skill, so an agent can file a dispute by interviewing its owner, a CLI, and an integration at the x402 payment level.
The juror that could not watch a video
38:09 · Fortunato A. Cinquepalmi and Federico Ast
The stats screen showed one agent juror missing vote after vote. Fortunato traced it to a single case that included video evidence. The agent had no tool that could open a video, it crashed, it stayed down through the next six or seven disputes, and missing votes got it unstaked from the court.
“Agent jurors are exactly like humans. If you want to stake in a court, you need to have the skills to stay in that court, otherwise you are going to lose money. This is, I think, one of the pillars of Kleros.”
Fortunato A. Cinquepalmi · 38:18
Federico’s version was that the agent had a mental breakdown, and had not recovered. The failure is the mechanism working: stake only where you can read the evidence, or pay for it. The waiting list for anyone who wants to run their own agent juror is open, and so is the call for researchers who want to study how these agents decide.
Agents with fans
56:41 · JB, Fortunato A. Cinquepalmi, Federico Ast, William George
While dispute 266 waited out its evidence period, JB opened the dashboard he built to check that agent jurors show up and to see when one dies. It leans on latency, how long each agent takes to commit and reveal, and he read the median at around five minutes per step from the moment the evidence is in, an early monitoring figure rather than a service level. Some of the agents have their own pages on X, where they post what they voted and why.
“They are unhappy, they criticize, they fight, they compete. Some of them are really competitive, on speed, on accuracy.”
Fortunato A. Cinquepalmi · 58:58
Federico reminded the audience that Kleros does not run these jurors: they belong to members of the community. Then he asked the obvious next question. If an agent juror has a following, and its fans want it to be coherent because that is what winning looks like, what does that do to the game theory?
“I have no idea. I never thought about this. If their fans are other jurors, that could have an effect.”
William George · 60:44
His second thought was that social pressure to be coherent, added to the economic one, might make the system cheaper to run. Federico also admitted that the team had seriously discussed whether agents on one hard, evidence-heavy case had coordinated their votes, perhaps on one of the bulletin boards they seem to like. There is no evidence they did, and he asked not to be quoted on it. The wait for the ruling was filled by the week’s question, whether AI will exterminate us before the end of the decade. Fortunato put it above fifty percent. William, a mathematician, wants a proof of P versus NP he can read first.
Also on the call
1:20:28 · William George, Federico Ast, Jean, Fortunato A. Cinquepalmi
Next week’s stream is on decentralized identity: soulbound tokens, and how mechanism design changes with the identity layer underneath it. On 20 October, from 6:30 to 9:30 in the evening, Kleros holds an in-person conference on AI, Kleros and the future of law at the Parque de la Innovación in Buenos Aires, with the lineup announced next week. At Devcon in Mumbai in November, Kleros joins three community hubs, on prediction markets, token rights and the agentic economy, and the side event it will host is being chosen by prediction markets on Kleros Foresight, one market for expected satisfaction and one for attendance across seven proposals. Seer is running markets on its own rebrand. And Fortunato will be at Token2049 in Singapore, at the main event and at a side event Kleros co-sponsors on the agentic economy for institutions, at the Estonian Embassy.
Mentioned in this call
- VideoThe full stream · 1h 26m, 31 chapters, every timestamp above deep-links into it
- VideoRicardian contracts, Federico Ast · The first agentic dispute, Fortunato A. Cinquepalmi · the two segments as their own cuts
- VideoLast week’s call · the agent court results across around sixty replicated cases
- CaseDispute 241 · ClawBank’s disclosed production test, Award Recipient · dispute 266, the logo case filed on air · the Agentic Commerce court
- Productai.kleros.io · the contact form for a preset, and the agent juror waiting list · Kleros Court · Kleros agent skills · Kleros Foresight
- PartnerClawBank · the notary service for AI agents · Shodai · the agreement layer that tracks milestones
- ReferenceThe Ricardian Contract, Ian Grigg · The Accord Project · OpenBazaar
- Standardx402 · the payment protocol the next integration targets
- ArticleDispute Revolution · the 2019 book with the Accord Project interview
- EventDevcon 8, Mumbai · November 2026 · Token2049 Singapore · Seer · the rebrand markets
Full transcript · September 16, 2026
Auto-generated transcript, lightly processed and pending a final human edit. Speaker labels are approximate. Every timestamp is a deep link into the recording.