AgentReport

0x222a…a5e5

0x222a088ad24ec3c8aa7713855ea896a48615a5e5Explorer
$74,974.42
Paid out
$0.00
Received
3
Settlements
1
Distinct counterparties
Over the whole indexed history

Paid $74,974.42 of the $3059.45M Roundhouse has indexed across 1,397,037 wallets — 0.0025% of it.

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

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%$74,974.4231

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 30d ago
    $74,974.42
    3 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…

Activity

MayJunJulAugSepOctNov
LessMore

One square per day; click a day to see its settlements in the ledger.

Frequent counterparties

CounterpartyPaid themReceived backSettlementsLast
0x0000…0000$74,974.42$0.00330d 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 3 observed settlements.

Organic volume $74,974.42 of $74,974.42 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x222a…a5e50x0000…0000EthereumEthereum$24,985.3470%0xd813…826630d ago0x227907…82f618
0x222a…a5e50x0000…0000EthereumEthereum$24,994.2470%0xd813…826630d ago0xb819a6…8f94a3
0x222a…a5e50x0000…0000EthereumEthereum$24,994.8470%0xd813…826630d ago0x8d3c32…e17c48

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

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

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: 0x222a…a5e5

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