
x402 Atlas
io.github.ausrine-labs由 GitHub 帳號 ausrine-labs 發布v0.2.0更新於 Oct 27, 2026
The x402 agent market on Base: sellers, prices, on-chain payments, operators, buyers. Dated.
發布方自己的服務:Red Atlas Api
概覽
唯讀的 MCP 伺服器,介接 x402 Atlas 公開紀錄,提供 x402 代理市場的賣家、價格與 Base、Solana 鏈上 USDC 支付資料。
- 可以做什麼
- 讀取最新鏈上交易日:x402 支付筆數、USDC 金額、買家錢包、獲付賣家、營運方與最忙碌賣家
- 依關鍵字或意圖搜尋賣家,並依真實 x402 支付排序
- 檢視單一賣家卡片:販售內容、與競品價格比較、排名、歷史及鏈上支付狀況
- 查詢某個營運方旗下的主機及其合計收入
- 找出向三個以上賣家付款的買家錢包
- 並排比較二到五個主機
- 適用情境
- 適合讓助理回答 x402 代理經濟中誰在付錢給誰、尋找提供某項服務的賣家,或核實賣家真實的鏈上支付紀錄,而非只看註冊表上的條目。
- 執行需求
- 以 stdio 在本機執行。可透過 uvx 從專案 Git 儲存庫安裝,或在程式碼檢出目錄中以 python3 執行腳本。不需 API 金鑰或帳號,會讀取網站發布的資料檔,每個行程抓取一次。可選設定 ATLAS_STORE、ATLAS_CACHE、ATLAS_DATA 與 ATLAS_SITE。僅限桌面用戶端。
安裝
在 SourceWeft 中
- 開啟 儀表板中的 x402 Atlas,將其新增到工作區。
- 為需要使用其工具的對話啟用該服務。
Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。
其他 MCP 客戶端
參照 儲存庫 中的啟動說明。
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).
來源:README.md,提交 23059d9
工具
0版本歷史
1- v0.2.0最新Sep 27, 2026
評分
已滿足適用檢查項的 50%
該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。
- 近 30 天內可連通25 分
請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。
- 已宣告認證方式10 分
請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。
- 已列出工具15 分
請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。
- 描述必需15 分
- 圖示10 分
- 文件15 分
- 授權條款10 分
其他 Atlas 整合
Red Atlas Api
red.atlas官方發布者
遠端 MCP 伺服器,讓助理存取波多黎各與哥倫比亞的房地產資料:物件、成交、地號、許可、分析與 AVM 報告。

MITRE ATLAS MCP Server
由 GitHub 帳號 imouiche 發布
依 MITRE ATLAS 對 AI 與代理式系統進行威脅建模,把系統架構的攻擊面對應到適用技術、緩解措施與真實事件。

RxAtlas
由 GitHub 帳號 vanja-ivancevic 發布
遠端 MCP 伺服器,可依 FDA 產品-NDC 粒度查詢美國藥品,並提供來源溯源與跨來源識別碼。

Barzel FinOps Atlas
由 GitHub 帳號 Realbizdigital 發布
用於 AI 代理成本控管的遠端 MCP 伺服器:依成果計算真實成本、預算、支出上限、異常偵測與稽核證據。

AI Obligations Atlas
由 GitHub 帳號 Triodian 發布
可檢索澳洲、新加坡與國際標準的 AI 治理義務資料庫,附來源層級、日期與溯源資訊。