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%daydreams326d ago0xfe30d4…e2cdc2
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams326d ago0x9cd1b5…3f69cb
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams326d ago0xd8888f…853da8
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams326d ago0xca1be0…389ea3
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams326d ago0x694f55…1cfb88
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams326d ago0xc1f514…c4a1d6
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams326d ago0x39ec45…43e298
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams326d ago0x7532df…284df2
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams326d ago0x0d5fb3…885387
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams327d ago0x864777…668a00
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams327d ago0x11fb98…98ff59
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams327d ago0x77d691…677e7c
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams327d ago0x7ce168…2da667
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams327d ago0x2c8eb5…21e1da
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams327d ago0x494e6c…44cf04
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams328d ago0xf50291…e5da78
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams335d ago0x813b55…86f5f5
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams337d ago0x2db631…ec10aa
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams337d ago0x3b3ca8…6e999d
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams337d ago0xae6ad6…a1731c
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams337d ago0x1e3289…6b5dd0
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams337d ago0xe65af8…58254f
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams337d ago0x9f59b9…4848e5
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams337d ago0x8a7547…5ac35a
0x2bb0…04040x6482…b779BaseBase$0.0001100%daydreams337d ago0xb7e865…96208e

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.