AgentReport

0x4a2a…f08c

0x4a2a7717dc05baffbea461f4c8a41dd11ecbf08cExplorer
Paid out
$1,144.00
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 $1,144.00 of the $3066.17M Roundhouse has indexed across 1,400,092 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%$1,144.0021

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 70d ago
    $1,144.00
    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$1,144.00$0.00270d 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 $1,144.00 of $1,144.00 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x4a2a…f08c0x0000…0000EthereumEthereum$1,044.0070%0x39d6…376570d ago0x41adf0…21df44
0x4a2a…f08c0x0000…0000EthereumEthereum$100.0070%0xc4d1…14a085d ago0x4525e1…efc379

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

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

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: 0x4a2a…f08c

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