AgentReport

0xf59b…5428

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

Paid $57.31 of the $3059.45M Roundhouse has indexed across 1,397,164 wallets — less than 0.0001% of it.

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

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%$57.3152

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

  • blockmachineblockmachine.ioEndpoint up
    0x5138…c14d · last paid 78d ago
    $40.00
    4 calls
    ▸1 catalogued endpoints, none priced at an amount this agent paid
  • 0x7356…8e55 · last paid 77d ago
    $17.31
    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
0x5138…c14d$40.00$0.00478d agoGraph
0x7356…8e55$17.31$0.00177d agoGraph

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

Data quality

70% of observed volume is with a single counterparty, in all 5 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xf59b…54280x7356…8e55EthereumEthereum$17.3170%0x027d…f07d77d ago0x96c41d…877cc4
0xf59b…54280x5138…c14dEthereumEthereum$3.0070%0x027d…f07d78d ago0x8d608d…fe8c54
0xf59b…54280x5138…c14dEthereumEthereum$3.0070%0x027d…f07d79d ago0x7622fe…07a9a2
0xf59b…54280x5138…c14dEthereumEthereum$9.0070%0x027d…f07d79d ago0x01c704…1ce1b2
0xf59b…54280x5138…c14dEthereumEthereum$25.0070%0x027d…f07d81d ago0x0498dc…1671e8

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

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

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: 0xf59b…5428

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