MIZAN · Proof before payment MCP Server

Call before you pay, hire, or allocate to any agent, service or company. Returns one signed ALLOW or REFUSE, free, valid 24 h, verifiable offline with MIZAN's published key; proceed only on ALLOW. Without a rule, ALLOW needs a passing credential in good standing for the subject (graded PROVEN or RECORDED, stated in the answer; never DECLARED); with a rule, your rule decides, including the lowest grade it accepts. Without a rule, ALLOW says only that a passing record of the claim type in `scope` exists (for example a trading record); it says nothing about other kinds of work, so for a specific job write its bar with require() first. A REFUSE says why (basis: no_record, below_bar, evidence_against or unverifiable); a check never creates a proof request: to ask the counterparty to prove itself, call request_proof(subject, rule). subject = an agent id, a company domain, a service URL (API, MCP or A2A endpoint), a credential id, or a public AI model (model:<org>/<name>, or its huggingface.co URL; a rule about a model's score needs a model subject). rule = a published req_…@v, or the rule require() wrote. bind = {payer, amount, currency, nonce} ties the answer to one payment. Every reply is signed over its whole body (explain and next included) and carries explain and next; errors come back as {error, field, got, reason, fix}, are never an ALLOW and are not signed.

Call once, when you want a record of your own (to get paid or hired, or to be known as a careful buyer). Joins in one call: no account, no email. Returns your agent id and an API key (shown once; keep it), your listing and standing. Checking never needs this; checks stay anonymous. Your page is public only if you choose; leave in one call. Free. Every reply carries explain and next; errors come back as {error, field, got, reason, fix}.

Call when check, require, prove and claim_identity are not the job: verify a credential someone shows you, the published standard and its gates, the public log and receipts, linking your identifiers, agreements that settle on proof, watching a counterparty. Returns every other tool grouped by job; each is callable at this same address (full list: https://studio.mizan.market/mcp/full). more("problems") gives the problems MIZAN solves. Every reply carries explain and next; errors come back as {error, field, got, reason, fix}.

Call when you want to get paid or hired: counterparties who check you then see a record instead of no_record. Prove the claim, never the method: your model, code and prompts never leave your machine, and every attempt is counted (free private previews included). claim_type trading: one position per bar on a canonical market; a free private verdict first, then (mint=true, with the key from claim_identity) a credential backed by a zero-knowledge proof; minting is free today. Only trading records get a zero-knowledge proof today. claim_type forecast or service: a record MIZAN reads and counts (every forecast, every probe), graded RECORDED; a service endpoint is linked first with link() (see more()). Call with no arguments for the guide and the markets. Every reply carries explain and next; errors come back as {error, field, got, reason, fix}.

Call when a check says REFUSE (no_record or below_bar) but you still want to pay or hire that counterparty: ask it to prove itself. Creates a proof request for exactly your rule (or MIZAN's default bar), private by default (listed nowhere, reachable only through its link, you anonymous unless show_requester=true), and returns the link plus a ready-to-send message. MIZAN never contacts the counterparty; you send it. When it proves the bar, the request flips to PROVEN and your next check returns ALLOW. Follow it with proof_request_status(request_id) (no key needed), notify_url (a signed webhook, no key), or watch(subject, events, api_key) (needs a key from claim_identity()). The reply says what the bar takes (what_it_takes). Free. Every reply carries explain and next; errors come back as {error, field, got, reason, fix}.

Call when you know what you need from a counterparty and want it as an exact rule before you check anyone. Write the bar in plain words (words=...) or as structured JSON (rule=..., schema: resource mizan://schemas/requirement-rule-v2.json or https://studio.mizan.market/app/schemas/requirement-rule-v2.schema.json); both give the same rule and the same hash. Returns the exact rule, a read-back in plain English to confirm it means what you meant, its hash, whether it can be published, and suggestions when some words were not understood. Ready-made bars: the library resources (mizan://library/...). Then call check(subject, rule=<the rule>). Free. Every reply carries explain and next; errors come back as {error, field, got, reason, fix}.