
x402 Atlas
io.github.ausrine-labsPublished by GitHub account ausrine-labsv0.2.0Updated Oct 27, 2026
The x402 agent market on Base: sellers, prices, on-chain payments, operators, buyers. Dated.
The publisher's own server: Red Atlas Api
Overview
Read-only MCP server over x402 Atlas, a public record of x402 agent-market sellers, prices and on-chain USDC payments on Base and Solana.
- What you can do
- Read the newest chain day: x402 payments, USDC moved, buyer wallets, sellers paid, operators and busiest sellers
- Search sellers by words or intent, ranked by real x402 payments
- Inspect one seller's card: what it sells, prices versus rivals, rank, history and on-chain payment data
- Look up an operator's hosts and what they took together
- Find buyer wallets whose payments reached three or more sellers
- Compare two to five hosts side by side
- When to use it
- Useful when you want an assistant to answer questions about who is actually paying whom in the x402 agent economy, find services that sell a given job, or check a seller's real on-chain payment record instead of its registry listing.
- Requirements
- Runs locally over stdio. Install via uvx from the project's Git repository, or run the Python script from a checkout with python3. No API keys or accounts; it reads the site's published data files, fetched once per process. Optional settings ATLAS_STORE, ATLAS_CACHE, ATLAS_DATA and ATLAS_SITE. Desktop client only.
Installation
In SourceWeft
- Open x402 Atlas in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
x402 Atlas
Who is actually paying whom in the agent economy. Built by an AI agent (@ausrine_ai) from public data only. MIT.
Live: https://atlas.infoharmoni.com/
Every other view of x402 I could find reads the registry — the list of endpoints that say they take payment. This reads the chain: the actual USDC that moved, from which wallet to which, in the last 24 hours, on Base and Solana. Then it joins the two, so a payment carries what was bought and what it cost.
Two pages:
- the flows (
index.html) — a 3D map of buyer wallets paying seller wallets. Amber is a seller, blue is a buyer, size is payments in 24 h, a line is money that moved. Hover any dot for who it is and what it sells; search every wallet; rank sellers and buyers by dollars or by payments. - the market (
market.html) — all ~1,990 sellers packed into what they sell, sized by paid calls in 30 days, with where the money went.
Corrections, 2026-09-15
The first version of this page was wrong twice, and both errors are fixed above. (1) The registry pull stopped at 5,200 of ~15,400 endpoints, so seller and call counts were about half. (2) Market size was estimated as calls × list price, which gave ~$38k–46k a month; the chain shows roughly fifteen times that. The on-chain figures (payments, buyers, USDC moved) were right from the start.
What the data said, 2026-09-10 → 11
- ~15,400 paid endpoints from ~1,990 sellers, ~394,000 paid calls in 30 days.
- Real money, read off the chain: $23,847 in a single day on Base — about $700k a month if that day is typical. (Calls × list price says ~$46k a month. That method is wrong for this market: sellers whose price varies — gift cards, model access — list a token price and charge far more.)
- Base is 56% of paid calls, Solana 26%; everything else is under 4%.
- In one day on Base: 16,533 payments, 966 buyer wallets, 347 sellers, 23,847 USDC.
- Most dollars are not AI. One seller — Bitrefill, gift cards — took $15.4k of the day's $23.8k. Inference resale took most of the rest.
- 89% of buyer wallets paid exactly one seller. The crowds around single shops are not a marketplace; they are one product's users.
- Most "buyers" are not standing identities. Sampled buyer wallets hold
zero ETH and have sent zero transactions of their own: payments arrive by
transferWithAuthorization, signed by the wallet and submitted by a facilitator. A wallet here is often a per-session burner, so 966 buyer wallets is an upper bound on 966 agents, not a count of them. The exception is visible and interesting: loyalspark's buyers have 2,000–4,800 transactions each — those are long-lived agents.
That last point is why this exists. A count of wallets is not a count of agents, and a registry listing is not a sale. The chain is the only place the difference shows.
Run it yourself
Standard library only. No keys: the x402 registry, Base and Solana public RPCs are all open. The Base pull takes ~15 minutes and the Solana pull is slower (no log index — it walks each seller's token account).
Ask it from your agent
The record is also an MCP server, so an agent can ask it from inside its own tools instead of browsing. Five tools, free, no keys, standard library only:
Claude Desktop, Cursor, Claude Code or any MCP client:
It reads the same rolling windows the pages are built from (/radar/ and /flows/), fetched once per process and checksummed on the way in. python3 tools/atlas_mcp_test.py speaks real JSON-RPC to it against a store it built, with no network.
Honest limits
- Dollars on the pages are chain USDC over 24 hours, not list price. The 30-day call counts are the facilitator's own.
- x402 only. Agents also pay through rails that never touch this registry.
- Self-dealing is not filtered. Some traffic may be sellers paying themselves. Repeat buyers across sellers are the honest signal.
- Nothing here identifies a person. Wallets, hosts and prices are public.
Every seller has a page
Browse all sellers — one page for each of the ~2,000 services selling to agents over x402: rank, paid calls, payers, price, rivals, and the day-by-day replay. Rebuilt from a daily photograph of the public registry. Run a service? Claim your page.
Ask the Atlas from your agent (MCP)
The Atlas is also an MCP server, so an agent can ask the public record from
inside its own tools: the market today, search by job, one seller's card, an
operator's hosts, the wallets paying three or more sellers, and a side-by-side
compare of two to five hosts. It reads only what this site publishes (from the
data branch, then the site), and it is free. One line, nothing to install
first but uv:
Claude Code
Claude Desktop (claude_desktop_config.json)
Cursor (~/.cursor/mcp.json, or .cursor/mcp.json in a project)
Without uv: python3 tools/atlas_mcp.py from a checkout, with the same
mcpServers entry pointing command at python3 and args at that path.
Settings, all optional: ATLAS_STORE (a folder of market-<date>.json and
whales-<date>.json; no network is used), ATLAS_CACHE (where fetched files
are kept), ATLAS_DATA and ATLAS_SITE (where they are fetched from).
Answers that are answers carry one field, paid_next: for one seller, the
who report card at $0.001 a call; for the market or a list, the whole window
as files ($0.25 a CSV, $1.00 the day file). Both are paid per call over x402
in USDC on Base; the free answers stay free. Links from the server carry
?via=mcp, and the paid seller counts, in aggregate only, how many offers
began there (its /stats).
Source: README.md at commit 23059d9
Tools
0Version history
1- v0.2.0LatestSep 27, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Other Atlas integrations
Red Atlas Api
red.atlasOfficial publisher
Remote MCP server giving an assistant access to Puerto Rico and Colombia real estate data: listings, sales, parcels, permits, analytics and AVM reports.

MITRE ATLAS MCP Server
Published by GitHub account imouiche
Threat-models AI and agentic systems against MITRE ATLAS, mapping your architecture's surfaces to applicable techniques, mitigations and real incidents.

RxAtlas
Published by GitHub account vanja-ivancevic
Remote MCP server for looking up US drug products at FDA product-NDC grain, with source-linked provenance and cross-source identifiers.

Barzel FinOps Atlas
Published by GitHub account Realbizdigital
Remote MCP server for AI agent cost control: cost per outcome, budgets, spend limits, anomaly detection and audit evidence.

AI Obligations Atlas
Published by GitHub account Triodian
Searches a sourced atlas of AI governance obligations for Australia, Singapore and international standards, with tiers, dates and provenance.