AgentReport

0xc586…8829

0xc586ec94df4496113c54d7ff558f58b8978e8829Explorer
Paid out
$267.75
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 $267.75 of the $3060.46M Roundhouse has indexed across 1,397,861 wallets — less than 0.0001% of it.

Chains (from the recent scan): Ethereum (4) · Base (1)

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

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

  • 0x5c7b…35c5 · last paid 1d ago
    $215.25
    4 calls

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

  • 0x0e3d…7757 · last paid 118d ago
    $52.50
    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
0x5c7b…35c5$215.25$0.0041d agoGraph
0x0e3d…7757$52.50$0.001118d agoGraph

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

Data quality

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

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xc586…88290x5c7b…35c5EthereumEthereum$26.2570%0xd016…b67a1d ago0x38a2fd…98de0c
0xc586…88290x5c7b…35c5EthereumEthereum$21.0070%0xe459…e4de24d ago0xff6da1…ff020a
0xc586…88290x5c7b…35c5EthereumEthereum$52.5070%0xc10a…ae5d82d ago0x13f897…8f3565
0xc586…88290x0e3d…7757BaseBase$52.5070%0x2a28…fc3d118d ago0x6c84d4…c6e0f0
0xc586…88290x5c7b…35c5EthereumEthereum$115.5070%0xd016…b67a221d ago0x05a7a7…8c5c17

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

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

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: 0xc586…8829

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