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%daydreams341d ago0x026742…274927
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams342d ago0xd09b80…e1c83f
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams342d ago0x12c491…50abef
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams342d ago0x9a08d7…120a59
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams342d ago0xc953b4…204da5
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams342d ago0x43dc90…e10e1c
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams342d ago0xe13b1e…5505ba
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams342d ago0x382233…4b8bb0
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams342d ago0x4ffca0…524fd4
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams342d ago0x87f38f…9c5663
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams342d ago0xa2f3a5…08338a
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams342d ago0x20927a…e3b9bb
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams343d ago0x94b909…37c666
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams343d ago0xc10105…6b2502
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams343d ago0xe67bd8…4144ab
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams343d ago0x92efdc…066fb2
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams343d ago0x8fd905…177de3
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams343d ago0x326743…ed013e
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams343d ago0x93b223…a230d4
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams343d ago0xd700b5…fec7f0
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams343d ago0x46191f…6e74b3
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams343d ago0x89c90d…7d6eea
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams343d ago0x163b6d…753b08
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams344d ago0xc8437a…af372d
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams344d ago0x1d5ea4…9d9372

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.