AgentReport

0xf180…bba8

0xf180df5f54cf7d0899d4c42901126463d007bba8Explorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
263
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $0.03 of the $3067.00M Roundhouse has indexed across 1,401,091 wallets — less than 0.0001% of it.

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

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%$0.032631

$0.03 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.

  • 0x6482…b779 · last paid 276d ago
    $0.03
    263 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

MayJunJulAugSepOctNov
LessMore

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

Frequent counterparties

CounterpartyPaid themReceived backSettlementsLast
0x6482…b779$0.03$0.00263276d agoGraph

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

Data quality

100% of observed volume is with a single counterparty; all observed volume is with one counterparty, in all 263 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams326d ago0x7567d7…f905ae
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams326d ago0x0063b4…12f65e
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams326d ago0x9c573c…c46b6f
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams326d ago0x66fcd2…2f2156
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams326d ago0x64586d…cd3ef2
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams326d ago0x893a88…d3c944
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams326d ago0x53cde4…208b5c
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams327d ago0x022a2c…798f2d
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams327d ago0x2006d0…48d183
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams327d ago0x5f3206…a10452
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams327d ago0x18c497…f4c1a1
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams327d ago0x64f1a4…bd0815
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams327d ago0x74c8d6…8516e2
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams327d ago0x7c5794…764fb1
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams328d ago0x39f186…6ca8b7
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams335d ago0xab2582…42e073
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams337d ago0x4e6fee…72e68b
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams337d ago0x6c1da1…763acb
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams337d ago0x8930d2…59f155
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams337d ago0x25f0bc…743c47
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams337d ago0xae4372…b3fab7
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams338d ago0x9a14da…badc65
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams338d ago0xe83882…d4499a
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams338d ago0xe73817…39f514
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams338d ago0x654dad…67adbd

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 0xf180…bba8 has actually paid for over the free read API. No key, no account.

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

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: 0xf180…bba8

curl -s 'https://api.roundhouseai.io/v0/agents/0xf180df5f54cf7d0899d4c42901126463d007bba8'
curl -s 'https://api.roundhouseai.io/v0/entities/0xf180df5f54cf7d0899d4c42901126463d007bba8/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. Either pay over x402 (mint a personal key for $0.01 at
GET https://api.roundhouseai.io/v0/test/x402), or ask me for an organization key, which I create at
https://roundhouseai.io/dashboard/connections. If you have neither, ask before going further.

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