AgentReport

0x2424…ea8e

0x2424b2f5f2c0428ee3e9b3dc637dc3947838ea8eExplorer
Paid out
$2,797.32
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 $2,797.32 of the $3067.43M Roundhouse has indexed across 1,401,742 wallets — less than 0.0001% of it.

Chains (from the recent scan): Ethereum (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
Onchain Data100%$2,797.3221

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; no listed price matches an amount this agent paid, so nothing narrows them.

  • 0x0000…0000api.cleave.fiGas price?Endpoint up
    0x0000…0000 · last paid 99d ago
    $2,797.32
    2 calls
    ▸1 catalogued endpoints, none priced at an amount this agent paid
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
0x0000…0000$2,797.32$0.00299d 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 $2,797.32 of $2,797.32 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x2424…ea8e0x0000…0000EthereumEthereum$402.6450%0x39d6…376599d ago0x27763a…414e5d
0x2424…ea8e0x0000…0000EthereumEthereum$2,394.6870%0x39d6…3765115d ago0x54166a…e2728e

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

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

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: 0x2424…ea8e

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