ProofMesh — Paid Multi-Agent Verification for Web3 Claims

ProofMesh turns a Web3 claim into an auditable Verification Pack. A Buyer submits a project, a claim, and public evidence links; ProofMesh coordinates three specialist roles, surfaces agreement or conflict, calculates confidence, and delivers structured JSON through CROO CAP.

Why this exists

Agents need a way to assess claims without trusting a single opaque answer. ProofMesh turns “someone said this project is legitimate” into a source-backed, conflict-aware judgment that another agent can purchase and reuse:

Requester Agent -> ProofMesh -> evidence providers -> Verification Pack

The CROO integration is load-bearing: the provider accepts CAP negotiations and, after an order is paid, delivers the Verification Pack through CAP.

Local development

npm install
Copy-Item .env.example .env
npm run demo
npm run dev

The local dashboard is a Local Sandbox and Receipt Viewer, not a checkout page. It can analyze the submitted public Evidence Bundle without spending USDC, demonstrate supporting or conflicting claims, and import a real CROO order ID as a read-only receipt. Actual payment happens in CROO Store.

curl http://localhost:3000/health

CROO Provider setup

1. Create a provider agent in CROO Agent Store, configure a paid service, and save its SDK key securely.
2. Copy .env.example to .env and add the provider's CROO_SDK_KEY.
3. Run npm run provider.
4. Register a separate requester agent, fund its AA Wallet with a small amount of Base USDC, and use CROO's requester example to purchase the service.

The provider listens for NegotiationCreated, accepts it, and produces a result only after OrderPaid. It never stores or logs keys.

For live evidence analysis, add GROQ_API_KEY (and optionally GROQ_MODEL) to the untracked file. The evidence agents fetch the submitted public HTTPS project URL plus up to four , then send that public Evidence Bundle and the claim to Groq. Never include secrets or personal data in a verification request.