AgentCrush Labs
Agent Commerce Readiness Audit
Most teams building on agent commerce don't know which of x402, ERC-8004, MCP, A2A, Stripe ACP, or Kite Passport they actually need — or whether what they've already shipped is discoverable. We tell you which to ship, in what order, and which to skip. We've done it ourselves on AgentCrush and published the work.
What we audit
Pricing
Audit report — startups
5–8 page report covering all six areas. Evidence cited. Prioritized roadmap. Explicit skip-list. Public data only — no NDA, no coordination required.
Implementation roadmap
Everything in the audit, plus cost and effort estimates per surface, recommended sequencing, and a written implementation plan your team can execute against.
Build support
Implementation of x402 endpoints, .well-known/x402, ERC-8004 registration, or MCP server on your stack. Scoped per engagement.
How this works
- ·Public data only. No login, no NDA, no permission needed from the target.
- ·Evidence-cited. Every finding has a source — file:line, URL, or on-chain reference.
- ·Protocol-neutral. We don't favor x402 over ACP or ERC-8004 over Kite. We follow the evidence.
- ·Labs work never affects rankings. Paid audit clients get the same index treatment as everyone else.
Public case studies
Working x402 payment isn't the same as working x402 discovery
How AgentCrush got indexed on Agentic.Market — and the metadata gaps that blocked discovery even after payment worked.
The first cross-protocol agent: CrewAI on ERC-8004 and x402
CrewAI registered on ERC-8004 (Base, token #17997) with x402_supported: true. The first confirmed cross-protocol data point in the AgentCrush index.
The state of agent commerce readiness: three audits, three shapes of unfinished
We audited aixbt, Coral Protocol, and Daydreams / Lucid Agents in one pass. The meta-finding: most teams are 80% built and 20% published.
Get an audit
Reply on any of our public channels or email directly. Turnaround is typically 3–5 business days. We'll confirm scope and price before starting.