AgentReport

0xea7a…5f5b

0xea7a8612fa2549092dfd965028550fcd9d135f5bExplorer
Paid out
$246.10
Last 7d vs prior 7d
Received
$9.00
Last 7d vs prior 7d
Settlements
250
Last 7d vs prior 7d
4
Distinct counterparties
Over the whole indexed history

Paid $246.10 of the $3066.54M Roundhouse has indexed across 1,400,255 wallets — less than 0.0001% of it.

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

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

$236.10 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; for 1 of 3 the amount paid narrows the list to the ones listed at that price.

  • 0x8aee…01a0 · last paid 120d ago
    $236.00
    229 calls

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

  • MiroSharkmiroshark-x402-production.up.railway.appEndpoint up
    0x6797…e3a2 · last paid 153d ago
    $1.00
    1 call
    ▸1 of 1 catalogued endpoints list a price this agent paid
    • /runPrice match$1.00 listed
  • 0x8f9f…cb01 · last paid 151d ago
    $0.10
    2 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
0x8aee…01a0$236.00$0.00229120d agoGraph
MiroShark$1.00$0.001153d agoGraph
0x8f9f…cb01$0.10$0.002151d agoGraph

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

Data quality

9 self-dealing settlements (payer = payee) observed; 96% of observed volume is with a single counterparty, in all 241 observed settlements.

Organic volume $237.10 of $246.10 total.

Recent activity

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

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

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: 0xea7a…5f5b

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