AgentReport

0x5a2c…c493

0x5a2c16e4da582cdd553b08d6f6e698b3faf5c493Explorer
Paid out
$468.56
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
2
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $468.56 of $3.31B indexed (less than 0.0001%).

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
Not in any catalogue100%$468.5622

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

  • 0x484a…1ca7 · last paid 261d ago
    $318.56
    1 call

    This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.

  • 0xba47…eb6f · last paid 299d ago
    $150.00
    1 call

    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
0x484a…1ca7$318.56$0.001261d agoGraph
0xba47…eb6f$150.00$0.001299d agoGraph

Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.

Data quality

68% of volume with one counterparty.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x5a2c…c4930x484a…1ca7EthereumEthereum$318.5670%0xbfa1…1b33261d ago0xedc627…82feab
0x5a2c…c4930xba47…eb6fEthereumEthereum$150.0070%0xbfa1…1b33299d ago0xd9afe9…07f3ec

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

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

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: 0x5a2c…c493

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