AgentReport

0xb006…e64d

0xb0060af62779d97016bed22ee5cbb9d65e43e64dExplorer
Paid out
$34.50
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
21986
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $34.50 of the $261.15M Roundhouse has indexed across 716,924 wallets — less than 0.0001% of it.

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

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%$3.771,0002

Every merchant paid publishes at least one catalogued endpoint.

Services it paid

A settlement carries the payee and the amount, never the URL. These are the endpoints each payee publishes; for 2 of 2 the amount paid narrows the list to the ones listed at that price.

Folded from this wallet's 1,000 most recent settlements of 21,986 lifetime, which is as far back as one scan reaches — so every figure in this section is a floor, and the totals above are not.

Balance now
Reading the chain…
Spending power
Reading the chain…
Burn rate
Reading the chain…
Runway
Reading the chain…

Funds flow over time

Activity

MarAprMayJunJulAugSep
LessMore

One square per day; click a day to see its settlements in the ledger.

Frequent counterparties

CounterpartyPaid themReceived backSettlementsLast
0x0495…eed9$2.30$0.00853225d agoGraph
0x8324…fd0e$1.47$0.00147238d agoGraph

Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.

Data quality

61% of observed volume is with a single counterparty, in the 1000 most recent settlements scanned (its history is longer than the 2000-row scan cap).

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xb006…e64d0x0495…eed9Base$0.01100%payAI225d ago0xa21599…fe4ef3
0xb006…e64d0x0495…eed9Base$0.01100%payAI225d ago0x4515eb…83a753
0xb006…e64d0x0495…eed9Base$0.10100%payAI225d ago0x4bb18a…0b1400
0xb006…e64d0x0495…eed9Base$0.10100%payAI225d ago0x196981…031ea9
0xb006…e64d0x0495…eed9Base$0.10100%payAI225d ago0xddb346…29f5a4
0xb006…e64d0x0495…eed9Base$0.10100%payAI225d ago0xb153b5…54a826
0xb006…e64d0x0495…eed9Base$0.10100%payAI225d ago0x917af5…bac2af
0xb006…e64d0x0495…eed9Base$0.10100%payAI225d ago0x1e20f5…437409
0xb006…e64d0x0495…eed9Base$0.10100%payAI225d ago0x265553…03bf3c
0xb006…e64d0x0495…eed9Base$0.10100%payAI225d ago0x7ae763…7e138c
0xb006…e64d0x0495…eed9Base$0.10100%payAI225d ago0xaab510…d690ae
0xb006…e64d0x0495…eed9Base$0.10100%payAI225d ago0x16d5ba…eb4a36
0xb006…e64d0x0495…eed9Base$0.10100%payAI225d ago0x20c6f4…da3372
0xb006…e64d0x0495…eed9Base$0.10100%payAI225d ago0xf8658d…37ff75
0xb006…e64d0x0495…eed9Base$0.10100%payAI225d ago0x78ccdb…ed0daa
0xb006…e64d0x0495…eed9Base$0.10100%payAI225d ago0x339b69…861461
0xb006…e64d0x0495…eed9Base$0.10100%payAI225d ago0x081007…21c509
0xb006…e64d0x0495…eed9Base$0.10100%payAI225d ago0xd66785…c008ea
0xb006…e64d0x0495…eed9Base$0.10100%payAI225d ago0xc535e7…773a91
0xb006…e64d0x0495…eed9Base$0.10100%payAI225d ago0xe950da…c6a598
0xb006…e64d0x0495…eed9Base$0.10100%payAI225d ago0x206d5b…9f1a83
0xb006…e64d0x0495…eed9Base$0.10100%payAI225d ago0x03e1f5…8ca585
0xb006…e64d0x0495…eed9Base$0.10100%payAI225d ago0x04c623…b03e1b
0xb006…e64d0x0495…eed9Base$0.10100%payAI225d ago0xa39b03…1b9692
0xb006…e64d0x0495…eed9Base$0.0001100%payAI238d ago0x3102a0…4192c6

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

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

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: 0xb006…e64d

curl -s 'https://api.roundhouseai.io/v0/agents/0xb0060af62779d97016bed22ee5cbb9d65e43e64d'
curl -s 'https://api.roundhouseai.io/v0/entities/0xb0060af62779d97016bed22ee5cbb9d65e43e64d/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. Mint a personal key for $0.01 at GET https://api.roundhouseai.io/v0/test/x402,
or use an organization key from https://roundhouseai.io/dashboard/team.

If you do not have Roundhouse tools or skills installed, read
https://roundhouseai.io/skill.md first — it is the whole procedure.