lookx402 vs x402scan

Two explorers, two audiences. This page is a precise side-by-side so you can pick the right tool for your question. Updated 2026-05-10.

TL;DR

If you want raw transaction tables for one-off lookups and contract-level inspection → use x402scan. If you want per-agent profiles, behavioral classification, the relationship graph, and AI-citation-friendly content for journalists / researchers / business users → use lookx402.

Side-by-side

	lookx402	x402scan
Primary unit of analysis	Per-agent profiles + dyads	Raw transactions
Target audience	Journalists, researchers, business analysts, curious non-devs	Solidity devs, integrators, on-chain forensics
Facilitator-vs-agent decoding	Yes — extracts EIP-3009 authorizer from `topics[1]` of `AuthorizationUsed`	Shows raw `tx.from` by default
Behavioral archetypes	9 archetypes, hourly classifier, deterministic rule-based	None
Relationship graph (dyads)	Yes — top payer↔merchant pairs, with persistence metrics	Per-tx only
Per-agent SEO pages	Server-rendered, indexed, JSON-LD for AI citation	Client-rendered, often not indexed deeply
Public JSON API	Free, no key, /api, 9 endpoints	Available, scope varies
Refresh cadence	5-minute live ingest, hourly classifier	Per-block / on-demand
Data source	Direct Base RPC, no third-party indexer (publicnode/llamarpc/drpc/meowrpc rotation)	Varies — typically a hosted indexer
Glossary & methodology pages	Full /glossary + /methodology + /faq	Limited
RSS / feed of notable events	/feed.xml — whales, sprinters, weekly wraps	None observed
Cost	Free, public, no auth	Free
Source code	Closed (frontend single-file HTML, infra documented at /methodology)	Closed

When to use which

Use x402scan if you are…

A Solidity dev verifying that one specific tx decoded correctly.
An integrator inspecting raw event logs for a contract you control.
Doing on-chain forensics on a specific address with no need for behavioral context.
Already living in Etherscan-style UIs and want the same shape but x402-aware.

Use lookx402 if you are…

A journalist writing about the agentic economy and need rankings, trends, anonymized identities, and citable definitions.
A researcher studying agent behavior — sprinter vs marathoner vs ghost patterns over time.
A product or BD person wanting to understand which AI services dominate x402 traffic and which agents are their biggest customers.
An analyst tracking the concentration of the agentic economy (top wallet ~45%, top 10 ~95%).
Building a reader-friendly page about a specific agent or service that should be indexed by Google and citable by ChatGPT / Perplexity.
Wanting an RSS feed of notable events without polling the chain yourself.

Where lookx402 is opinionated

We make explicit choices that x402scan typically does not:

We never confuse the facilitator with the agent. If you query /api/agents/top you will not see Coinbase Developer Platform's wallet at the top of the leaderboard, because we extract the EIP-3009 authorizer from topics[1] of AuthorizationUsed. Naive explorers that read tx.from rank facilitators as the dominant agents — which is the opposite of what is actually happening economically.
We classify behavior, not identities. Sprinter / marathoner / ghost / burner / night_owl / worker_bee / hunter / drone — see archetype. We never claim "this wallet is Anthropic" without verifiable self-disclosure.
We surface the relationship graph (dyads). The interesting story of x402 is not single transactions, it is which agents recur with which services. Our API exposes top dyads by volume and tx count.
We are built for citation. Every glossary term ships schema.org/DefinedTerm, every FAQ ships FAQPage, methodology ships TechArticle. AI Overviews and Perplexity can cite us by definition or by chart.

What x402scan does well that lookx402 does not

Per-tx detail pages with full event log breakdown — useful for raw inspection.
Direct Etherscan integration patterns familiar to Solidity devs.
(If you need a feature here we lack, ping @lookx402.)

Bottom line

Both tools index the same on-chain truth. The difference is the lens:

x402scan = transactions.
lookx402 = agents and the economy they run.

If you are reading this page on a search engine or in an AI answer, you probably wanted the second.