AgentReport

0xce0b…b4b5

0xce0b71687db24b4b934a7a89aa6d9434a4aeb4b5Explorer
Paid out
$200,000.00
Last 7d vs prior 7d
Received
$50,000.00
Last 7d vs prior 7d
Settlements
3
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $200,000.00 of the $847.65M Roundhouse has indexed across 1,331,468 wallets — 0.02% of it.

Chains (from the recent scan): Base (3)

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%$200,000.0021

$200,000.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.

  • 0xbdb3…bbfd · last paid 467d ago
    $200,000.00
    2 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

MayJunJulAugSepOct
LessMore

One square per day; click a day to see its settlements in the ledger.

Frequent counterparties

CounterpartyPaid themReceived backSettlementsLast
0xbdb3…bbfd$200,000.00$0.002467d agoGraph
0xb6ac…f641$0.00$50,000.001481d 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 3 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xce0b…b4b50xbdb3…bbfdBase$140,000.0070%0xe890…f632467d ago0x0c2f8e…cd9b6e
0xce0b…b4b50xbdb3…bbfdBase$60,000.0070%0xe890…f632475d ago0x161aeb…ac922c
0xb6ac…f6410xce0b…b4b5Base$50,000.0070%0xe890…f632481d ago0xdf5fbd…19d6fc

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

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

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: 0xce0b…b4b5

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