Liveness, rung by runghow the rungs are defined →

Every registration on Base enters at the top. Each ring is the share that reaches that rung, and only the bottom three have ever moved money.

Ring width is on a log scale (the ladder spans three orders of magnitude), so read the figure, not the width. Silver rings are estimates: a sampled probe rate × the registration total, marked ~. Emerald rings are counted. Hover a ring for its share of the rung above.

The rank, last 90 daysdefinition →

Click a legend key to isolate a series. L8 and L9 are subsets of L7.

Detections by kind, all timethe log →

Click a kind to filter the alert lists. A detection is a shape with evidence; an incident is a detection that is also a harm, and recent.

Your agents

Live incidents, whole graphJSON →

What each shape means, and what to checkwhy behaviour, not identity →

Where agent money goesthe article →

Of — that left agent wallets, — was an agent paying someone.

Money flowdefinition →

Every dollar that left an agent wallet, to where it was counted, and the counted part by rail.

The x402 ribbon is a floor: only payments to sellers we can name are attributed to the rail. Hover a ribbon or a node.

Top ranked agents by observed spendingJSON →

Concentration is the story: a handful of agents and one escrow contract account for most counted spending. Hover a bar for the agent; click it to watch that agent.

Wallets, payers and the addresses they payidle money →

x402, measured against the registryour read of x402 →

x402 transactions per day, 90 daysour read of x402 →

Cited from x402scan. Most of this traffic is not from agents with an on-chain identity: among registered agents, x402 is a small share of payments by count.

Who registers, who mints, who answersthe ERC-8004 read →

New registrations per day, 90 daysdefinition →

Spikes are bursts: one address minting hundreds of names in an hour. A registration count measures issuance, not activity.

ERC-8004 reputation, read from the registry's own logsdefinition →

Feedback is a signal format, not a score. A handful of raters write most of it, so a rating says as much about the rater as about the agent.

Market contextnever an input to rank or liveness

Partner catalogs, run through our qualifierJSON →

Identities each catalog lists, against the ones we could bind to a wallet that is not shared by many identities. Rates are over what we checked, never over a partner’s own census.

ERC-8004 issuance on BNB, counted from the chainJSON →

The identity registry sits at the same address on BNB as on Base, but each chain has its own storage: token id N on BNB is not token id N on Base. A mint here is issuance, never an agent. The chain gets a rank of its own only when a wallet bound to a BNB registration is seen paying a different address on BNB, which is the next thing the watcher learns to read.

Stablecoins sent by every BNB registration owner, receipt-checkedJSON →

Every owner wallet, not a sample: the USDT, USDC, FDUSD and USD1 each one sent to another address after its first registration on BNB, read every hour. Receipts from the public Binance nodes then split each transfer into a hop (the money came back in the same transaction), a DEX swap, a payment to a contract, or a payment to a plain wallet. A plain wallet can be an exchange deposit address or the owner's own other wallet. None of it is added to Base.

What we can and cannot see on BNB today

ERC-8004 issuance on Ethereum, Arbitrum One, OP Mainnet and PolygonJSON →

The identity registry sits at the same address on these chains as on Base, each with its own storage. Counts start the day we started watching each chain (27 September 2026); a mint is issuance, never an agent, and a chain gets a rank of its own only when a wallet bound to a registration there is seen paying there. On Base and Ethereum registry events also arrive by webhook within seconds.

Solana agents: the Metaplex registry, their cards, wallets and paymentsEngine →

Solana's on-chain agent registry is Metaplex's MPL Agent Registry. Each record points at an MPL Core asset; its registration file is graded like a Base card, and the agent's own wallet is the asset-signer address derived from the asset. Payments count the net USDC and USDT that left the agent's wallet or its owner's wallet after registration, swaps excluded. Never added to Base.

x402 Bazaar: who sells, on which chainJSON →

Coinbase’s catalog of paid endpoints, read whole every six hours. A listing is an offer to sell, not a payment; payments are counted on the chains we read. It is the one view of x402 across Solana, Polygon, Arbitrum, BNB, Robinhood Chain and the rest that needs no chain read.

Checks by stateevery check →

Flagged right nowJSON →

An agent can read its own books, or any ranked agent’s, with a plain GET. No key, no login. Every value carries as_of, a producer and a definition id.

curl -s "https://agenticfinancegraph.com/api/agent?id=53008&format=json" \
  | jq '.agent | {liveness, usdc_float, pay, incidents: (.incidents|length)}'

Free tier: one agent per call, top 25 on the roster, 25 newest detections, no evidence objects. Fair use: cache for five minutes (the CDN does).

Paying, as an agentmanifest →

Evidence packs cost 1 to 5 cents in USDC on Base each (bundle 10 cents, revaluation 25 cents), paid over x402 v2: the check answers 402 with a PAYMENT-REQUIRED header, the agent retries with a signed PAYMENT-SIGNATURE, and the receipt comes back in PAYMENT-RESPONSE. The manifest lists every price and the receiving address; Coinbase’s facilitator settles on Base.

We never hold keys and never sit in the payment path: Coinbase's facilitator verifies and settles the agent's own signed authorization. An agent pays us the way it pays any x402 seller.

