AgentReport

0xee30…2f9c

0xee3067051991ce23b76a758a553ea9553a422f9cExplorer
Paid out
$24.15
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
4
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $24.15 of the $3218.94M Roundhouse has indexed across 1,447,303 wallets — less than 0.0001% of it.

Whole-history totals from the index rollup, which can be up to 30 minutes behind.

Chains (from the recent scan): Ethereum (4)

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

$24.15 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.

  • 0x5c7b…35c5 · last paid 2d ago
    $24.15
    4 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
0x5c7b…35c5$24.15$0.0042d 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 4 observed settlements.

Organic volume $24.15 of $24.15 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xee30…2f9c0x5c7b…35c5EthereumEthereum$10.5070%0xc10a…ae5d2d ago0xa407f3…b20e3d
0xee30…2f9c0x5c7b…35c5EthereumEthereum$10.5070%0xe459…e4de48d ago0xaee646…3c96b4
0xee30…2f9c0x5c7b…35c5EthereumEthereum$2.1070%0xe459…e4de100d ago0xe46bfc…71fda0
0xee30…2f9c0x5c7b…35c5EthereumEthereum$1.0550%0xe459…e4de166d ago0x5b7fd8…97f688

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

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

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: 0xee30…2f9c

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