checked 2026-09-20
Unnamed x402 service
0x60a80cdb55ddeb8afef5b2f16f153bb0cb95e690
#422 of 521 by verified x402 revenue top 81%|
Direct recipient
Receives payments and keeps 89.2% 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 $44,710.98 received from 19 payers
across 129 payments, and $39,890.92 kept.
Measured
Received
$44,710.98USDC
lifetime, exact on-chain · no x402 settlement on record for this address
Kept
≤ $39,890.92USDC
upper bound · USDC only
Payers
19
exact · every payer captured
Payments
129
exact total
Classification — what we decided from those measurements, never a rating
Verdict, every day we ran
Verdict each day
organic payments on all 9 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 not verdict-backed
Every day in the span as a table (8 rows, 7 measured)
| day | settled USDC | settlements | average |
|---|---|---|---|
| 2026-09-04 | $397.00 | — | — |
| 2026-09-05 | $1,025.00 | — | — |
| 2026-09-06 | not measured — AQUIX did not run that day | ||
| 2026-09-07 | $5,738.00 | — | — |
| 2026-09-08 | $5,028.00 | — | — |
| 2026-09-09 | $962.00 | — | — |
| 2026-09-10 | $5,981.00 | — | — |
| 2026-09-11 | $10,999.00 | — | — |
These days were measured but not judged. We hold
15 settlements worth $30,130.00 across
7 days (2026-09-04 to 2026-09-11),
but no verdict was recorded for those days at the time. They are charted so the money is visible,
and marked so the difference is not lost. Average per day shown $4,304.29
· of the days present, not of the calendar.
Where it sends
0x3701…9c7b54.7%
0xe5e9…00c636.5%
0x7ff3…a2048.6%
0x75cb…cf3e0.1%
0x0afd…a6100.0%
Shares of every USDC dollar that left this address, for its
whole history. 5 destinations in total.
How it was paid
no authorisation we could read100.0%
x402 confirmed — 15 settlements on record. Every one is a USDC transfer whose transaction carried a matching EIP-3009 payment authorisation, reconstructed from public Base state. This is the proof, and it rests on all of them, not a sample. Separately, a sampler looked at 6 payments on 2026-09-19, 1 day ago, and found no authorisation it could read in that sample. That is an indication from a small sample, not a finding about this address, and where it disagrees with the settlements above, the settlements are what count.
Where the money went
destination
USDC sent
share
0x3701…9c7b
$2,638.00
54.7%
0xe5e9…00c6
$1,759.76
36.5%
0x7ff3…a204
$416.20
8.6%
0x75cb…cf3e
$6.00
0.1%
0x0afd…a610
$0.10
0.0%
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
$44,710.98
lifetime, all-route, exact on-chain
USDC sent on
$4,820.06
10.8% of received
Settled and attributed
$0.00
no measured day yet
Distinct amounts
93
average $429.91
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.000 ETH
left this address in 1 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 24 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
89.22%
retained — processed
Confidence
Medium
19 payers · 93 distinct amounts
Volume backing
Elevated
$44,710.98 backed by 19 payers and 93 distinct amounts
Sybil state
unchecked
funding provenance not 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 received89.22%
Distinct payers19
Distinct amounts93
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 stateunchecked
First funder of the payersnot measured
Payers19 distinct paying addresses · 93 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-09-12.
Final through — · no streak.
Verdict history
Every snapshot ever taken, never rewritten.
9 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 no VERDICT-BACKED day for this address — the days charted above are measured but were not judged at the time
- Volume processed, 30-day no daily row exists for this address yet, so there is no window to total
- Every day renders no VERDICT-BACKED day for this address — the days charted above are measured but were not judged at the time
- Final through no VERDICT-BACKED day for this address — the days charted above are measured but were not judged at the time
- Daily averages no VERDICT-BACKED day for this address — the days charted above are measured but were not judged at the time
- 7 / 30-day trend a trend needs TWO measured periods; this address does not yet have an earlier window to compare against
- Streak no VERDICT-BACKED day for this address — the days charted above are measured but were not judged at the time
- Consistency no VERDICT-BACKED day for this address — the days charted above are measured but were not judged at the time
- Coverage badge no VERDICT-BACKED day for this address — the days charted above are measured but were not judged at the time
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.
