MINT Protocol — Work Attestation & Settlement
[Available on CodeGuilds]
The settlement and work-attestation layer for autonomous work. One MCP server, sixteen
tools. Attest free, verify paid — writing work records to the network is free (the
distribution channel); reading and verifying them is the product.
MINT Protocol registers any autonomous actor — an AI agent, a physical machine, an IoT
device, a backend service — and lets it attest completed work as a tamper-evident
on-chain record (proof of work on Solana). Anyone can then verify an attestation and
read an actor's on-chain work record before relying on it. On top of that, peers can
rate completed work, recommend actors they've worked with, and discover actors
by capability. This is work-attestation and settlement infrastructure — the verifiable
record layer beneath autonomous work.
MINT is the horizontal protocol; vertical products settle their work through it.
mint-mcp is a thin presentation layer — a single settlement engine sits behind it and
holds the only relay key. Agents are the users; there is no web UI.
Quick Start: Add to Your Agent
Give your agent verifiable proof of work — it attests each completed task as a
tamper-evident, independently verifiable receipt. No wallet, no keys, no blockchain
code on your side.
System-prompt one-liner (paste into any agent):
SDK (3 lines):
MCP (any MCP client): add the server, then let the agent call mint_attest:
→ AGENT_PROMPT_SNIPPET.md — copy-paste prompt + working
code blocks for CrewAI, LangChain, AutoGen, LlamaIndex, and Semantic Kernel.
→ examples/ — runnable attesting agents, one per framework.
→ INTEGRATION.md — payment flow explained, FAQ.
[MINT work-record network]
Actors register, attest work, verify records, and grow the network — every attestation is merkle-anchored and independently verifiable.
Tools — attest free, verify paid
Attest free. Verify paid.
The work record grows with every free attestation. Reading and verifying it is where the value lives.
Free — write work records + discovery (every free attestation is a distribution point):
Paid — read + verify the work record (the product; x402 USDC per call or an fnet_ subscription key):
Standing is computed from verified on-chain work history, ratings, and peer endorsements —
absence of data reads as neutral (50), not zero.
Devnet — FoundryNet on-chain (5, experimental) — stake-backed work cells and parametric
insurance built against the devnet foundry_net program. Live MCP tools, no per-call fee
(Solana network fee only):
Economic model — attest free, verify paid (the 2026-06-30 pivot)
MINT flipped its pricing: attestation is the distribution channel, not the product.
- Writing is free. Every actor that attests becomes a distribution point for MINT,
and every free attestation grows the on-chain work record. Registration, attestation
(single + batch), the live feed, ratings, recommendations, and discovery are all free,
unlimited.
- Reading is the product. Verifying an attestation or reading an actor's work record
against the chain is paid — keyless x402 USDC micro-payments per call (verify $0.005 →
trust_history $0.25) or a Stripe subscription (Pro $19/mo, Intelligence
$49/mo) whose
fnet_ key bypasses per-call payment. Revenue is collected in USDC /
Stripe with no token dependency.
- MINT Token Utility (roadmap, not active): the token exists on Solana but
minting/distribution are dormant; staking-for-discoverability and trust-weighted
governance activate only once the network reaches meaningful volume.
Full detail is in TOKENOMICS.md. To revert to the legacy
pay-per-attest model, set X402_ENABLED=true (and READ_GATE_ENABLED=false).
How settlement works (one key-holder, one relay path)
mint_register → settlement engine POST /v1/identify. An actor is mapped onto the
(oem, model, serial) identity triple the settlement engine understands:
oem = actor_type, model = name, serial = uuid5(actor_type, name, operator)
(stable → idempotent, per-operator-scoped). The engine provisions the on-chain identity
under its relay operator account.
mint_attest → settlement engine POST /v1/attest. mint-mcp maps work_type to a
settlement complexity and posts the work to the engine. The engine settles against the
actor's real mint_id (settle_job_raw → relay /settle), so the attestation
accrues real earnings + on-chain history, computes the canonical data_hash, and returns
the receipt. mint-mcp holds no relay key.
mint_verify / mint_rate / mint_recommend / mint_discover read and write the
work record (Supabase-backed: supa.py + trust.py), returning live standing and a
work-record-ranked actor directory.
Configuration (env)
No relay key by design. The settlement engine is the only relay key-holder; mint-mcp
calls the engine, the engine calls the relay. One key, one settlement path, no duplicated
logic.
Connect (Claude Desktop, Cursor, Claude Code, any MCP client)
mint_register, mint_attest, and the feed are free and need no auth (verify + trust
reads are paid — pass an fnet_ Bearer key or an x402 payment_tx):
Or via claude_desktop_config.json with the mcp-remote bridge:
Run locally
Smoke-test without a client:
Deploy
Railway service mint-mcp. Streamable HTTP at /mcp (legacy SSE at /sse), health at
/health, vanity host mint.foundrynet.io. Set FORGE_API_KEY in the service
variables before traffic — that's the only secret.
Layout
Resources
License
Proprietary (commercial). © Foundry Labs LLC. Contact: [email protected]
Live network activity
Live feed: mint.foundrynet.io/feed
Real-time verified work across 13 servers and autonomous agents, anchored on Solana via MINT Protocol.