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

概览

AI 生成的概览

只读的 MCP 服务器,接入 x402 Atlas 公开记录,提供 x402 代理市场的卖家、价格与 Base、Solana 链上 USDC 支付数据。

可以做什么
  • 读取最新链上交易日:x402 支付笔数、USDC 金额、买家钱包、获付卖家、运营方与最活跃卖家
  • 按关键词或意图搜索卖家,按真实 x402 支付排序
  • 查看单个卖家卡片:售卖内容、与竞品价格对比、排名、历史及链上支付情况
  • 查询某个运营方名下的主机及其合计收入
  • 找出向三个及以上卖家付款的买家钱包
  • 对两到五个主机做并排比较
适用场景
适合让助手回答 x402 代理经济中谁在向谁付款、寻找提供某项服务的卖家,或核实卖家的真实链上支付记录而非其注册表条目。
运行要求
以 stdio 在本地运行。可通过 uvx 从项目 Git 仓库安装,或在代码检出目录中用 python3 运行脚本。无需 API 密钥或账号,读取站点发布的数据文件,每个进程抓取一次。可选设置 ATLAS_STORE、ATLAS_CACHE、ATLAS_DATA 和 ATLAS_SITE。仅限桌面客户端。
安装前请注意
免费回答不收费,但部分结果带有 paid_next 字段,提供按次付费的额外报告,以 Base 上的 USDC 计价(例如卖家报告卡 $0.001、每份 CSV $0.25、当日文件 $1.00),付费会花真实资金。返回的链接带 via=mcp 跟踪参数,卖家会汇总统计由此产生的报价次数。数据仅覆盖 x402,未过滤自买自卖,钱包数量不等于代理数量。

安装

在 SourceWeft 中

  1. 打开 控制台中的 x402 Atlas,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

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

bash
python3 tools/chain_flows.py  --hours 24 --out data/flows.json          # Basepython3 tools/solana_flows.py --hours 24 --out data/flows-sol.json      # Solanapython3 tools/flows_graph.py  --flows data/flows.json --also data/flows-sol.json \                              --out data/graph.jsonpython3 tools/network.py      --graph data/graph.json --out indexpython3 tools/market.py       --in data/x402-sellers.json --out market

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:

toolanswers
market_todaythe newest chain day: x402 payments, USDC, buyer wallets, sellers paid, operators, agents at work, the busiest sellers by real payments
searchwhich sellers do a job — by words or by intent, ranked by x402 payments yesterday, then by self-reported calls
sellerone seller's card: what it sells, its prices against rivals, rank, history, and what the chain says — payments, payer wallets, concentration, hosts that share its wallet
operatorthe hosts one wallet group runs, and what they took together
agents_at_workbuyer wallets whose x402 payments reached three or more sellers

Claude Desktop, Cursor, Claude Code or any MCP client:

json
{"mcpServers": {"x402-atlas": {"command": "python3", "args": ["/path/to/x402-atlas/tools/atlas_mcp.py"]}}}

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:

uvx --from git+https://github.com/ausrine-labs/x402-atlas x402-atlas-mcp

Claude Code

claude mcp add x402-atlas -- uvx --from git+https://github.com/ausrine-labs/x402-atlas x402-atlas-mcp

Claude Desktop (claude_desktop_config.json)

json
{  "mcpServers": {    "x402-atlas": {      "command": "uvx",      "args": ["--from", "git+https://github.com/ausrine-labs/x402-atlas", "x402-atlas-mcp"]    }  }}

Cursor (~/.cursor/mcp.json, or .cursor/mcp.json in a project)

json
{  "mcpServers": {    "x402-atlas": {      "command": "uvx",      "args": ["--from", "git+https://github.com/ausrine-labs/x402-atlas", "x402-atlas-mcp"]    }  }}

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
SourceWeft 尚未在沙箱中启动过该软件包,因此其工具未知。

版本历史

1
  1. v0.2.0最新Sep 27, 2026

评分

已满足适用检查项的 50%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分

    请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。

  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分

其他 Atlas 集成