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.43M Roundhouse has indexed across 1,401,575 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%daydreams349d ago0x28e85a…1f3660
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams349d ago0x440435…cb6567
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams350d ago0x821552…7b1b22
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams350d ago0xedddd7…b7b2de
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams350d ago0x8b6c02…70d302
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams350d ago0x04489e…6fd787
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams350d ago0x945db5…a3dc31
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams350d ago0xb69a0c…965b9b
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams350d ago0xa681fc…09523b
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams351d ago0x14f209…83f5dc
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams351d ago0xd36415…e68257
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams351d ago0x14efaa…ae7f9f
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams351d ago0xc142fc…cd062c
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams351d ago0x479a13…e5962b
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams351d ago0x6ff04c…eb4062
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams351d ago0xfe8cc7…438fec
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams351d ago0x6547a0…6e3a83
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams352d ago0x34b3a5…753557
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams352d ago0xcd0b93…e67533
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams352d ago0xfbfbb5…1f6458
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams352d ago0xeccf2b…c9c8f7
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams352d ago0x95cb06…465aed
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams352d ago0x5967c2…928c1d
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams352d ago0xae0db1…d9f080
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams352d ago0x733175…4caea4

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.