AgentReport

0x4e65…5dfb

0x4e65539bb5f893ccd2b71d3d807b5112e1b85dfbExplorer
Paid out
$6,673.78
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
2
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $6,673.78 of the $3059.45M Roundhouse has indexed across 1,397,037 wallets — 0.0002% of it.

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

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%$6,673.7821

$6,673.78 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.

  • 0x09ae…ec64 · last paid 12h ago
    $6,673.78
    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
0x09ae…ec64$6,673.78$0.00212h agoGraph

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

Data quality

100% of observed volume is with a single counterparty; all observed volume is with one counterparty, in all 2 observed settlements.

Organic volume $6,673.78 of $6,673.78 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x4e65…5dfb0x09ae…ec64BaseBase$1,370.7570%0xc99d…a8f412h ago0x2a84cd…b7366f
0x4e65…5dfb0x09ae…ec64BaseBase$5,303.0370%0x07ae…0e6732d ago0x8956b8…3567a4

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

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

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: 0x4e65…5dfb

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