MIZAN · Solutions

Require a counted record where money moves.

Write your bar once, in plain words. It compiles to one exact rule, pinned by its hash, and every check against it runs that same rule, wherever it runs. Checking is free.

Agent marketplaceslist and pay agents on what they earned Payment railssettle only on a signed ALLOW Funds and labsallocate and deploy on a counted result
01 · Agent marketplaces

Pay agents on the jobs they finished, not the stars they collected.

The problem

A listing shows an agent’s best work and a rating the agent can shape. The buyer cannot see how many jobs it took on, how many it failed, or who those jobs were for.

MIZAN counts every receipted job, failures included, and answers with one signed yes or no against your bar, before a buyer pays.

The bar you would write

“Pay an agent only if at least 90% of its receipted jobs with independent counterparties succeeded, over at least 20 settled jobs in the last 90 days.”

template agent-reputation-v0 · draft

Where it is enforced

  • Listing an agent is listed only while it meets the bar
  • Release milestones paid only on ALLOW, each authorisation redeemed once
  • Disputes a buyer contests a verdict on the record; corrections append
Require it on your marketplace →
02 · Payment rails

Prove it was earned in the same step as the payment.

The problem

A rail proves that an agent paid. It cannot grade its own merchants and stay neutral, and a lost reply plus a retry can turn one payment into two.

The MIZAN verdict travels with the payment as one signed token. Your facilitator checks it offline against a published key, with no call to MIZAN, and settles only on an unexpired ALLOW bound to this payee and this rule.

The bar you would write

“Settle only when the payee’s counted record meets the payer’s bar and the payment is within the limits its principal signed.”

carried in x402, AP2, ACP or a plain header

Where it is enforced

  • Payment request the bar travels as one field in the payment requirement
  • Release one single-use authorisation per hold
  • Spending limits each payment read against what the principal signed
Require it on your rail →
03 · Funds and labs

Allocate and deploy on the count, not the best try.

The problem

A track record and a benchmark score are each someone’s best try. The number of tries behind them is the one figure that is never on the page.

MIZAN binds the count inside a zero-knowledge proof, corrects for luck by the real number of tries and keeps the method private. AI scores are proven from every attempt, all declared before the first one ran.

The bar you would write

“Allocate only to a strategy proven forward-only for at least 180 days and 100 trades, that kept its own mandate.”

template machine-credit-v0 · draft

Where it is enforced

  • Questionnaire one clause your due-diligence form checks automatically
  • Deploy a model or strategy ships only on ALLOW
  • Code gate a contract or config line checks the verdict before it allocates
Require it in your process →
Releasemoney moves only on ALLOW
Payment requestone field in the requirement
Listinglisted while the bar is met
Deployships only on ALLOW
Questionnaireone clause, checked
Code gatea line a contract checks

One bar. The same answer at every point.