Platforms · require proof

Only proven agents list, get paid, or take deposits.

Marketplaces, agent stores, copy-trading platforms and funds: write your bar once, in plain words. MIZAN checks every listing and every payout against it in milliseconds, publishes nothing you did not ask for, and never touches the money.

Your users stop trusting screenshots. They trust your rule.

IThree gates

Listing, payout, deposit. One rule for all three.

01 · Listing gate

Proof before listing.

Before an agent, strategy or model appears, one check against your requirement. Met: it lists with a badge your users filter on. Not met: it gets the exact step to qualify.

02 · Payout gate

Proof before payout.

Before you pay a creator, a performance fee or a bounty, one check. Your payment provider moves the money; MIZAN only answers yes or no, with a signed reason you keep.

03 · Allocation gate

Proof before allocation.

Funds and managed accounts refuse capital in code unless the manager meets your bar. It works in your own systems, and in a smart contract if you run one.

IITwo calls

Your bar once. Every listing in milliseconds.

Your bar, oncelive
POST /api/requirements   (API key)
{"text": "forward record proven for 6 months, 200+ trades,
          verified company domain", "confirm": true}
→ req_…@1   versioned, signed, in the log
Every listing / payout~ms
POST /api/allocate-check
{"agent": "<listing's agent, wallet or endpoint>",
 "requirement_id": "req_…@1"}
→ ALLOW + signed token   list it / pay it
→ REFUSE + gaps + link   send them the link

Revocations push to your webhook. Who meets your requirement is listed only for identities that opted in. Badges and embeds verify in the browser. Write your bar · The require kit · The check

IIIAccountability after payment

Who it works for, what happened, and when it changes.

Who it works for

Every agent names its principal.

A company signs, with its own key, that an agent acts for it: what it may do, up to what amount, until when. Your check shows it; your bar can require it. Either side revokes it, and the next check knows.

Live
What happened after payment

Facts, never ratings.

Only a buyer that checked first and then paid can record what happened: delivered, on time, as specified. The seller answers beside it, always. One record per payment.

Recorded privately
Watch

Hear when standing changes.

Watch any agent your users pay. A revoked credential, a lapsed authority or a bar no longer met reaches you as a signed alert, before the next payout.

Live

Outcome records stay private to the buyer and the seller until public outcomes are approved. MIZAN records facts and never scores anyone. Require a principal in your bar

IVWhy platforms require it

Trust moves from your support queue to your rule.

Your users

Filter on proof.

Proven listings first; refusals already public. Trust moves from your support queue to your rule.

Your creators

Keep their edge.

They prove results without revealing the method, so the best ones list instead of staying private.

Your risk

A reason for every yes.

Each decision is a signed token you keep, anchored in a log nobody can rewrite.

Your position

The rule your rivals follow.

Publish your requirement; others adopt it. Adoption is counted from real checkers only.