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%daydreams352d ago0xa10290…bfd6c4
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams353d ago0x7a0263…fb44f5
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams353d ago0x1cd259…259015
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams353d ago0x1058a1…565cd0
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams353d ago0x35a738…7883b4
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams353d ago0x9129c6…44d408
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams355d ago0x76a3bc…c6f8ce
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams355d ago0x425042…9363ef
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams355d ago0x99448e…0c6fc3
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams355d ago0xc7a784…fd0a56
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams355d ago0x27c601…25a0e5
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams356d ago0xbcdb30…8ee7ea
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams356d ago0xdcd8f3…44dc37
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams356d ago0x665ca7…a54f4a
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams356d ago0xb988e0…638e5b
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams356d ago0xd9136e…e4ce58
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams356d ago0xf52af2…ca795f
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams357d ago0x2b4b45…0851a6
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams357d ago0xa57c36…fe7351
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams357d ago0x0a3780…011d76
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams358d ago0x638cbc…3ad0d0
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams358d ago0x6bf9c2…1e32e0
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams358d ago0x203087…821627
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams358d ago0xb94e30…0e5a50
0xf180…bba80x6482…b779BaseBase$0.0001100%daydreams358d ago0xbaaedd…383b44

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.