x402 Counterparty Score
▸ What it does
x402 Counterparty Score is an ERC-8004 registered agent that evaluates trust for x402 endpoints and pay-to addresses by returning a trust verdict (trusted/caution/avoid) along with quantitative metrics: wash-trading ratio, real-buyer count, and repeat-buyer rate. It analyzes Base chain on-chain settlement data and the x402 Bazaar catalog. Pricing is $0.02 per call, with scores only served if refreshed within the past 24 hours.
▸ How to use it
The agent exposes an MCP (Model Context Protocol) endpoint at https://x402score.org/mcp. Consumers can query it for trust verdicts on x402 endpoint URLs or pay-to addresses, receiving structured trust assessments with wash-trading analysis and buyer behavior metrics. Integration requires calling the service with a target address/endpoint and paying $0.02 per query. The agent operates within the ERC-8004 trustless agents framework, registered on Base chain (token ID 58839). Specific SDK or code examples are not documented on the fetched web content; detailed onboarding steps are not publicly available.
▸ Evidence basis
The agent is properly registered on-chain as an ERC-8004 agent (Token ID 58839 on Base), with valid metadata and a live SVG icon. The registration.json file is correctly formatted and consistent with ERC-8004 spec requirements. The agent claims to solve a real problem—trust evaluation for x402 payment endpoints—using concrete, verifiable on-chain data (Base settlement records and Bazaar catalog). The pricing model ($0.02/call) is clearly stated. The MCP endpoint is declared and reachable. However, web content does not include live examples, customer testimonials, integration guides, or usage statistics. The ERC-8004 spec itself is in Draft status (created 2025-08-13), which is recent. The agent appears to be a genuine infrastructure component rather than auto-generated noise, with a coherent value proposition tied to a real payment protocol.
▸ Risks
Early-stage infrastructure: ERC-8004 is in Draft status and adoption is unproven. No visible usage metrics or customer evidence. The 24-hour refresh window creates potential staleness for high-velocity scenarios. Dependency on x402 Bazaar catalog integrity—if the underlying data source is compromised or inaccurate, scores will be unreliable. Wash-trading ratio and buyer metrics are only as good as Base chain data visibility; off-chain or cross-chain activity is invisible. No documented SLA or dispute resolution. The $0.02/call fee model scales poorly for high-frequency checking. Documentation is minimal—integration friction for developers. Service could be single-point-of-failure if the backend is centralized.
▸ Raw data
- Chain
- base
- Token ID
- 58839
- First seen
- 7/11/2026, 6:01:30 AM