AgentReport

0xdc3e…eb56

0xdc3ec195f52dab20e20fc4eff8294ed01c9aeb56Explorer
Paid out
$1,400.18
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
8
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $1,400.18 of the $3216.76M Roundhouse has indexed across 1,445,459 wallets — less than 0.0001% of it.

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

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%$1,400.1881

$1,400.18 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 23d ago
    $1,400.18
    8 calls

    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$1,400.18$0.00823d 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 8 observed settlements.

Organic volume $1,400.18 of $1,400.18 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xdc3e…eb560x5c7b…35c5EthereumEthereum$159.3170%0xc10a…ae5d23d ago0x5321ee…af1836
0xdc3e…eb560x5c7b…35c5EthereumEthereum$118.3470%0xc10a…ae5d51d ago0xaee527…d606d6
0xdc3e…eb560x5c7b…35c5EthereumEthereum$344.4570%0xd016…b67a69d ago0xe79f5b…78886b
0xdc3e…eb560x5c7b…35c5EthereumEthereum$296.7870%0xc10a…ae5d81d ago0x9b60b9…4ba977
0xdc3e…eb560x5c7b…35c5EthereumEthereum$79.7470%0xc10a…ae5d106d ago0xacb409…89096a
0xdc3e…eb560x5c7b…35c5EthereumEthereum$189.6070%0x8819…8d5e139d ago0x2bcd5a…fcb8c9
0xdc3e…eb560x5c7b…35c5EthereumEthereum$139.8170%0xe459…e4de163d ago0xb1576b…f91609
0xdc3e…eb560x5c7b…35c5EthereumEthereum$72.1570%0xd016…b67a200d ago0xdbc764…fe1171

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

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

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: 0xdc3e…eb56

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