AgentReport

0xe009…691f

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

Paid $34.55 of the $260.82M Roundhouse has indexed across 716,570 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.511,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 22,226 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.20$0.00869225d agoGraph
0x8324…fd0e$1.31$0.00131238d 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 the 1000 most recent settlements scanned (its history is longer than the 2000-row scan cap).

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xe009…691f0x0495…eed9Base$0.10100%payAI225d ago0x52050d…117a50
0xe009…691f0x0495…eed9Base$0.10100%payAI225d ago0x59b702…c16aaf
0xe009…691f0x0495…eed9Base$0.10100%payAI225d ago0x044a3b…f438fd
0xe009…691f0x0495…eed9Base$0.10100%payAI225d ago0x5e11fe…9e83a6
0xe009…691f0x0495…eed9Base$0.10100%payAI225d ago0x92d65c…4f38cb
0xe009…691f0x0495…eed9Base$0.10100%payAI225d ago0xce0fed…2cdf84
0xe009…691f0x0495…eed9Base$0.10100%payAI225d ago0x0d758b…a2b936
0xe009…691f0x0495…eed9Base$0.10100%payAI225d ago0xcd9742…7f38b7
0xe009…691f0x0495…eed9Base$0.10100%payAI225d ago0x27bc1a…c14e30
0xe009…691f0x0495…eed9Base$0.10100%payAI225d ago0x1cab48…959db8
0xe009…691f0x0495…eed9Base$0.10100%payAI225d ago0x16ab6e…338ddb
0xe009…691f0x0495…eed9Base$0.10100%payAI225d ago0xba1226…ee6c7b
0xe009…691f0x0495…eed9Base$0.10100%payAI225d ago0xb88c91…9b4e0c
0xe009…691f0x0495…eed9Base$0.10100%payAI225d ago0x6761d2…09e8db
0xe009…691f0x0495…eed9Base$0.10100%payAI225d ago0x9f3371…684b9f
0xe009…691f0x0495…eed9Base$0.10100%payAI225d ago0x2a90a7…dfa877
0xe009…691f0x0495…eed9Base$0.10100%payAI225d ago0x4fd1dd…dddead
0xe009…691f0x0495…eed9Base$0.10100%payAI225d ago0x1ad31e…808ad2
0xe009…691f0x0495…eed9Base$0.10100%payAI225d ago0x2f2f5d…caa3dd
0xe009…691f0x0495…eed9Base$0.10100%payAI225d ago0xf8e2b6…6bab12
0xe009…691f0x0495…eed9Base$0.10100%payAI225d ago0xb7a897…c87dd5
0xe009…691f0x0495…eed9Base$0.01100%payAI225d ago0xe6fe65…615589
0xe009…691f0x0495…eed9Base$0.01100%payAI225d ago0x65cdfb…c58aa9
0xe009…691f0x0495…eed9Base$0.0001100%payAI238d ago0x06334f…9ef6cd
0xe009…691f0x0495…eed9Base$0.0001100%payAI238d ago0xc02329…572ce2

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

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

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: 0xe009…691f

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