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.25M Roundhouse has indexed across 1,401,192 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%daydreams346d ago0x6854a4…d20ea0
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams346d ago0xd7bd2f…fc78a6
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams346d ago0xff8db9…57aa91
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams346d ago0x7a309d…fcef13
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams346d ago0xf6ee97…78564b
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams347d ago0x0cb726…f950fc
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams347d ago0xb8c180…1db41a
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams347d ago0x98e3b2…7d35eb
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams347d ago0x9abaca…64c6bb
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams347d ago0xf47572…3147df
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams347d ago0x8576c7…cf869b
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams347d ago0x4579ec…e7ae82
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams348d ago0x2b5f1c…b7ccd2
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams348d ago0xabf039…1c9ed3
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams348d ago0x555b04…a12e7f
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams348d ago0xcedd39…6eefc3
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams348d ago0x718903…844e2e
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams348d ago0xe11d8a…54edd7
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams348d ago0x6ee7dc…3f1fd8
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams348d ago0xec9554…b00585
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams348d ago0xa922fb…7c57b1
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams348d ago0xb2a785…20d67e
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams348d ago0x574dce…8d569c
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams349d ago0x988b8c…2e5935
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams349d ago0x127965…e62efc

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.