checked 2026-09-20
Unnamed x402 service
0x0b8fb4bc97d89e9397f7a4060889adc946adfdf4
#490 of 521 by verified x402 revenue top 94%|
Direct recipient
Receives payments and keeps 0.0% of them.
★ Whether 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.
Claimed vs observed
Nothing is claimed.
No ERC-8004 registration, no x402 authorization, and no listing in any public x402
directory was found for this address, so there is nothing to compare against what the chain shows.
The chain shows $718.08 received from 16 payers
across 145 payments, and $0.00 kept.
Measured
Received
$718.08USDC
lifetime, exact on-chain · no x402 settlement on record for this address
Kept
$0.00USDC
nothing kept · USDC only
Payers
16
exact · every payer captured
Payments
145
exact total
Classification — what we decided from those measurements, never a rating
Verdict, every day we ran
Verdict each day
organic payments on all 40 measured days
How a verdict can change
Every change is adjudicated in public and logged with its date and reason. Nothing here
is edited silently, and no verdict is ever removed from this row.
Trends
No settled day has been attributed to this address yet, so there is no series to
plot. The lifetime figures above are all-route and unaffected.
Where it sends
0xee7a…405572.6%
0x3304…566a27.4%
Shares of every USDC dollar that left this address, for its
whole history. 2 destinations in total.
How it was paid
carried a valid x402 authorisation16.7%
no authorisation we could read83.3%
No x402 settlement on record. Our settlement store holds none for this address. The volume shown above is all-route USDC, a different and wider measure. That is a limit of our capture, not a finding about this address — the chain sample below did find x402-shaped payments here that our collector has not reconstructed. Separately, a sampler looked at 6 payments on 2026-09-19, 1 day ago, and classified them x402 direct — though 5 of the 6 carried none it could read, so that label rests on 1. That is an indication from a small sample, not a finding about this address.
Where the money went
destination
USDC sent
share
0xee7a…4055
$521.28
72.6%
0x3304…566a
$196.80
27.4%
These are addresses, not identities · we name one only where
a public source already does. This does not include the ETH reported below — the fold is USDC-only.
What we read off the chain measured
Facts, not judgements. Every figure below is USDC taken from Base settlements.
USDC received
$718.08
lifetime, all-route, exact on-chain
USDC sent on
$718.08
100.0% of received
Settled and attributed
$0.00
no measured day yet
Distinct amounts
51
average $9.84
7 / 30-day trend
—
a trend needs 5 measured days on each side and at least $1 a measured day to divide into; this address does not clear both yet, so no percentage is printed
Not counted in retained
0.156 ETH
left this address in 8 transfer(s). Retained counts USDC only, so it is an upper bound · this movement is real and is not in it. No dollar value is assigned. Separately, at least 34 transfer(s) across 7 token contract(s) are attributed to this address for tokens it never received. A block explorer will show them; we do not count them as outflow.
What we concluded from them computed
Derived figures, each stating the arithmetic behind it.
Reality ratio
0%
retained — processed
Confidence
Medium
16 payers · 51 distinct amounts
Volume backing
Elevated
$718.08 backed by 16 payers and 51 distinct amounts
Sybil state
clean
first-funder measured
Average per active day
$0.00
no active day
Consistency
0%
of days since first settlement had activity
Why this verdict
Named rule R3 · Organic payments, no circular flow
Payments arrive in varied amounts at irregular intervals, and the money does not circle back to the people who sent it.
Kept of received0.00%
Distinct payers16
Distinct amounts51
In, out and kept — 2026-09-19
Not measured for this address on 2026-09-19. AQUIX builds this split from
two independent series and this address appears in neither on that day. That is an absence of
measurement, not a measurement of zero · the attribution is not claimed either way.
Who funded the payers
Sybil stateclean
First funder of the payers
0x1b63…2ca9 · contract, treated as infrastructurePayers16 distinct paying addresses · 51 distinct payment sizes
A shared first-funder is a shared-funder pattern, so we name it.
The test treats it as a signal only when the funder is not infrastructure and covers 50% or more of payers
— most wallets legitimately get their first funds from one exchange, bridge or router.
Time and trust
First seen
Entered the register on 2026-06-11.
Final through — · no streak.
Verdict history
Every snapshot ever taken, never rewritten.
40 snapshots recorded · no verdict change: this agent has held the same verdict since first seen.
Corrections
No published correction affects this agent.
Late writes
No day for this agent has ever been completed after publication.
Basis
Snapshot 2026-09-20 · methodology v3.2.
Retained and processed are never summed. Retained is clamped at zero, so it can overstate but never understate.
Check it yourself. Every figure on this page is reconstructed from public Base
chain state. No API key, no account, no trust required — open the address and compare the USDC
transfers against what we show.
Notes and limits
Paid through
No settlement in the 7-day window · 2026-09-14 to 2026-09-20 · is attributed to a named facilitator. That is not the same as saying no rail ever carried its money: the lifetime total above is all-route and covers the whole history, and this window does not.
Coverage of the daily series
0.00% of this agent’s money. The chart and the day strip are drawn from that series; the lifetime totals are not, and the two are never added together.
Per day: settled
no attributed day for this address yet, so the daily panels are omitted rather than drawn empty.
What this page cannot show for this agent
- Name no single public name: either no directory, Basename or manifest carries this address, or it publishes several unrelated services and none of them is its name
- Claimed vs observed no ERC-8004 registration and no x401 authorization exist to compare against
- First seen first-seen is derived from settled days and this address has none
- Volume processed, 30-day no daily row exists for this address yet, so there is no window to total
- Per day: in · out · retained this address has no in/out row on the newest complete day and fewer than two measured days in the daily flow series
- Every day renders no settled days to render
- Final through no settled day has been finalised for this address
- Daily averages no settled days
- 7 / 30-day trend a trend needs TWO measured periods; this address does not yet have an earlier window to compare against
- Streak no consecutive settled days
- Consistency no settled days
- Coverage badge coverage has no meaning without settled days
Why this agent has no name
We check Basenames, the public x402 discovery directories, ERC-8004, Farcaster, contract bytecode and published deployment manifests. Either nothing is registered, or the address publishes several unrelated services and no one of them is its name. That is a fact about what this operator chose to publish, not a gap in the audit.
How a rule works here
One sentence per rule, stating what the rule tests and citing figures already on this page. The threshold itself is not published, so it cannot be gamed. Rules are named so that a verdict which changes can be pointed at. The full set of rules
Everything else is measured, not inferred. A figure we do not hold is never rendered as zero.
