AgentReport

0x408a…d5ef

0x408a41e0e28b7d621e6ddd53cc954e4d550cd5efExplorer
$0.02
Paid out
$0.00
Received
4
Settlements
3
Distinct counterparties
In the 4 settlements scanned

Paid $0.02 of the $840.44M Roundhouse has indexed across 1,315,165 wallets — less than 0.0001% of it.

Counted from this wallet’s own settlements. The index rollup has no row for it yet, which is normal for an address first seen in the last half hour.

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

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
Web & Content63%$0.0111
AI & Media25%$0.00421
Onchain Data13%$0.00211

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 3 of 3 the amount paid narrows the list to the ones listed at that price.

One merchant publishes more endpoints than a single catalogue read returns; its list is partial.

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

Frequent counterparties

CounterpartyPaid themReceived backSettlementsLast
0xabf4…a9d0$0.01$0.0012d agoGraph
0xe903…1abf$0.004$0.0022d agoGraph
0xd161…f1b3$0.002$0.0012d agoGraph

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

Data quality

63% of observed volume is with a single counterparty, in all 4 observed settlements.

Recent activity

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

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

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: 0x408a…d5ef

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