Paying, as a personcompare plans →

Plans are paid in USDC on Base from the wallet you signed in with: Watch free (3 agents), Operator 29 USDC per 30 days (25 agents, evidence packs included), Team 149 USDC per 30 days (250 agents, packs and revaluations included). Your wallet shows the exact amount and the receiving address before you approve; no gas, no card, and nothing renews by itself.

Where the money goes: straight to one published receiving address, the same one the checks' manifest names (payTo). We never hold your funds or keys, and the transaction is your receipt. Upgrade

Your accountUpgradeSign out

Wallet

— Copy basescan →

Plan

—

Agents watched

—

Signed in until

—

Telegram alerts

Link Telegram Opens @AgenticGraphBot with a one-time code (15 minutes). Linked, a chat watches as many agents as your plan (Watch 3, Operator 25, Team 250); /mine lists the agents this wallet owns.

Sync across devices

Keep my watch-list, notes and rules on my account—

Motion

On (default)Follow my device settingOffThe clock hand and the falling drop stop when your device asks for reduced motion (Windows: “Show animations” off).

Your wallet is your account: there is no password and nothing to reset. Your plan and your purchases are recorded against this address on our side, so they follow you to any browser you sign in from. The watch-list, allow-lists, notes and rules stay in this browser unless you switch sync on; then a copy is kept on your account too, and switching it off deletes that copy. Delete my account

Your purchaseswhat a pack is for →

Every plan and evidence pack paid by this wallet, with its on-chain receipt. A pack can be downloaded again here at any time; the receipt is your proof of purchase, and the file cites it.

Alert rulesReset to defaults

Set any number to 0 to switch that alert off. The drain shape and the new-counterparty rule look at the record the Desk reads, the 25 newest payments, after at least three earlier ones; an allow-listed address on an agent’s card never triggers either. The public drain_pattern detector uses the same shape at 5× and $250. Below $10 of float an agent drops from L8 to L7, which is why the low-float default is $10.

Your data

Watch-list, allow-lists and alert rules are saved in this browser’s local storage (afg-desk). To draw a card, the Desk asks our API for that agent’s record and sends your session with the request, so the answer carries exact balances; our host keeps standard request logs (IP address, time, URL). We do not store your watch-list unless you turn on sync. To use the same Desk on another browser or device, turn on sync, or export here and import there.

Export watch-list (.json)Import watch-listClear this browser

Simulate your thresholds on real agentsRun on the top public agents

Runs the alert rules above over the highest-ranked public agents without adding them to your Desk, so you can see what your settings would flag before you watch anything. Change a threshold and the result updates.

How the Desk tracks your agentsthe ladder →

1. You add an id. A token id, a slug or the bound wallet. The Desk asks /api/agents?q= whether it is ranked: a bound wallet observed paying a different address after the registration existed. If it is, the id, token and slug are saved under afg-desk in this browser and nowhere else. Paste several at once, separated by commas or new lines, to add a whole fleet.
2. Every visit, every card reads the public record. /api/agent?id=…&format=json gives the rank, the bound wallet, the float, the 25 newest payments with their transaction hashes, the bindings and the incidents; /api/detections?actor=… gives every detection on the id. A signed-in Desk sends its session with the request and gets exact floats; a paid plan also gets the full tiers. The watch-list itself stays in this browser unless you turn on sync, and our host keeps standard request logs (IP address, time, URL).
3. We keep the record fresh on our side. The registry watcher sees a new registration within minutes. Payments: every ranked wallet is pushed to us the moment a USDC transfer lands, and the payment scan re-reads each one on a schedule (agents that paid in the last 30 days daily, funded ones weekly, the rest monthly) with the receipt check that excludes routing hops before anything is counted. Floats and declared endpoints are probed daily. The pulse clock on the Overview shows the age of every feed, and the data checks run on our own tables every three hours.
4. Alerts are computed here, in your browser, from the rules above: the drain shape, a large first payment to a new address, a quiet wallet, low float, spending over your 30-day budget, one address taking too much of the spending, a delegation to code we cannot name or a change of delegation, plus the public detections on the id at the severity you chose. Each rule reads the record the card shows (the 25 newest payments) and skips addresses on the agent’s allow-list. Pause one agent or all; a paused card still loads its books.
5. Many agents. One card per agent, up to your plan: Watch 3, Operator 25, Team 250. Agents beyond the limit stay saved, unwatched, until you remove one or upgrade. Export the watch-list under Your data and import it on another device; the file holds ids, allow-lists and rules only. A link of the form /desk/app?watch=53008 opens straight on a card, so a platform can hand each operator their own.

Feed your agent Download the agent brief (.md)Config (.json)Copy prompt

Your agent never logs in and needs nothing installed: it reads the same JSON these cards read, with any HTTP client. The brief is a Markdown file written for an agent’s context (system prompt, skill folder or tool description): the endpoints, what each field means, the decision rules with your thresholds, how to pay for an evidence pack, and the ids and allow-lists you set on this Desk. The JSON is the same thing for code. Download again after you change agents or thresholds.