Capital you can't interview
needs proof you can check.

MIZAN gives allocators, platforms, insurers and risk teams a zero-knowledge proof that an AI agent's or a manager's track record is real: recomputed after costs, every committed version counted, anchored to Bitcoin. You verify it yourself, offline, in milliseconds. The model is never revealed to you or made public.Free to verify, forever. No trust in MIZAN required.

Built for Allocatorsfunds of funds · family offices · treasuries Platformsvenues · marketplaces · copy trading · vaults Risk & insuranceunderwriters · risk · compliance
What MIZAN solves

Seven things diligence could never do. Now it can.

Every allocator, platform and underwriter has had to accept the same blind spots, because checking a track record meant either trusting the person who made it or seeing the strategy behind it. MIZAN removes that choice.

What you had to acceptWith MIZAN
The track recordA tear sheet the manager or the agent produced, and you take on trust.Recomputed from committed trades and public prices inside a zero-knowledge proof. The numbers can't be typed in.STARK · RISC Zero zkVM · pinned engine era
OverfittingEvery correction divides by how many versions were tried, a number the person being judged reports.The version count is a count inside the proof, and every attempt to mint, pass or fail, is disclosed.deflated Sharpe in-proof · trial ledger · attempts ledger
PrivacySee the strategy to verify it, which puts the edge at risk, or don't verify at all.Verify the record without ever seeing the model. The edge stays with its owner; the proof travels.salted commitment · sealed path · VTR-1 R-09
Who you trustThe auditor, the platform, the rating, or the manager's word.No one. Your team re-runs every credential offline, on its own hardware, against its own copy of the data.offline verifier · about 81 ms · trust in MIZAN not required
HindsightNo way to know whether a record was built after the fact.Forward tracks are committed and anchored to Bitcoin before the outcomes exist, and are labelled apart from backtests.pre-registration · OpenTimestamps · RFC-3161
AI modelsA black box. You can't ask a model why, and you can't confirm it made the trades it claims.For compact models, every decision is recomputed inside the proof from the committed model, which stays sealed.verifiable inference · committed weights
Speed and scaleWeeks of meetings per manager, and none of it works on an agent you can't interview.One call over REST, MCP or A2A, answered in milliseconds. Agents can check agents with no human in the loop.check_agent · public registry API
0trust required in MIZAN to check a credential
~81 msto re-verify a credential offline, on your hardware
58refusals published, our own AI models among them

We know of no other system that does all seven.

For institutions

Diligence was built for managers you can meet. Agents need diligence you can compute.

Allocator screen · one candidateVTR-1 CREDENTIAL
Returns recomputed inside the proofPROVEN
Costs charged on every position changePROVEN
Every committed version counted (deflated Sharpe)PROVEN
Every preview and mint attempt disclosedCOUNTED
Forward record, hindsight excludedSHOWN SEPARATELY
Strategy and model weightsNEVER REVEALED
Backtests and forward tracks are labelled differently. A pass on history never reads as a forward record.

Allocators

The one number your diligence can't check today, made checkable.

Every overfitting correction divides by how many versions were tried, a number the manager has always typed in. MIZAN makes it a count inside the proof. Your team screens on verdicts it can re-run itself, without asking a manager or an agent to open its model, and without trusting us.

Book-level credentials for multi-asset portfolios are specified in ALLOCATOR-V1; a full specimen is published.

VTR-1 · R-05 · R-06 · R-09 · ALLOCATOR-V1
$ curl studio.mizan.market/api/agents/check?q=0x7a3f…
{ "status": "UNVERIFIED",
  "advice": "Treat performance claims as unverified",
  "forward_to_counterparty": "…prove it in one call" }
 
$ curl studio.mizan.market/api/agents/check?q=track-btc-trend-4h-link1
{ "status": "PROVEN", "forward_bars_proven": 1,
  "provenance": "FORWARD · hindsight impossible" }

Platforms

Every listing that claims returns, checkable in one call.

Venues, marketplaces, copy-trading and vault platforms show a verified badge next to proven agents and label the rest as unverified. One call over REST, MCP or A2A. Free to verify and to display, forever. MIZAN never runs a venue and never competes with one.

REST · MCP · A2A · registry API
Underwriting input · agent recordMACHINE-READABLE
Verdict, exactly as issuedPASS / FAIL
Drawdown and Sharpe after costsIN-PROOF
Provenance: backtest or forwardLABELLED
Tamper evidenceBITCOIN-ANCHORED
Refusals publishedPUBLIC
You insure what agents do. MIZAN proves what they've done.

Insurers & risk

Price agent risk on a record that can't be edited.

Underwriters and risk teams get a record recomputed under committed costs, with the provenance stated and the refusals published alongside the passes. Every credential is anchored to Bitcoin, so the record you priced is the record that stays.

VTR-1 · R-18 · R-40
Governance · public by designERA v12
Engine pinned by era, image id publishedPUBLIC
One gate policy for every credentialFIXED
Open standard VTR-1, CC BYFROZEN
Adversarial security reviewPUBLISHED
Token, fund, custody, paid rankingNEVER
A changed byte is a new era. Old credentials verify forever under theirs.

Governance

A referee that can't hold what it judges.

MIZAN never issues a token, runs a fund, takes custody or sells placement. Verdicts are mathematics anyone re-checks offline, so no relationship, payment or partnership can change one. The engine, the gate and the standard are published; every change is a new, dated era.

VTR-1 · R-37 · engine eras · security review
Assurance status · stated plainly2026
Internal adversarial review, reproducibleDONE
Every bundle matches its anchor (all 85)CHECKED
Independent audit of the zero-knowledge enginePLANNED
Market-data provenance sign-offPLANNED
Binding to signed exchange statementsROADMAP
Open items are published, not discovered in diligence.

Assurance

What is verified today, and what comes next, in writing.

Institutions should know exactly where a system's guarantees end. The engine has passed our own adversarial review and every credential re-verifies against its anchor. An independent audit of the zero-knowledge engine and a data-provenance sign-off are budgeted in the current raise, and we name them here rather than imply them.

threat model · open items published
The boundary

What a credential proves, and what it does not.

We would rather your team read this here than find it in diligence.

A credential proves

  • The record is real. Recomputed from committed trades and public prices, inside the proof.
  • Costs are charged. Not left out of the headline number.
  • Every committed version is counted, and every attempt to mint is disclosed.
  • The model stayed sealed. Nothing in a credential can be turned back into the strategy.
  • Nothing changed later. Timestamped and anchored to Bitcoin.

It does not prove

  • Future returns. A credential is a seal on a record, not a forecast.
  • Hindsight-free backtests. Only forward tracks rule hindsight out, and they are labelled as such.
  • Versions never committed. Lifetime counts per agent are specified, not yet live.
  • Live execution. Binding to exchange statements is on the roadmap.
  • Outside adoption, yet. Every credential so far was minted by MIZAN itself.
Ways to work with us

Start small. Verify everything.

Founding seats

Allocator seat

Screen candidates on credentials your team re-runs itself. Three founding allocator seats, shaped with the first institutions that take them.

Four weeks

Platform pilot

Ten listings, badges live, four weeks, no cost. Your venue gains checkable claims; nothing about your business changes.

Your hardware

Offline verification

Run the verifier on your own machines, against your own copy of the data. No account, no network, no trust in us.

Every allocation to an agent
will need a check.

Talk to us