AgentReport

0xd5a1…408b

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

Paid $123.41 of the $846.98M Roundhouse has indexed across 1,330,524 wallets — less than 0.0001% of it.

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

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%$123.4122

$123.41 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.

  • 0x6b44…485f · last paid 417d ago
    $116.38
    1 call

    This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.

  • 0xba8d…cecc · last paid 519d ago
    $7.03
    1 call

    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

MayJunJulAugSepOct
LessMore

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

Frequent counterparties

CounterpartyPaid themReceived backSettlementsLast
0x6b44…485f$116.38$0.001417d agoGraph
0xba8d…cecc$7.03$0.001519d agoGraph

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

Data quality

94% of observed volume is with a single counterparty, in all 2 observed settlements.

Organic volume $123.41 of $123.41 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xd5a1…408b0x6b44…485fBase$116.3870%0xe890…f632417d ago0x31eaa9…f921a3
0xd5a1…408b0xba8d…ceccBase$7.0370%0xe890…f632519d ago0x5e52bd…2e17aa

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

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

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: 0xd5a1…408b

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