AgentReport

0xe6d5…6144

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

Paid $34.13 of the $261.45M Roundhouse has indexed across 717,524 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,952 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.00853226d agoGraph
0x8324…fd0e$1.47$0.00147239d 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
0xe6d5…61440x0495…eed9Base$0.01100%payAI226d ago0x164f9e…89d2a3
0xe6d5…61440x0495…eed9Base$0.10100%payAI226d ago0x3fc5fc…844161
0xe6d5…61440x0495…eed9Base$0.10100%payAI226d ago0xd088ad…13a1dc
0xe6d5…61440x0495…eed9Base$0.10100%payAI226d ago0xb1d8c3…1bb471
0xe6d5…61440x0495…eed9Base$0.10100%payAI226d ago0xd46bf6…b3da9a
0xe6d5…61440x0495…eed9Base$0.10100%payAI226d ago0xb167ef…ca7a52
0xe6d5…61440x0495…eed9Base$0.10100%payAI226d ago0xfcddcc…0f9365
0xe6d5…61440x0495…eed9Base$0.10100%payAI226d ago0xaffd00…d3c272
0xe6d5…61440x0495…eed9Base$0.10100%payAI226d ago0xa1e8e4…49e4e0
0xe6d5…61440x0495…eed9Base$0.10100%payAI226d ago0x9100ea…9185ce
0xe6d5…61440x0495…eed9Base$0.10100%payAI226d ago0xa9dda1…f6a577
0xe6d5…61440x0495…eed9Base$0.10100%payAI226d ago0x1b4e9d…9a9fc2
0xe6d5…61440x0495…eed9Base$0.10100%payAI226d ago0xd2139f…8b6536
0xe6d5…61440x0495…eed9Base$0.10100%payAI226d ago0xadd9f5…522924
0xe6d5…61440x0495…eed9Base$0.10100%payAI226d ago0x36b7a5…bc8be9
0xe6d5…61440x0495…eed9Base$0.10100%payAI226d ago0x6747fa…31f7bf
0xe6d5…61440x0495…eed9Base$0.10100%payAI226d ago0x6db819…c6c2e5
0xe6d5…61440x0495…eed9Base$0.10100%payAI226d ago0x4ea409…57fbb5
0xe6d5…61440x0495…eed9Base$0.10100%payAI226d ago0x9879c6…eec70e
0xe6d5…61440x0495…eed9Base$0.10100%payAI226d ago0x7f1ee9…3be27f
0xe6d5…61440x0495…eed9Base$0.10100%payAI226d ago0x2299f3…791522
0xe6d5…61440x0495…eed9Base$0.10100%payAI226d ago0x99d62b…58d988
0xe6d5…61440x0495…eed9Base$0.10100%payAI226d ago0x83c52a…ba4fe0
0xe6d5…61440x0495…eed9Base$0.01100%payAI226d ago0x14a76e…00160a
0xe6d5…61440x0495…eed9Base$0.0001100%payAI238d ago0xc77eba…dd8f5c

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

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

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: 0xe6d5…6144

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