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%daydreams344d ago0xd2d4b3…6cc727
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams344d ago0xca9132…ffcd79
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams344d ago0xcd88f1…47e106
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams344d ago0x02330c…653088
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams344d ago0x94909a…fd7aa0
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams344d ago0xd3db81…d9bdca
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams344d ago0x298743…adfbc6
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams344d ago0x031d79…dab0af
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams345d ago0xf3864f…ce6c34
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams345d ago0xfe080c…8356b8
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams345d ago0x798c4d…67bc69
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams345d ago0x9952f3…614fe5
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams345d ago0x76cba4…f91a70
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams345d ago0xe4b237…089227
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams345d ago0xc71342…1b56a1
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams345d ago0xd7b256…a629eb
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams345d ago0xc12b1f…983b89
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams345d ago0x285eb0…e61045
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams345d ago0x05a7be…0efedd
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams345d ago0xa41911…52594c
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams346d ago0x5d73b9…6cf0d4
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams346d ago0x52acc5…d5d655
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams346d ago0x35ee51…07d77f
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams346d ago0x17eee8…88ed07
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams346d ago0x552c26…09c3ae

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.