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,255 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%daydreams343d ago0x5c5f76…0aa7c0
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams343d ago0x8fe52f…3385c0
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams343d ago0x397d05…496a18
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams344d ago0xa370d3…d1186b
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams344d ago0xb37eb8…33aad9
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams344d ago0x115e90…2a4145
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams344d ago0xea8178…1b91bd
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams344d ago0xb584fa…553e87
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams344d ago0x97dd68…e2f3f3
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams344d ago0xf58612…75e047
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams344d ago0x36eb80…79a62f
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams344d ago0x5d8ce9…d74807
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams344d ago0x501b85…14a532
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams344d ago0x20b2b4…c8a924
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams344d ago0x2fedad…628d11
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams345d ago0x71b9dc…3f78b8
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams345d ago0xdb403b…116458
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams345d ago0x61a5a8…4afabb
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams345d ago0x308094…06c717
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams345d ago0xadef45…f6fc32
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams345d ago0xb3b232…f197c2
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams345d ago0xddb234…e938b7
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams345d ago0x0220f5…cc68b2
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams345d ago0xad5ea0…39cd10
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams345d ago0x4dbf96…f09284

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.