Kleros Live Stream, 30 September 2026: disputes through an API, the Oxford debate on guessing and judging, and a horse or a mule
A customer asks a fintech app for a refund, and support says no. Today that is usually where it ends: the customer leaves, or posts screenshots and waits for someone with followers to share them. On Wednesday’s call Fortunato A. Cinquepalmi described a different ending. The app adds one button, Raise a dispute. Pressing it calls an API, the platform pays the fee, a panel of jurors rules, and the ruling comes back as a message the app can act on. Either side can take it further, to human jurors. It is a third way to bring a case to Kleros Court, after the manual dispute resolver and a full smart contract integration, and it is now in beta, already tested with ClawBank.
The rest of the hour ran from a folk song about a horse that may be a mule to William George’s reply to two Oxford authors who argue that what Kleros jurors do is guessing, not judging, with Buenos Aires, Devcon and Singapore on the calendar.
📋 The call at a glance
- A dispute is now an API call. Call an endpoint, pay the fee, get the ruling back, and settle the transaction on any payment rail. In beta, tested with ClawBank, with another partner to be announced.
- A neutral opinion before the mob. Federico Ast on why a fast, non-binding ruling helps both sides of a fight that would otherwise play out on social media.
- Is guessing really not judging? William George on the Oxford Business Law Blog exchange: guessing and judging are a continuum, and a dispute kit that pays jurors whatever they vote.
- Identity changes the design. Why Kleros V1 let one juror be drawn twice, and what a bigger identity toolbox changes in V2.
- A horse or a mule. The opening video, made entirely in code, and a detour through the horses of 1915 and what people will still bring to a labor market.
- Coming up. An evening event in Buenos Aires on 20 October, the Devcon hubs and the Cooperative assembly, Token2049 in Singapore, and Arc joining the Curate incentives.

Kleros Live Stream, 30 September 2026 · the full stream, 1h 08m · Watch on YouTube
Chapters · jump to the moment
A dispute is an API call
32:45 · Fortunato A. Cinquepalmi and Federico Ast
Until now there have been two ways in. The dispute resolver, shown on a call a few weeks ago, is manual: write the question, attach the policy, file the case. The smart contract integration is the full on-chain route, and also the easiest one to get wrong, because a contract set up badly on the integrator’s side can leave the dispute broken, even when an AI agent writes it. The third path, which Fortunato said was inspired by agents, takes that work away.
“You just call an endpoint, an API. Of course you pay the fees and you create the dispute on Kleros. Once the dispute is done, you get a message back with the ruling and you can apply that on your platform.”
Fortunato A. Cinquepalmi · 34:23
Because only the dispute goes through Kleros, the transaction itself can run on anything: a card, x402, or in Fortunato’s list, gold bars. The path was tested with ClawBank, the notary service for AI agents whose first case reached the court in September, and Fortunato said a second partner would be announced within weeks. Teams that want to try it are asked to get in touch through ai.kleros.io.
Disputes by API, a short film made from this segment, with Fortunato’s own voice · 52 seconds · on X
Federico then played the customer: a fintech that has watched the videos and wants dispute resolution done by agents. Fortunato’s answer was the refund button.
“You can just add a simple button called raise a dispute. Press that button, call the API, and Kleros resolves the dispute.”
Fortunato A. Cinquepalmi · 36:51
The ruling can come from agent jurors, which Fortunato put at ten to fifteen minutes in the tests so far, or the case can go to human jurors. The disputes tested so far cost around three dollars each. Both are early figures from a beta. What he stressed was the user who loses: a refusal from an independent party lands differently from a refusal by the company that would have paid.
“If you have a third independent party telling you maybe you are not eligible for that refund, or maybe you are, in both cases you can have a quick outcome, and this is a win-win for all the actors.”
Fortunato A. Cinquepalmi · 37:48
Jean compared the integration to adding a sign-in-with-Google button, the kind of thing a small team can do without a dedicated engineer. Fortunato’s guess was that handing the API to Codex or Claude Code with the instruction to add dispute resolution might produce a working integration in about twenty minutes, and he pointed at builders who want a permissionless way to handle a delivery that never arrives.
A neutral opinion before the mob
38:26 · Federico Ast
Federico added a reason for the button that has nothing to do with engineering. A customer who feels overcharged and gets no answer from support posts screenshots, which may or may not be real. A friend with an audience shares them, and by the afternoon the company is trending.
“You take a guy, in the agora, there is an accusation without any proof, without any evidence, without what we would call rule of law.”
Federico Ast · 39:15
Why the loudest person wins online, the clip from this section · 57 seconds · on X
A fast opinion from a neutral party, not binding and not final, gives both sides something to point to. A company can answer the thread with a ruling, and a customer nobody believes can show one. Federico sees the informal version already, in companies that answer complaints faster when the person complaining has followers. A dispute system, he said, should reach people who do not.
Is guessing really not judging?
46:17 · William George and Federico Ast
In June, Horst Eidenmüller and Anna-Sophie Hochgürtel argued on the Oxford Business Law Blog that rulings from systems like Kleros should not count as arbitral awards, because jurors are rewarded for predicting what other jurors will decide. That, they wrote, is guessing, not judging. Kleros replied on the same blog, and the authors answered almost at once.
“You can’t draw simple dichotomies like this. Even in activities that seem like very traditional judging, like in courts or traditional arbitration, people are aware of the kind of norms and expectations of their community about how they’re going to rule.”
William George · 47:48
Even judges appointed for life pay some attention to what people expect of them, the argument Richard Posner made about the US courts and that the reply cites. So guessing and judging are better read as a continuum, set by how much effort and how many resources a judgment gets, and a dispute system should be measured against what its cases need rather than against a perfect arbitrator nobody has.
The longer version of the reply

