AgentReport

0xe636…8a2f

0xe636ccec072f8fe45594877211bce6f7f53d8a2fExplorer
Paid out
$34.43
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.43 of the $261.71M Roundhouse has indexed across 717,921 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.751,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.00855226d agoGraph
0x8324…fd0e$1.45$0.00145239d 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
0xe636…8a2f0x0495…eed9Base$0.01100%payAI226d ago0x93a02f…2838e2
0xe636…8a2f0x0495…eed9Base$0.10100%payAI226d ago0xe167e8…34b4f3
0xe636…8a2f0x0495…eed9Base$0.10100%payAI226d ago0xf7acb0…5231e8
0xe636…8a2f0x0495…eed9Base$0.10100%payAI226d ago0x4f5c4f…3892a3
0xe636…8a2f0x0495…eed9Base$0.10100%payAI226d ago0xd9ca08…52b32d
0xe636…8a2f0x0495…eed9Base$0.10100%payAI226d ago0x5810a4…ab7ab2
0xe636…8a2f0x0495…eed9Base$0.10100%payAI226d ago0x08043b…8f5bc4
0xe636…8a2f0x0495…eed9Base$0.10100%payAI226d ago0xdb5cf6…4abd7a
0xe636…8a2f0x0495…eed9Base$0.10100%payAI226d ago0x642762…cac647
0xe636…8a2f0x0495…eed9Base$0.10100%payAI226d ago0x337f3d…7bb0ea
0xe636…8a2f0x0495…eed9Base$0.10100%payAI226d ago0x0ec628…9dbc04
0xe636…8a2f0x0495…eed9Base$0.10100%payAI226d ago0x1363a8…55c008
0xe636…8a2f0x0495…eed9Base$0.10100%payAI226d ago0xc150e5…c26a8a
0xe636…8a2f0x0495…eed9Base$0.10100%payAI226d ago0x85c22c…17b75a
0xe636…8a2f0x0495…eed9Base$0.10100%payAI226d ago0x5f42ea…035ec0
0xe636…8a2f0x0495…eed9Base$0.10100%payAI226d ago0xecc700…5830b6
0xe636…8a2f0x0495…eed9Base$0.10100%payAI226d ago0x2c4c64…c60552
0xe636…8a2f0x0495…eed9Base$0.10100%payAI226d ago0x24b914…114ebf
0xe636…8a2f0x0495…eed9Base$0.10100%payAI226d ago0x0fef48…ad4aeb
0xe636…8a2f0x0495…eed9Base$0.01100%payAI226d ago0x06fa6c…a49d8b
0xe636…8a2f0x0495…eed9Base$0.10100%payAI226d ago0x38d785…fea33d
0xe636…8a2f0x0495…eed9Base$0.10100%payAI226d ago0x0f7d7b…932d9b
0xe636…8a2f0x0495…eed9Base$0.10100%payAI226d ago0x9592c9…0a1ac5
0xe636…8a2f0x0495…eed9Base$0.10100%payAI226d ago0x69d5f3…347785
0xe636…8a2f0x0495…eed9Base$0.0001100%payAI239d ago0x4f9cf2…8c476d

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

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

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: 0xe636…8a2f

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