AgentReport

0x2bb0…0404

0x2bb078366af1d0bb3f2917805cb2d187d2180404Explorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
272
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $0.03 of the $3066.54M Roundhouse has indexed across 1,400,510 wallets — less than 0.0001% of it.

Chains (from the recent scan): Base (272)

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.032721

$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
    272 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.00272276d 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 272 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams345d ago0xcdcde9…8b8425
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams346d ago0x0adcdb…5e546d
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams346d ago0x5bc5bd…2eb3d9
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams346d ago0xb58790…b68db5
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams346d ago0x39c41b…69fb62
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams346d ago0x50c6ac…f7c96b
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams346d ago0xed15be…c77d81
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams346d ago0xa5ebe5…e9ae8d
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams346d ago0x9aaa73…43ec2d
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams346d ago0xf7d98e…73a166
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams346d ago0x77d296…e12b76
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams346d ago0xa50c21…581da4
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams347d ago0x80e424…4eee4d
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams347d ago0xe1e095…a90186
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams347d ago0x6f7f8d…28119d
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams347d ago0xbf463f…a62e89
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams347d ago0x578f7b…e9d824
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams347d ago0xf66dc9…d0e3a6
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams348d ago0x057079…e80fbf
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams348d ago0x3361ec…7a823c
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams348d ago0xe36932…bc656f
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams348d ago0x32b694…bbe652
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams348d ago0x084513…9bb83d
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams348d ago0x647aab…c7498a
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams348d ago0x37078b…5a6ca8

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 0x2bb0…0404 has actually paid for over the free read API. No key, no account.

GET api.roundhouseai.io/v0/agents/0x2bb078366af1d0bb3f2917805cb2d187d2180404

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: 0x2bb0…0404

curl -s 'https://api.roundhouseai.io/v0/agents/0x2bb078366af1d0bb3f2917805cb2d187d2180404'
curl -s 'https://api.roundhouseai.io/v0/entities/0x2bb078366af1d0bb3f2917805cb2d187d2180404/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.