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%daydreams352d ago0x20bb79…73b930
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams352d ago0xc48f0c…17dd6c
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams352d ago0x49ef9e…2c830a
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams352d ago0xbb39d6…b46ef2
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams352d ago0x7021d7…6cbbea
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams352d ago0x2b4b55…625030
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams352d ago0x196b8a…7aa0c7
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams352d ago0x9d7280…1814fc
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams353d ago0x844b3e…189824
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams353d ago0x4e5a14…aab952
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams353d ago0x787ed4…892d9b
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams353d ago0xf7bac0…240a6f
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams354d ago0x33ffd8…df278f
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams354d ago0x7688a6…59bee3
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams355d ago0xd5c92b…b44610
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams355d ago0x525720…51fbac
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams355d ago0x99f695…d1ce54
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams355d ago0x9e838b…480b32
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams355d ago0xe41ae5…489738
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams356d ago0x6ff920…34026e
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams356d ago0x038fd6…35007b
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams356d ago0x7adad4…0bc83d
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams356d ago0xe7e463…10529b
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams356d ago0x112de8…4f1278
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams357d ago0xcd2185…77e91c

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.