Easier than a rating. Truer than one.
A rating is someone's opinion, easy to read. A MIZAN proof is a fact anyone can re-run, and now it is easier to read than a rating: one line, no key, no call to us.
Three ways in. Pick the one that matches where you already are.
Sellers attach the proof. Buyers verify it with zero calls to us.
Like stapling in TLS: you get a signed receipt bound to the exact wallet, host or agent id you are paid as, issued only if that identity passes. Attach it to your responses. A buyer verifies the signature locally against our published key. A receipt shown by anyone else is never an ALLOW.
# get it once mizan staple 0xYourPayoutWallet // or keep it fresh on every response app.use(mizanStaple({ identity: "0xYourPayoutWallet" })); # Python: app = MizanStaple(app, identity="0x…")
import { verifyReceipt } from "https://mizan.market/skill/mizan-receipt.mjs";
const r = await verifyReceipt(receipt, { identity: payTo });
r.allow // true only for a PASS bound to payTo
# Python: verify_receipt(receipt, identity=pay_to)Carry it as an X-Mizan-Receipt header, in x402 terms (accepts[i].extra.mizan.receipt), in your agent card, or at /.well-known/mizan.json. The payment guard and the label read it automatically and fall back to the live check. Receipts last 24 hours; the middleware renews them.
Then you already read MIZAN. Same shapes, proof inside.
Every MIZAN verdict is served in ERC-8004's own feedback and validation shapes, signed, off-chain, so any indexer or agent that reads ERC-8004 reads MIZAN unchanged. The value encodes the verdict (PASS 100, NOT SIGNIFICANT 50, FAIL 0) and points at a zero-knowledge credential anyone re-verifies. It is never an opinion score.
GET https://studio.mizan.market/api/erc8004/feedback/<agent, wallet or credential> GET https://studio.mizan.market/api/erc8004/validation/<agent, wallet or credential>
Not sure where it goes? Ask the doctor.
Run it in your project. It detects x402 payments, an HTTP server, LangChain or CrewAI, MCP, or a site that lists agents, and prints the one line to add.
pip install https://mizan.market/skill/mizan_sdk-0.5.3-py3-none-any.whl mizan doctor
Reading a stapled proof needs no network at all.
0.14 ms
per verification, 0 network calls (1,000 runs, Node).
0.21 ms
per verification, 0 network calls (1,000 runs).
62 ms
typical, 74 ms slow, one call (20 runs).
456 bytes
signed, bound to one identity, 24 hours.
Measured by MIZAN on 21 October 2026 from one network; your latency will differ. Verification needs WebCrypto Ed25519 (Node 20+, current browsers) or Python's cryptography package; without it, one call verifies the signature and the binding rule is unchanged. The require kit · The check