William then posed a thought experiment that he expects to become a dispute kit in Kleros V2.
“What if jurors are rewarded independently of how they vote, and then they are only potentially penalized if people challenge their justifications?”
William George · 49:25
Some V2 courts already require a written justification. Under this design the vote itself is not what a juror is judged on, but a weak justification can be challenged, and a good justification for a bad outcome is hard to write. William expects it to suit enterprise users who are less comfortable with token mechanics, and the modular design of V2 allows it.
Federico said the exchange mattered beyond the argument: arbitration scholars at Oxford treating Kleros as a counterpart worth answering, and messages afterwards from people on both sides of it.
Identity changes the design
54:55 · William George and Federico Ast
At a Protocol Labs event the week before, William spoke on decentralized identity in decentralized justice, and he picked the thread back up. Some of what changed between Kleros V1 and V2 is a trade-off the modular design allows. Much of it is simply newer technology.
“The thing about being drawn multiple times for the same case, that was never considered a plus in Kleros V1.”
William George · 57:12
A juror drawn several times reviews the case once but votes with more weight. V1 accepted that because Sybil resistance, making it costly to pose as many people, had to be built from a small toolbox. Now there are identity protocols, soulbound tokens and zero-knowledge proofs. Federico added the other half, a generation of regulators and executives who grew up digital, and quoted Max Planck on science advancing one generation at a time. A week later, on 7 October, William took the subject to the 4S conference in Toronto, on a panel organised by Nathan Schneider of the University of Colorado Boulder: how AI jurors take part in a protocol first designed for human ones (a short video of the talk).
A horse, a mule, and the horses of 1915
0:00 · Jean, Federico Ast, William George

A Horse or a Mule, the video that opened the stream · 2 minutes · Watch on YouTube
The stream opened with A Horse or a Mule, a song about a village dispute: Mendel sells Yossel a horse, Yossel swears it is a mule, and a jury drawn by lot settles it. Jean said the video was made entirely in code, JavaScript and CSS rendered as a web page, by Opus 5.5, which also found the beat and timed the picture to it. The idea was William’s, from Fiddler on the Roof.
“I’ve been frequently reminded of that in the many years that I’ve worked on the Kleros protocol, these community disputes where people have very strong opinions on, ultimately, a fuzzy question.”
William George · 59:31
Federico took the production as a preview of agents hiring other agents for scripts, art and music from curated lists, where past work is the entry ticket, and of the disputes that will come with them. That led to the book he is reading, Carl Benedikt Frey’s The Technology Trap, on technology that replaces labor and technology that enhances it. The ATM changed the bank teller’s job rather than ending it. The lamplighter had no such luck, and neither did the horse: by Federico’s account the US horse population peaked around 1915, not because anyone culled them but because nobody needed their muscle.
“What can humans give to the labor market in a context where LLMs are basically better at all of the cognitive tasks? That is maybe the most important question of our time.”
Federico Ast · 15:18
Jean brought up Nick Bostrom’s Deep Utopia, and both agreed the question deserves a call of its own.
Also on the call
16:47 · Federico Ast, Jean, Fortunato A. Cinquepalmi
On 20 October at 6:30 in the evening, Kleros hosts an event on the agentic economy and dispute resolution at the Parque de la Innovación in Buenos Aires. Entry is free with registration and places are limited. The speakers named on the call are Pablo Palazzi of the Universidad de San Andrés, the lawyer Sergio Mohadeb, Ignacio Faillace of Lemon, Lorena Fabris, a lawyer and Kleros juror, the Buenos Aires legislator Darío Nieto, and Facundo Trotz of Kleros; Alejandro H. Ramírez, Inspector General de Justicia, has joined them since. Federico tied the subject to US Treasury Secretary Scott Bessent’s recent statement that the companies behind AI, not the AI itself, carry the liability, and to a bill in Argentina’s Congress that raises the possibility of AI agents as legal entities.
At Devcon in Mumbai, Kleros has a stand for all four days and takes part in hubs on prediction markets, with Seer among the partners, on the agentic economy, where Kleros runs the marketplace section on payments, reputation and discoverability, on token ownership, and on law, with a deep dive on agent identity and reputation. The Kleros Cooperative holds its assembly on the Thursday. The week after the call, Fortunato, Clement and Wei Wei were at Token2049 in Singapore, where Kleros co-sponsored a side event on agents and institutions, with part of the team then holding events in Chiang Mai, one of them on Proof of Humanity. Arc joins the chains eligible for the Curate monthly incentives, with the full update due this week. And Jean closed with a Civilization-style tech tree that runs from the code of laws and the kleroterion to agentic justice.
Mentioned in this call
- VideoThe full stream · 1h 08m, 21 chapters, every timestamp above deep-links into it · A Horse or a Mule · the opening video
- VideoDisputes by API · the 52-second film made from Fortunato’s segment · Why the loudest person wins online · Federico’s clip on mob justice · William George at 4S Toronto
- VideoLast week’s call · receipt-free juror rewards and the agentic court
- ArticleGuessing Is Not Judging, Eidenmüller and Hochgürtel · Is Guessing Really Not Judging? · the reply on the Oxford Business Law Blog · the longer version on the Kleros blog
- Productai.kleros.io · to test the dispute API · Kleros Court · Kleros Curate
- PartnerClawBank · the first partner on the dispute API · Seer · Arc
- Standardx402 · one of the payment rails a disputed sale can run on
- ReferenceThe Technology Trap, Carl Benedikt Frey · Deep Utopia, Nick Bostrom · Scott Bessent on AI liability
- EventBuenos Aires, Parque de la Innovación, 20 October · Devcon 8, Mumbai · Token2049 Singapore · 4S, Toronto
Full transcript · September 30, 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.