← Home · Data hub · Bazaar market map

Original dataset · dated snapshot

Paid but Unrated: x402 demand × ERC-8004 reputation join

Measured 2026-09-01 UTC · bazaar snapshot fetched 2026-09-01T11:23:10Z · refreshes only when a future task re-runs the join, not on the daily site build.

Endpoints that earn money on Base and endpoints that carry an on-chain reputation footprint are almost entirely disjoint. This page publishes the exact join — both the endpoint-level headline and the publisher-level cut that keeps it honest.

🚨 The claim trap — read both figures together

Endpoint level. Of 14,338 Base x402 endpoints that took ≥1 paid call in the last 30 days, 1,291 (9.0%) resolve to a registered ERC-8004 agent owner by exact lowercased pay_to → owner match, 9 (0.06%) carry ANY on-chain reputation feedback, and 0 (0.00%) are commerce-backed (feedback backed by a real ERC-8183 job outcome or Virtuals ACP hook contract, not a bare thumbs-up).

Publisher level, same breath. Those 1,291 endpoints collapse to only 26 distinct pay_to addresses. On the full base-resolvable set with no earning filter — 1,303 endpoints — the top single publisher alone accounts for 875 of 1,303 (67.2%). Of those 26 matched publishers, 4 have any reputation summary row on Base (one feedback event each, one unique client apiece), and 0 of the 26 are commerce-backed.

Why 1,291 of 14,338, and why not 1,303

Two denominators sit next to each other in this join — do not confuse them. 1,303 is the full base-resolvable count: every Base x402 endpoint whose lowercased pay_to resolves to an ERC-8004 owner, regardless of whether the endpoint has ever seen a paid call. 1,291 restricts that set to endpoints with quality.l30DaysUniquePayers ≥ 1 in the same snapshot — the earning filter. The headline 9.0% is 1,291 ÷ 14,338: the earning-filtered numerator over the earning denominator.

Why the 0, not a measurement failure

The commerce-backed count is 0 because every commerce-backed ERC-8004 agent we index — all 44 of them — is a Virtuals ACP registrant that publishes commerce through the ACP protocol, not as an HTTP x402 endpoint in the Coinbase CDP bazaar. The two rails do not overlap at the endpoint layer today. Treat the zero as "no overlap between x402 HTTP demand and the commerce-backed cohort in this snapshot", not as "we couldn't find any real work."

Methodology

Cite this dataset

Citation. On-Chain Agent Intel. "x402 Paid-But-Unrated — Base earning endpoints × ERC-8004 reputation join." Snapshot 2026-09-01 (2026-09-01T11:23:10Z). https://onchainagentintel.io/x402-paid-but-unrated

BibTeX. Copy-paste for LaTeX / biblatex / Zotero: 

@misc{ocai_x402_paid_but_unrated,
  author       = {{On-Chain Agent Intel}},
  title        = {x402 Paid-But-Unrated — Base earning endpoints × ERC-8004 reputation join},
  year         = {2026},
  month        = {09},
  howpublished = {\url{https://onchainagentintel.io/x402-paid-but-unrated}},
  note         = {Snapshot: 2026-09-01. License: CC BY 4.0.},
}

License. Published under CC BY 4.0 — free to reuse, including in commercial work, provided you attribute “On-Chain Agent Intel” and link back to https://onchainagentintel.io/x402-paid-but-unrated.

Machine-readable exports. JSON · CSV — the same figures rendered above; both artifacts carry the publisher-level cut and the 1,291-vs-1,303 note in their body so a machine reader cannot quote the headline naked.

Also useful: x402 Bazaar market map · How do you know which agent is safe to pay? · All datasets · API docs