AgentReport

0xe1c9…c401

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

Paid $34.23 of the $261.16M Roundhouse has indexed across 717,066 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.861,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,835 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.42$0.00856225d agoGraph
0x8324…fd0e$1.44$0.00144238d 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
0xe1c9…c4010x0495…eed9Base$0.01100%payAI225d ago0x104901…facecc
0xe1c9…c4010x0495…eed9Base$0.01100%payAI225d ago0x4f66cb…2dd86c
0xe1c9…c4010x0495…eed9Base$0.01100%payAI225d ago0x37f2fb…20a7e5
0xe1c9…c4010x0495…eed9Base$0.01100%payAI225d ago0x36c496…fe79f7
0xe1c9…c4010x0495…eed9Base$0.10100%payAI225d ago0x7bfaf2…5c1afd
0xe1c9…c4010x0495…eed9Base$0.10100%payAI225d ago0x5b8290…de57fb
0xe1c9…c4010x0495…eed9Base$0.10100%payAI225d ago0xd6e3b3…6128bc
0xe1c9…c4010x0495…eed9Base$0.10100%payAI225d ago0xf4ec40…13b545
0xe1c9…c4010x0495…eed9Base$0.10100%payAI225d ago0xe3ad1e…7137ac
0xe1c9…c4010x0495…eed9Base$0.10100%payAI225d ago0xfe08a5…8e0ffd
0xe1c9…c4010x0495…eed9Base$0.10100%payAI225d ago0x027d18…cafe4f
0xe1c9…c4010x0495…eed9Base$0.10100%payAI225d ago0x42af0f…8ea7f5
0xe1c9…c4010x0495…eed9Base$0.10100%payAI225d ago0x8a4b2b…850413
0xe1c9…c4010x0495…eed9Base$0.10100%payAI225d ago0xf3fd10…567e16
0xe1c9…c4010x0495…eed9Base$0.10100%payAI225d ago0x1c2a70…a6fb29
0xe1c9…c4010x0495…eed9Base$0.10100%payAI225d ago0x0b21eb…69da71
0xe1c9…c4010x0495…eed9Base$0.10100%payAI225d ago0xe342ea…5a74f9
0xe1c9…c4010x0495…eed9Base$0.10100%payAI225d ago0xc5c73b…257765
0xe1c9…c4010x0495…eed9Base$0.10100%payAI225d ago0x9d37c5…8b6dc2
0xe1c9…c4010x0495…eed9Base$0.10100%payAI225d ago0x5d6030…a7462d
0xe1c9…c4010x0495…eed9Base$0.10100%payAI225d ago0xf86ca0…6a78ec
0xe1c9…c4010x0495…eed9Base$0.10100%payAI225d ago0x73c467…75f64a
0xe1c9…c4010x0495…eed9Base$0.10100%payAI225d ago0xba469b…c28778
0xe1c9…c4010x0495…eed9Base$0.10100%payAI225d ago0x0e50a7…ef1f09
0xe1c9…c4010x0495…eed9Base$0.10100%payAI225d ago0x8eef75…8903ee

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

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

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: 0xe1c9…c401

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