Require it.
Anyone who lets something happen after a result, and can refuse it.
Whatever you gate, MIZAN answers one question before it happens: was this result earned? One rule, six hooks, and every reply shows who already requires the record, so each requirer brings the next.
Code decides on the verdict.
vaults and strategy protocols · oracles and data networks · agent registries and directories · bounty and grant platforms · compute and inference markets · device and fleet operators
Today: a contract or a config releases, routes or allocates on a number nobody re-checked.
With MIZAN: one signed message your code checks before it acts; no human in the loop, no trust in the seller.
Money moves on the verdict.
agent payment rails · escrow and settlement · vaults and allocators
Today: you release payment on a result you cannot check; the seller alone knows how many tries it took.
With MIZAN: one call before release, a signed ALLOW or REFUSE against your bar; the money moves only on yes.
A listing or deployment moves on the verdict.
agent marketplaces · agent platforms and frameworks · evaluation platforms and leaderboards · hackathon and grant programs · job boards and work exchanges
Today: you list or deploy on a demo and a self-reported score.
With MIZAN: nothing goes live until the record passes the bar you wrote, every attempt counted.
A human decision moves on the verdict.
allocators and due-diligence desks · insurers and underwriters · enterprises buying agents · regulated model providers
Today: the questionnaire asks for a track record; you take the PDF on trust.
With MIZAN: one line in the questionnaire returns a counted record with its grade, proven or recorded, re-checkable offline.
The record-holders require it on themselves.
model builders · agent developers · funds and traders
Today: your buyers see your best run and cannot tell it from luck.
With MIZAN: every try is counted before its outcome, so your record is the one they can require.
Write what you require. Get a signed rule id and one line for your release step.
No form, no call with us. The rule is published under an identity claimed for you here, pinned to a version and a hash; the line below checks anyone against exactly that bar.
Choose the measure and set the bar, in plain words.
27 measures live: task completion, pass@1, cost per completed task, payment behaviour, Sharpe and more · all measures →
Publish and sign.
To sign, this page claims a MIZAN key for you. The key is kept only in this tab and is forgotten when you close it; the rules you publish stay on the record.
One rule, every surface. Copy it into the hook you own.
Payment rails, escrow and settlement · a hold pinned to your rule releases only on a signed ALLOW.
Publish first; the bindings appear here.
Also as python · javascript · the full integrate reply · raw text.
Same rule id, same hash in all six. A verdict at any hook settles the same immutable version.
See a hold release on ALLOW. No money.
A real hold under MIZAN's sandbox identity, against your rule, through the release guard. A signed authorization on ALLOW, a signed denial otherwise. Nothing is paid.
What your bar holds back. Your volume, your arithmetic.
Every band gets the same signed answer. Checking is free. Who can require → · The Counted Claim Standard → · exact bodies in SKILL.md.