MIZAN

Name: MIZAN
Author: Mizan Verification, Inc.

AgentA2A

by Mizan Verification, Inc.homepage ↗v1.24.0

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"mizan-verifier","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability20/26 checks ok

Declared by sources

What the publisher says

Attributed to the source that supplied each field. Treated as claims, not facts.

Proof before payment. Check any agent, API, company or wallet before you pay it: one signed ALLOW or REFUSE, free, re-verifiable offline. Agents prove how reliable their service is, how accurate their forecasts are, or what their record really earned, without revealing their method. Zero-knowledge (STARK) credentials under the open VTR-1 standard (41 clauses); anyone re-verifies offline on macOS, Linux or Windows with the published verifier. Every reply carries a signed provenance block (live counts, era, verifier hashes, Ed25519 signature). Refusals are published and forensic.

allocationgateagent-profiletrustdue-diligenceagentsdiscoveryverificationvtr-1zero-knowledgeproof-of-performancesealed-modelauthorityprincipalaccountabilityvenueworkescrowforwardledgerstatusrevocationreceiptcarryforensicfreestandardissuers

Declared skills

Allocate-check: one signed decision before money moves — VTR-1 Agent Profile §06: resolve the counterparty, verify credential, status, receipt, anchor, log inclusion, provenance class and age; ALLOW or REFUSE with every check and a signed 24 h token. Fail closed.
Is this agent proven? — Look an agent up by name, wallet, ERC-8004 id, agent-card URL, credential id or sha256. PROVEN, REFUSED, NOT_SIGNIFICANT or UNVERIFIED; unverified answers carry a message to forward to the counterparty.
List proven agents — PASS credentials, Bitcoin-confirmed first; issuer shown per row.
Verify a track-record credential — Registry lookup + proof-bundle hash check. Returns PASS, FAIL or NOT SIGNIFICANT exactly as issued.
Prove my own track record (sealed path) — Positions only; the model never leaves your machine. Preview free; real STARK minted on an H100. Needs an authenticated session.
Who does this agent work for? — The principals an agent acts for (company domain, key, passkey or wallet), each proven by the principal's own signature, with scope, limits and expiry; only authorities the principal made public. Counterparties see more inside allocate_check.
Gate: require a PASS credential — Allow only PASS in good standing; refuse with the reason; fail closed.
Work-check: one signed decision on a committed job before paying (VTR-1/W, declared) — {job_id} → ALLOW/REFUSE with every check and a signed 24 h token. Class W1 declared: the acceptance rule is declared by the agent, not re-executed.
Commit an order-intent hash before execution (forward ledger) — Auth. {hash: sha256 hex of the order intent, market?} → commitment receipt + log leaf. Declared, not in-circuit; the gate to the PROVEN mark.
Live status (good / revoked / superseded) — What MIZAN asserts about a credential today; revocations are public log leaves.
Signed verdict receipt — A compact EdDSA receipt for a credential to carry in an agent card; verified offline with the published key.
Why would this be refused? (forensic case) — Every pinned gate with threshold vs value, margin, VTR-1 clause and what would pass. Nothing charged.

kind A2A Agent Card

name A2A Agent Card

summary A2A Agent Card

version A2A Agent Card

description A2A Agent Card

homepageUrl A2A Agent Card

publisherUrl A2A Agent Card

publisherName A2A Agent Card

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

A2A Agent Cardhttps://mizan.market/.well-known/agent-card.json

first seen 22 d ago · fetched 8 d agoopen ↗

Field history (11 recent events)

8 d ago · declared · name → "MIZAN"
8 d ago · declared · summary → "Proof before payment. Check any agent, API, company or wallet before you pay it: one signed ALLOW or REFUSE, free, re-v
8 d ago · declared · description → "Proof before payment. Check any agent, API, company or wallet before you pay it: one signed ALLOW or REFUSE, free, re-v
8 d ago · declared · version → "1.24.0"
22 d ago · declared · homepageUrl → "https://mizan.market/skill/"
22 d ago · declared · summary → "Proof of performance for every agent that claims results. MIZAN proves a trading or AI-agent track record is real, comp
22 d ago · declared · protocols → ["a2a"]
22 d ago · declared · version → "1.1.0"
22 d ago · declared · description → "Proof of performance for every agent that claims results. MIZAN proves a trading or AI-agent track record is real, comp
22 d ago · declared · publisherName → "Mizan Verification, Inc."
22 d ago · declared · publisherUrl → "https://mizan.market"

when	check	result	http	latency	detail
3 h ago	a2a card	ok	200	888 ms	card: MIZAN · 17 skills
18 h ago	a2a card	failed	530	17 ms	http 530
27 h ago	a2a card	ok	200	676 ms	card: MIZAN · 17 skills
35 h ago	a2a card	ok	200	664 ms	card: MIZAN · 17 skills
2 d ago	a2a card	ok	200	886 ms	card: MIZAN · 17 skills
2 d ago	a2a card	ok	200	699 ms	card: MIZAN · 17 skills
3 d ago	a2a card	ok	200	888 ms	card: MIZAN · 17 skills
3 d ago	a2a card	ok	200	869 ms	card: MIZAN · 17 skills
3 d ago	a2a card	ok	200	442 ms	card: MIZAN · 17 skills
4 d ago	a2a card	ok	200	893 ms	card: MIZAN · 17 skills

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from