AgentReport

0xe495…ab0f

0xe495c2ebbc7ade9f1d2866ffb71282901adbab0fExplorer
Paid out
$0.83
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
834
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

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

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

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%$0.838342

$0.83 went to wallets that publish no endpoint in any catalogue we crawl — spend we can see and cannot describe.

Services it paid

A settlement carries the payee and the amount, never the URL. These are the endpoints each payee publishes; no listed price matches an amount this agent paid, so nothing narrows them.

  • 0xfe80…47ee · last paid 37d ago
    $0.71
    711 calls

    This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.

  • 0x9c95…e299 · last paid 76d ago
    $0.12
    123 calls

    This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.

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
0xfe80…47ee$0.71$0.0071137d agoGraph
0x9c95…e299$0.12$0.0012376d agoGraph

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

Data quality

85% of observed volume is with a single counterparty, in all 834 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xe495…ab0f0xfe80…47eeBaseBase$0.001100%fluxa66d ago0x647219…1800da
0xe495…ab0f0xfe80…47eeBaseBase$0.001100%fluxa66d ago0x6346d0…145716
0xe495…ab0f0xfe80…47eeBaseBase$0.001100%fluxa66d ago0x8ec2e2…20edc5
0xe495…ab0f0xfe80…47eeBaseBase$0.001100%fluxa66d ago0x871f14…a72ae1
0xe495…ab0f0xfe80…47eeBaseBase$0.001100%fluxa66d ago0x26fbc3…9fbc5f
0xe495…ab0f0xfe80…47eeBaseBase$0.001100%fluxa66d ago0x3f0e48…a9a3d9
0xe495…ab0f0xfe80…47eeBaseBase$0.001100%fluxa66d ago0xa4bd31…be9740
0xe495…ab0f0xfe80…47eeBaseBase$0.001100%fluxa66d ago0xd91d19…9259de
0xe495…ab0f0xfe80…47eeBaseBase$0.001100%fluxa66d ago0x1d4df8…5d052a
0xe495…ab0f0xfe80…47eeBaseBase$0.001100%fluxa66d ago0xdc94dc…620618
0xe495…ab0f0xfe80…47eeBaseBase$0.001100%fluxa66d ago0x8094dd…2e42c5
0xe495…ab0f0xfe80…47eeBaseBase$0.001100%fluxa66d ago0xb4f49b…bc43de
0xe495…ab0f0xfe80…47eeBaseBase$0.001100%fluxa66d ago0x49ab88…7ada54
0xe495…ab0f0xfe80…47eeBaseBase$0.001100%fluxa66d ago0x8c661e…be890e
0xe495…ab0f0xfe80…47eeBaseBase$0.001100%fluxa66d ago0x81f923…a66e86
0xe495…ab0f0xfe80…47eeBaseBase$0.001100%fluxa66d ago0x872810…9d0eca
0xe495…ab0f0xfe80…47eeBaseBase$0.001100%fluxa66d ago0xb4f4cb…01f57d
0xe495…ab0f0xfe80…47eeBaseBase$0.001100%fluxa66d ago0x1e2d42…138ab7
0xe495…ab0f0xfe80…47eeBaseBase$0.001100%fluxa66d ago0xf5b9ff…4d3524
0xe495…ab0f0xfe80…47eeBaseBase$0.001100%fluxa66d ago0x7a5242…2e4519
0xe495…ab0f0xfe80…47eeBaseBase$0.001100%fluxa66d ago0x8a7169…2e57dc
0xe495…ab0f0xfe80…47eeBaseBase$0.001100%fluxa66d ago0xae99e5…7be2b1
0xe495…ab0f0xfe80…47eeBaseBase$0.001100%fluxa66d ago0x3e40b0…d0ed03
0xe495…ab0f0xfe80…47eeBaseBase$0.001100%fluxa66d ago0x512d35…2910d1
0xe495…ab0f0xfe80…47eeBaseBase$0.001100%fluxa66d ago0x7bde32…8cf378

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

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

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: 0xe495…ab0f

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