AgentReport

0x0495…eed9

0x0495d60c927b97d67d5018c6aa65c9b2bebaeed9Explorer
Paid out
$33.03
Last 7d vs prior 7d
Received
$27,192.71
Last 7d vs prior 7d
Settlements
29716599
Last 7d vs prior 7d
4482
Distinct counterparties
Over the whole indexed history

Paid $33.03 of the $3059.45M Roundhouse has indexed across 1,397,164 wallets — less than 0.0001% of it.

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

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 catalogue97%$9.949813
Web & Content2%$0.25152
Location & Weather<1%$0.0441

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

Folded from this wallet's 2,000 most recent settlements of 29,716,599 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. 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…

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
0x8324…fd0e$9.68$0.00968263d agoGraph
0x25f6…1b57$0.00$1.4414417d agoGraph
0x3ede…d839$0.00$1.4014150d agoGraph
0x9683…22cc$0.00$0.5923240d agoGraph
0x9cc4…b176$0.00$0.2516139d agoGraph
0x7d9d…405d$0.24$0.0014243d agoGraph
0x9520…556a$0.00$0.2020117d agoGraph
0x4e2e…e3e7$0.20$0.001258d agoGraph

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

Data quality

Not enough of this address's history was examined to assess it: self_dealing and counterparty_concentration and single_counterparty were computed over the 2000 most recent settlements scanned (its history is longer than the 2000-row scan cap), so nothing found there rules anything out. This is an incomplete check, not a clean record.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x25f6…1b570x0495…eed9BaseBase$0.01100%payAI33d ago0x513ddc…a293b6
0x25f6…1b570x0495…eed9BaseBase$0.01100%payAI34d ago0x62cdf4…eead9f
0x25f6…1b570x0495…eed9BaseBase$0.01100%payAI35d ago0xfc9a5e…300233
0x25f6…1b570x0495…eed9BaseBase$0.01100%payAI36d ago0xc7a570…e0dbec
0x25f6…1b570x0495…eed9BaseBase$0.01100%payAI37d ago0xc656c3…c855f9
0x25f6…1b570x0495…eed9BaseBase$0.01100%payAI38d ago0x077bf1…cd85ac
0x25f6…1b570x0495…eed9BaseBase$0.01100%payAI39d ago0x68b884…c69e74
0x25f6…1b570x0495…eed9BaseBase$0.01100%payAI40d ago0x46d031…a6699d
0x25f6…1b570x0495…eed9BaseBase$0.01100%payAI41d ago0xa6d6e5…cf7ca7
0x25f6…1b570x0495…eed9BaseBase$0.01100%payAI42d ago0x080b46…62dc01
0x25f6…1b570x0495…eed9BaseBase$0.01100%payAI43d ago0xbc0450…de8c8b
0x25f6…1b570x0495…eed9BaseBase$0.01100%payAI44d ago0xbc5fe9…b6e0fe
0x25f6…1b570x0495…eed9BaseBase$0.01100%payAI45d ago0x88ddb0…a70847
0x25f6…1b570x0495…eed9BaseBase$0.01100%payAI46d ago0xd40a15…4382bc
0x25f6…1b570x0495…eed9BaseBase$0.01100%payAI47d ago0x7dca33…bf7971
0x25f6…1b570x0495…eed9BaseBase$0.01100%payAI48d ago0x8b18c3…282a80
0x25f6…1b570x0495…eed9BaseBase$0.01100%payAI49d ago0x3e5855…23c817
0x25f6…1b570x0495…eed9BaseBase$0.01100%payAI50d ago0x5ac68b…c22ff1
0x25f6…1b570x0495…eed9BaseBase$0.01100%payAI51d ago0x7d1c82…eaeca6
0x25f6…1b570x0495…eed9BaseBase$0.01100%payAI52d ago0x722b81…db22c2
0x25f6…1b570x0495…eed9BaseBase$0.01100%payAI53d ago0x95b1a0…0c71f5
0x25f6…1b570x0495…eed9BaseBase$0.01100%payAI54d ago0xb032ef…f51363
0x25f6…1b570x0495…eed9BaseBase$0.01100%payAI55d ago0x80c36a…acea20
0x25f6…1b570x0495…eed9BaseBase$0.01100%payAI56d ago0xd2cb3f…bec55a
0x25f6…1b570x0495…eed9BaseBase$0.01100%payAI57d ago0xf72cca…32bba6

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

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

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: 0x0495…eed9

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