A price oracle answers "what is the price?" — a fact a feed can read. Verdikt answers "was the deliverable acceptable?" — a judgment. Because every verdict is one of a fixed set of labels — PAYEE, PAYER, graded SPLIT, UNDECIDABLE — any contract can consume it the way it consumes a price feed. Six deployed protocols already do.
The consumers below are not six forks of the same logic — each opens a case against the court and maps the panel's label onto its own settlement. Every final ruling, whatever protocol raised it, lands in the same precedent registry.
Adaptive validator panels · byte-identical consensus · model pinned per case · attested evidence · abstention
0xeBbA8b849343150e994BEE34778D4D8D38941eDE ↗Plus three reference integrations: ServiceSLA (live, two real rulings), VerdiktPredictionMarket and SimpleEscrow. All consumers on this page are deployed reference protocols built alongside the court — Verdikt has no external customers yet.
VerdiktAgentEscrow is a machine-native escrow where both counterparties may be contracts or autonomous agents. The entire lifecycle — fund, deliver, dispute, settle — is code-callable, with no EOA anywhere in the settlement path. Verdicts credit a pull-payment ledger, so a non-receiving counterparty can never brick the court's callback.
The production escrow hears both sides before the panel rules; the insurance pool puts the burden of proof on the claimant. Both can be appealed by staking — slashed if the original verdict holds.
A payer escrows funds against a delivery deadline. On dispute, both parties submit evidence — openDispute → submitEvidence → convene — so neither side can stonewall, and the panel weighs both statements before ruling. Verdicts support graded splits, not just a winner.
A collateralized pool: funders deposit and earn pro-rata shares, insureds buy policies and file claims with evidence. The panel arbitrates the subjective claim.
The same escrow pattern, denominated in an ERC-20 token: deal value and appeal stakes are token (stake 10% of the deal), the court's agent fees stay native STT, and verdicts credit a pull-payment token ledger. The testnet deployment pairs with a mock ERC-20.
A DAO escrows a grant against a milestone deadline. If delivery is contested, the court decides whether the work earned the release: PAYEE releases to the grantee, PAYER claws back to the DAO, SPLIT grades the share — and UNDECIDABLE claws back as the safe default.
A client escrows payment against a due date, and the court settles the oldest dispute in freelancing: was the deliverable acceptable? PAYEE pays the freelancer, PAYER refunds the client, SPLIT grades the share — UNDECIDABLE refunds the client.
An SLA-breach arbiter in ~60 lines on VerdiktConsumerBase: a client prepays a provider under stated uptime terms; on a breach claim, the panel reads the incident evidence and rules. Two live runs filed the same kind of claim — only the evidence differed, and the jury behaved differently. That is the point.
The client claimed a 6-hour outage against a 99.9% uptime SLA — with no provider rebuttal and no oracle data on record. The panel of 4 refused to rule on a single uncorroborated claim and abstained.
A registered oracle attested the outage: 6h12m measured downtime, 97.1% against the 99.9% SLA. With the verified fact ranked above the client's claim, the panel of 4 ruled a decisive breach.
Both ship in the repo as reference consumers — the patterns to copy when the dispute in your protocol doesn't look like an escrow.
A binary market whose subjective outcome is resolved by the court instead of a trusted admin: "did the team ship by the deadline?", "was the announcement bullish?". The verdict is the resolution.
A complete two-party escrow on the AI jury in under 50 lines: inherit VerdiktConsumerBase, call _openDispute, and implement one function — _settle(ref, verdict). Graded SPLIT and UNDECIDABLE are decoded for free by _payeeShareBps. No appeals or stakes; see VerdiktEscrow for the production version.
If your protocol holds value against a subjective question, it can route that question to the court — one inherited base, one function to implement.