AgentReport

0xbcba…7ecb

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

Paid $0.001096 of the $3206.20M Roundhouse has indexed across 1,440,020 wallets — less than 0.0001% 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
Onchain Data91%$0.00099511
Not in any catalogue9%$0.00010121

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

  • 0x0000…0000api.cleave.fiGas price?Endpoint up
    0x0000…0000 · last paid 67d ago
    $0.000995
    1 call
    ▸1 catalogued endpoints, none priced at an amount this agent paid
  • 0x46f5…a378 · last paid 51d ago
    $0.000101
    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

MayJunJulAugSepOctNov
LessMore

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

Frequent counterparties

CounterpartyPaid themReceived backSettlementsLast
0x0000…0000$0.000995$0.00167d agoGraph
0x46f5…a378$0.000101$0.00251d agoGraph

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

Data quality

91% of observed volume is with a single counterparty, in all 3 observed settlements.

Organic volume $0.001096 of $0.001096 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xbcba…7ecb0x46f5…a378BaseBase$0.000120%Payer-submitted51d ago0xba2201…594030
0xbcba…7ecb0x46f5…a378BaseBase$0.00000120%Payer-submitted53d ago0xee968a…077be0
0xbcba…7ecb0x0000…0000BaseBase$0.00099520%Payer-submitted67d ago0xb9d9b3…299991

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

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

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: 0xbcba…7ecb

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