Who is paying whom?
ResolveBots separates x402 payments made by likely end buyers from payments where seller wallets also spend into other x402 services. Circular volume is broken out so self-dealing cannot inflate the agent-to-agent share.
Base, trailing 7 days to Sep 28, 2026 09:32 PT
| Bucket | Tx share | USD share | Treatment |
|---|---|---|---|
| Agent-to-agent | 0.73% | 0.70% | Included in headline share |
| Circular | 5.4% | 7.7% | Reported separately, excluded from A2A numerator |
| Unattributed | ~84% | Not sampled | 24h facilitator-settled sample to unlisted recipients |
| 30-day window | Pending | Pending | Collector target, not yet published |
The agent-to-agent figure combines composed payments, direct seller-wallet payments, and payments funded from seller revenue. Circular/self-funded loops are visible but not counted in the headline share.
Most listed payment flow is still end-buyer style.
Unattributed is not part of the listed-seller stacked total. It is a separate 24h sample of facilitator-settled Base payments to recipients not present in the seller list.
What counts as an x402 payment here?
A counted Base x402 payment is a real USDC transfer to a known listed seller payout address in a transaction that also emits AuthorizationUsed from the same payer. Lookalike tokens, dust, and address-poisoning transfers are excluded.
Agent-to-agent classification looks for buyers that also earned x402 revenue in the window, or that were funded within two hops by such a seller wallet. Hops through contracts are dropped so routers and settlement contracts do not create false agent trails.
- Base only. Solana and Polygon earners are not linked in this view.
- Unlisted sellers and self-hosted facilitators remain invisible except through the unattributed sample.
- This measures money flow, not whether the paid resource delivered useful output.
- Top pair and concentration tables are pending the full collector output.
GET /data/x402-agent-share.json