These figures and labels — including every “verified” — are the old method’s, frozen as of 27 Oct 2026 while the method is revised. Nothing here is updated until launch: any “measured daily” or “one snapshot every day” line below describes the old schedule. The new method will be published at least 7 days before the new site. The new figures follow at launch.
AQUIX 2026-10-27

Definitions

Every word AQUIX publishes, defined once, with how it is computed and what it equals today. The methodology page explains the method; this page defines the words. If you quote AQUIX, quote from here.

Every figure on this page is read from the published register when the page is built. None is typed.

The money words

Received, all routes
Every USDC dollar that arrived at an address on Base, by any route — x402 or not.
how it is computedThe address’s USDC balance plus the USDC it sent out, as our record holds them.
today$144,019,348.34 across 995 published addresses
x402 revenue, verified
The part of what an address received that we can tie to an x402 payment: a USDC transfer whose transaction also carries an EIP-3009 AuthorizationUsed event naming the same party that sent the transfer.
how it is computedThe sum of settled amounts in the settlement record. It is always the smaller of the two figures.
today$65,520,838.16 — 45.49% of everything received
Outflow
Every USDC dollar an address sent out, in any transaction, at any time. Lifetime, not per payment.
how it is computedThe sum of USDC transfers out of the address. USDC only: value that left as ETH or another token is not in it.
Kept (retained)
Received minus outflow, never below zero. Because, in these figures, received is the balance plus the money sent out, kept is in effect the address’s USDC balance, floored at zero.
how it is computedGREATEST(received − outflow, 0). Because it is floored at zero and counts USDC only, kept can overstate what an address kept and never understates it.
today$1,810,187.68 — 1.26% of everything received
Pass-through
The address forwards money onward inside the same transaction that paid it.
how it is computedMeasured per transaction. Not the same as outflow: an address can send out everything it received and have no pass-through, because it spent the money later.
Kept and received are never added together. They measure different things: a payment processor can move a lot of money and keep almost none of it.

The verdict words

How to read a verdict

Figures are measurements. Received, kept and settled amounts are reconstructed from public Base chain data.

A verdict is a classification: our judgement, reached by published rules from those figures. It describes how money behaves at an address. It is not an endorsement, an accusation, or a claim about who operates the address.

Every verdict is shown with three things beside it: how strong the evidence is, what we know about identity, and whether the address is published in the register.

Pages published before 2026-09-17 use earlier labels: Verified — service = Service · Verified — conduit = Conduit · Verified — circular flow = Circular flow. The verdicts are unchanged; only the words on the badge changed.

Service
Paid through x402, and not identified as a router, a rail or wallet software.
how it is computedMost services were admitted by one of our named rules for organic payment behaviour: payments arriving in varied amounts, at irregular intervals, with no circular flow. The rest reach this verdict by default: no named rule decided them, and the share of what they received that went back to their own payers stayed below the limit our rules set. 871 of 907 were admitted by a named rule in this snapshot; 36 were not. The verdict describes how an address was admitted, not how much it keeps: 364 published addresses keep less than 0.05% of what they receive, and the Kept figure on each page is the measurement.
today907 in this snapshot · evidence: behavioural
Conduit
A payment router, rail or facilitator, identified by its role in the protocol or by a published deployment. Money moves through a conduit by design.
how it is computedThe test is a role, not a pattern: an address is a conduit because it has been identified as a router or a rail, never because of how its money moves. An address can forward almost everything it receives without being a conduit; its page says so when that happens.
today27 · evidence: attribution
Circular flow
A large share of everything the address received went back to the addresses that paid it, and no named rule for organic payment behaviour applied. Its volume overstates the demand it represents.
how it is computedThe share is measured on everything received, over the address’s whole history, and printed on its page. The limit that triggers this verdict is set in our rules and is not published. This describes the money, not the operator: value returning to the same counterparties is also what a trading program, a settlement loop or a refund flow looks like.
today48 · evidence: behavioural
Wallet software
A wallet product rather than a business, identified by its code or by a published deployment, never by pattern alone.
how it is computedWallet software is published so readers can see it rather than quietly dropped. Like every row, it is ranked by the x402 revenue we can verify.
today13 · evidence: attribution

The three things shown beside every verdict

A verdict answers one question: what does the money do at this address? Everything else is a separate axis, shown separately.

