AgentReport

0xea6c…640f

0xea6c4ffbf0b707fa3a7fc2a41b735a9c7d9e640fExplorer
Paid out
$170.01
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 $170.01 of the $3067.00M Roundhouse has indexed across 1,401,091 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%$170.0121

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 79d ago
    $170.01
    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$170.01$0.00279d 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 $170.01 of $170.01 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xea6c…640f0x0000…0000EthereumEthereum$95.0970%0x39d6…376579d ago0xa1a09e…cfd104
0xea6c…640f0x0000…0000EthereumEthereum$74.9270%0x39d6…376585d ago0x46d0d4…8f8c16

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

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

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: 0xea6c…640f

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