AgentReport

0x4eb835369ef68bcf883fd3c81b6024a2ef2bdbf6

0x4eb835369ef68bcf883fd3c81b6024a2ef2bdbf6Explorer
Paid out
$14.29
Last 7d vs prior 7d
Received
$14.25
Last 7d vs prior 7d
Settlements
120
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $14.29 of the $260.63M Roundhouse has indexed across 716,280 wallets — less than 0.0001% of it.

Chains (from the recent scan): Base (120)

What it buys

Grouped by the capability each merchant's catalogue is mostly about. A merchant counts once, in one group — nothing records which of its endpoints a payment bought.

GroupShareSpentCallsSellers
Not in any catalogue100%$14.29341

$14.29 went to wallets that publish no endpoint in any catalogue we crawl — spend we can see and cannot describe.

Services it paid

A settlement carries the payee and the amount, never the URL. These are the endpoints each payee publishes; no listed price matches an amount this agent paid, so nothing narrows them.

  • 0xac65…4417 · last paid 112d ago
    $14.29
    34 calls

    This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.

Balance now
Reading the chain…
Spending power
Reading the chain…
Burn rate
Reading the chain…
Runway
Reading the chain…

Funds flow over time

Activity

MarAprMayJunJulAugSep
LessMore

One square per day; click a day to see its settlements in the ledger.

Frequent counterparties

CounterpartyPaid themReceived backSettlementsLast
0xac65…4417$14.29$0.0034112d agoGraph
0xb90a…9ae4$0.00$14.2586112d agoGraph

Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.

Data quality

50% of observed volume is with a single counterparty, in all 120 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xb90a…9ae40x4eb8…dbf6Base$0.01100%fluxa112d ago0x42360c…6e4ea4
0xb90a…9ae40x4eb8…dbf6Base$0.01100%fluxa112d ago0x9406d0…ed9429
0x4eb8…dbf60xac65…4417Base$0.02100%fluxa112d ago0xe4a4ee…e8e98f
0xb90a…9ae40x4eb8…dbf6Base$0.01100%fluxa112d ago0x7825aa…b54cca
0xb90a…9ae40x4eb8…dbf6Base$0.01100%fluxa112d ago0xe92e4a…571a30
0xb90a…9ae40x4eb8…dbf6Base$0.01100%fluxa112d ago0xa3c377…4059a6
0x4eb8…dbf60xac65…4417Base$0.06100%fluxa112d ago0xc9fdfa…0da27d
0xb90a…9ae40x4eb8…dbf6Base$0.06100%fluxa112d ago0x99e145…3a6538
0x4eb8…dbf60xac65…4417Base$0.02100%fluxa113d ago0xcd107a…047b5c
0xb90a…9ae40x4eb8…dbf6Base$0.01100%fluxa113d ago0xbe29d1…00f0df
0xb90a…9ae40x4eb8…dbf6Base$0.01100%fluxa113d ago0xfef575…85bb21
0x4eb8…dbf60xac65…4417Base$0.01100%fluxa113d ago0xe15827…d33f94
0xb90a…9ae40x4eb8…dbf6Base$0.01100%fluxa113d ago0xe0c912…78bee8
0x4eb8…dbf60xac65…4417Base$0.01100%fluxa113d ago0x59eb8e…6cf4a6
0xb90a…9ae40x4eb8…dbf6Base$0.01100%fluxa113d ago0x29101d…217161
0x4eb8…dbf60xac65…4417Base$0.52100%fluxa114d ago0x985018…6db624
0xb90a…9ae40x4eb8…dbf6Base$0.50100%fluxa114d ago0x4e456d…8306af
0xb90a…9ae40x4eb8…dbf6Base$0.01100%fluxa114d ago0x246dd2…d63c36
0xb90a…9ae40x4eb8…dbf6Base$0.01100%fluxa114d ago0x3474e7…baae23
0x4eb8…dbf60xac65…4417Base$0.03100%fluxa114d ago0x192072…6739b4
0xb90a…9ae40x4eb8…dbf6Base$0.01100%fluxa114d ago0x97512d…a74f07
0xb90a…9ae40x4eb8…dbf6Base$0.01100%fluxa114d ago0x8feb14…3a9c9a
0xb90a…9ae40x4eb8…dbf6Base$0.01100%fluxa114d ago0x1ca408…eba2b9
0x4eb8…dbf60xac65…4417Base$0.05100%fluxa114d ago0xf836bd…1f3b76
0xb90a…9ae40x4eb8…dbf6Base$0.01100%fluxa114d ago0xd376f9…fc54a7

Hand this page to an agent

Copy the prompt and paste it into Claude, an MCP client or your own agent — it will check what 0x4eb835369ef68bcf883fd3c81b6024a2ef2bdbf6 has actually paid for over the free read API. No key, no account.

GET api.roundhouseai.io/v0/agents/0x4eb835369ef68bcf883fd3c81b6024a2ef2bdbf6

Open skill.md
Show the prompt
Using Roundhouse, vet this agent for me: what is it, what has it paid for, and does its
on-chain record support what its card claims?

  Agent: 0x4eb835369ef68bcf883fd3c81b6024a2ef2bdbf6

curl -s 'https://api.roundhouseai.io/v0/agents/0x4eb835369ef68bcf883fd3c81b6024a2ef2bdbf6'
curl -s 'https://api.roundhouseai.io/v0/entities/0x4eb835369ef68bcf883fd3c81b6024a2ef2bdbf6/settlements'

Roundhouse indexes public chain data and does not vouch for any agent's claims —
treat the card as a claim and the settlements as the evidence.

The /v0 API needs an API key (`authorization: Bearer rh_live_…`) on everything except
/v0/unified* and /v0/endpoints. Mint a personal key for $0.01 at GET https://api.roundhouseai.io/v0/test/x402,
or use an organization key from https://roundhouseai.io/dashboard/team.

If you do not have Roundhouse tools or skills installed, read
https://roundhouseai.io/skill.md first — it is the whole procedure.