Evidence strength
How much data stands behind the verdict — not how good the address is.
how it is computedHigh, Medium or Low, set by how many distinct payers and how many distinct payment amounts the verdict rests on, sampled across the address’s whole history rather than a recent window. Thin evidence means the verdict rests on a single sampled payer. It may still be right, but it is the weakest evidence we publish, and every page it applies to says so. The exact limits between High, Medium and Low are set in our rules and are not published.
today132 high · 250 medium · 613 low · 533 thin
Identity
Named — a public name exists, and its source is shown: a Basename, or an x402 directory listing. Unnamed — no public source names this address.
how it is computedWhether any address is operated by an AI agent is not verified. On-chain records show that a payment settled, not who or what decided to make it. A name is a claim about the name, never about the operator.
today118 named · 877 unnamed
Name verified
A second, independent source agrees about the name — never about the operator, and never that the operator can be trusted.
how it is computedEither a Basename resolved on-chain, or a service name the operator lists in a public x402 directory and serves from its own registered domain.
today41 of 995
Register status
Whether an address is published, and if not, what we did with it. An address has exactly one current status.
how it is computedIn the register — published, with one of the four verdicts. Reclassified as wallet software — kept in the register with the wallet verdict. Removed — infrastructure — identified as protocol infrastructure and kept out of every total. Examined, not admitted — looked at, and not published. Not examined — known to us, not yet assessed. “Undecidable” is not a status; it is a census class (below).
today995 in the register in this snapshot

The census and the register use different classes

The census sorts every address paid on x402 in a seven-day window by what its money did. The register publishes only the x402 sellers that pass all our tests, each with a verdict. The two use different words, and one word appears in both.

“Conduit” means different things in the two. A census conduit forwards money onward inside the same settlement transaction. A register conduit is a router or rail identified by its role. An address that is paid and moves the money later counts as an earner in the census and can still be a service in the register.

Census classWhat it meansClosest register outcome
EarnerPaid regularly across the window, on many days and many payments.Service
ConduitForwards onward inside the same settlement transaction on almost every payment.Conduit — detected differently; see the note above.
Bot-shapedPaid on many days, almost always the same very small amount.Examined, not admitted
PassengerOne or two payments on a single day.Not examined
InfrastructureNamed on a published rail or disburser list.Removed — infrastructure
UndecidableToo little activity to say; the census says so rather than guessing.Not examined

The limits behind these classes are set in code and are described here in words, not published as numbers. The census changes nothing: it never moves an address into or out of the register, and it carries no verdict.

The measurement words

Measured day
A day our collector ran and read the chain end to end.
how it is computedA day it did not run is shown as missing, never as zero. Percentages are averages per measured day, never window totals, because a total would count a missing morning as zero.
Unmeasured
We did not look, or could not finish looking.
how it is computedUnmeasured is never shown as zero: a gap and an absence of money are different facts.
Counted / ceiling
Whether a figure is a count or a ceiling.
how it is computedReceived and payer counts are counts of what our record holds. Kept is always a ceiling: it is floored at zero and counts USDC only.
Final through <date>
Coverage proved by the record, not by the calendar.
how it is computedA day is published only once its blocks have been read without a gap.
Payer
A distinct address that sent USDC to this one.
how it is computedExact where every payer was captured, and the page says when it was not.
today125,891 payers, counted per address and added across the register — a payer that paid two addresses is counted at each

Membership — who is in the register

In scope
The address has at least one x402 settlement AQUIX holds on-chain evidence for.
how it is computedThe settlement record decides; sampling is used only where no settlement is held, and never overrides held evidence.
The x402 Seller Registry
The published set: addresses that passed the classifier and the scope test. A check for payers funded by one source has been run on only part of the register.
how it is computedIt is small on purpose: most addresses on a payment rail are not businesses, and a register that claimed otherwise would be measuring traffic and calling it commerce.
today995 published, 118 with a public name
Removed
Addresses that are the rail rather than paid by it: payment-protocol contracts, merchant payout contracts, wallet infrastructure.
how it is computedThe list is kept by hand, so it holds only what we have already found; it is not an automatic filter.

What AQUIX does not claim

That any address is an AI agent
It cannot be shown from chain data, so we do not claim it.
how it is computed“Agent” names the category of payments; what we verify is economic behaviour: money arriving on the x402 rail, and what happened to it.
That the verified figure is all of x402
x402 has more than one settlement scheme. AQUIX reconstructs the exact scheme, which settles on-chain through EIP-3009 and can be checked transfer by transfer.
how it is computedPayments settled through other schemes are not counted. As those are adopted, the figure covers a smaller share of x402 activity, and a fall in it is not evidence that sellers earn less.
That this is all of Base
The chain carries far more than x402.
how it is computedAn address whose income is not x402 — a router, a bridge — is not in the register even when it is very large.
AQUIX Evidence before trust @aquixai intelligence@aquix.ai
Why you do not have to trust us

Every figure is reconstructed from public Base chain state. No API key, no account, no trust required — open an address and compare the USDC transfers against what we show. Corrections to published figures are logged with their date and reason.

AQUIX · an independent observatory of the x402 rail on Base · Measured daily at 07:00 UTC · Snapshot 2026-10-27 · Methodology v3.2 · Classifier v4 · Latest correction #10 · No protocol pays to appear here

Company names and logos are the property of their owners and are shown for identification only. Their appearance here does not imply any affiliation with, or endorsement by, AQUIX.