AgentReport

0xcb7f…bdf6

0xcb7f61880d28abbc407de9a2b7d694f1af83bdf6Explorer
Paid out
$2,456.74
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 $2,456.74 of the $3063.39M Roundhouse has indexed across 1,398,970 wallets — less than 0.0001% of it.

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

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%$2,456.7472

$2,456.74 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.

  • 0xccac…c36d · last paid 85d ago
    $1,706.74
    6 calls

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

  • 0xd40a…3166 · last paid 51d ago
    $750.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
0xccac…c36d$1,706.74$0.00685d agoGraph
0xd40a…3166$750.00$0.00151d agoGraph

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

Data quality

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

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xcb7f…bdf60xd40a…3166EthereumEthereum$750.0070%0x6757…5e1b51d ago0x8398ea…e11795
0xcb7f…bdf60xccac…c36dEthereumEthereum$586.6270%0x6757…5e1b85d ago0x012baf…583540
0xcb7f…bdf60xccac…c36dEthereumEthereum$200.0070%0x6757…5e1b154d ago0xbf6731…1a11da
0xcb7f…bdf60xccac…c36dEthereumEthereum$332.3570%0x6757…5e1b185d ago0x1dee12…092681
0xcb7f…bdf60xccac…c36dEthereumEthereum$100.0070%0x6757…5e1b206d ago0x6218bd…f4c121
0xcb7f…bdf60xccac…c36dEthereumEthereum$362.7770%0x6757…5e1b210d ago0x8685cd…e970f5
0xcb7f…bdf60xccac…c36dEthereumEthereum$125.0070%0x6757…5e1b229d ago0x1cea2c…a877d0

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

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

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: 0xcb7f…bdf6

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