AgentReport

0xd260…d7b9

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

Paid $840.00 of the $3063.39M Roundhouse has indexed across 1,398,970 wallets — less than 0.0001% of it.

Chains (from the recent scan): Ethereum (6) · 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%$840.0072

$840.00 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 150d ago
    $735.00
    6 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 158d ago
    $105.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
0x5c7b…35c5$735.00$0.006150d agoGraph
0x0e3d…7757$105.00$0.001158d agoGraph

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

Data quality

88% of observed volume is with a single counterparty, in all 7 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xd260…d7b90x5c7b…35c5EthereumEthereum$105.0070%0xd016…b67a150d ago0x4b5841…023411
0xd260…d7b90x0e3d…7757BaseBase$105.0070%0xbe1f…63c9158d ago0x8a5490…82a221
0xd260…d7b90x5c7b…35c5EthereumEthereum$105.0070%0xc10a…ae5d170d ago0xe2d9a5…a7542f
0xd260…d7b90x5c7b…35c5EthereumEthereum$105.0070%0xe0df…59a1182d ago0x9a56fe…8b0383
0xd260…d7b90x5c7b…35c5EthereumEthereum$126.0070%0xe459…e4de189d ago0xa9bf90…2144a3
0xd260…d7b90x5c7b…35c5EthereumEthereum$189.0070%0xd016…b67a203d ago0x891638…2399fd
0xd260…d7b90x5c7b…35c5EthereumEthereum$105.0070%0xc10a…ae5d211d ago0x9b8add…eb443d

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

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

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: 0xd260…d7b9

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