AgentReport

0x1bce…338a

0x1bce60d58b493e3dbb9fa96128c9444c78ef338aExplorer
Paid out
$1.46↓ 100%
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
3↓ 100%
Last 7d vs prior 7d
3
Distinct counterparties
Over the whole indexed history

Paid $1.46 of the $3228.97M Roundhouse has indexed across 1,452,264 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
Not in any catalogue99%$1.4422
Web & Content1%$0.0211

$1.32 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; for 2 of 3 the amount paid narrows the list to the ones listed at that price.

One merchant publishes more endpoints than a single catalogue read returns; its list is partial.

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
0xccc8…15be$1.32$0.001145d agoGraph
0x7dd5…2629$0.12$0.001145d agoGraph
0x8d38…b120$0.02$0.00110d agoGraph

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

Data quality

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

Organic volume $1.46 of $1.46 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x1bce…338a0x8d38…b120BaseBase$0.02100%coinbase10d ago0xf8d0a8…998993
0x1bce…338a0x7dd5…2629BaseBase$0.12100%coinbase145d ago0x898a9f…a0e05c
0x1bce…338a0xccc8…15beBaseBase$1.3270%0xf70d…dbef145d ago0x53b451…5e3fd4

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

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

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: 0x1bce…338a

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