Skip to content

feat(agentkit): add MIZAN action provider — verify zero-knowledge track-record credentials before paying or allocating - #1564

Open
muaviamohammed wants to merge 1 commit into
coinbase:mainfrom
muaviamohammed:feat/mizan-action-provider
Open

muaviamohammed wants to merge 1 commit into
coinbase:mainfrom
muaviamohammed:feat/mizan-action-provider

Conversation

@muaviamohammed

@muaviamohammed muaviamohammed commented Oct 14, 2026 •

Copy link
Copy Markdown

What

Adds MizanActionProvider (mizan), a network-agnostic, read-only provider with three actions:

  • check_agent — is this counterparty proven? Looks an agent up by wallet address, name, ERC-8004 id, agent-card URL or credential id and returns PROVEN, FORWARD_UNSEALED, PASSED_BACKTEST, REFUSED, NOT_SIGNIFICANT or UNVERIFIED. An AgentKit agent already knows the wallet it is about to pay, so this is the natural one-call check before a transfer.
  • verify_credential — looks a MIZAN credential up in the public registry, downloads the proof bundle, checks its sha256 against the registry anchor, and returns the verdict exactly as issued (PASS, FAIL, NOT_SIGNIFICANT) or UNVERIFIED if missing or tampered.
  • list_datasets — the canonical public markets a credential can be minted on.

Why

Agents increasingly pay other agents for signals, copy their strategies, or allocate to listed records on a self-reported tear-sheet. A MIZAN credential is a zero-knowledge (STARK) proof under the open Counted Claim Standard (specification © Mizan Verification, Inc., free to implement; client code MIT) that a track record is real, computed under committed costs, out-of-sample, and not cherry-picked (the trial count is a Merkle leaf count read in-circuit), without revealing the strategy. This provider gives an AgentKit agent a one-call "check before you pay" gate.

Notes

  • No wallet, no API key, HTTPS only. supportsNetwork() returns true.
  • Tests: 9 passing (jest src/action-providers/mizan). Lint and prettier clean. Changeset added (patch). README table updated.
  • Docs for agents: https://mizan.market/skill/ · MCP server: https://studio.mizan.market/mcp · Public wall (pass and fail): https://mizan.market/registry/

Update 2026-11-04: rebased onto current main as one signed commit (all commits now signed). jest src/action-providers/mizan 9/9, eslint and prettier clean.

@cb-heimdall

cb-heimdall commented Oct 14, 2026 •

Copy link
Copy Markdown

🟡 Heimdall Review Status

Requirement Status More Info
Reviews 🟡 0/1
Denominator calculation
Show calculation
1 if user is bot 0
1 if user is external 0
2 if repo is sensitive 0
From .codeflow.yml 1
Additional review requirements
Show calculation
Max 0
0
From CODEOWNERS 0
Global minimum 0
Max 1
1
1 if commit is unverified 0
1 if authored by an app that is not allowlisted and lacks verified human attribution 0
Sum 1

@github-actions github-actions Bot added documentation Improvements or additions to documentation action provider New action provider typescript labels Oct 14, 2026
Read-only, network-agnostic provider with check_agent, verify_credential
and list_datasets. Rebased onto main as one signed commit.
@muaviamohammed
muaviamohammed force-pushed the feat/mizan-action-provider branch from 5e61536 to 8692fb6 Compare November 3, 2026 21:43
@muaviamohammed

Copy link
Copy Markdown
Author

Update since opening: the project now lives at github.com/muaviamohammed/mizan, and licensing is clarified: client code is MIT, and the specification is © Mizan Verification, Inc. and free to implement. I rebased onto current main as a single signed commit (the earlier commits were unsigned), and the provider's 9 tests, eslint and prettier pass locally; the required checks are green. Happy to adjust anything you'd like.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

action provider New action provider documentation Improvements or additions to documentation typescript

Development

Successfully merging this pull request may close these issues.

2 participants