AgentReport

0x5c1b…738b

0x5c1b73e16a0caed8ea36df12c7c54b2ebc80738bExplorer
Paid out
$19,765.61
Last 7d vs prior 7d
Received
$1,255.93
Last 7d vs prior 7d
Settlements
16
Last 7d vs prior 7d
4
Distinct counterparties
Over the whole indexed history

Paid $19,765.61 of the $846.74M Roundhouse has indexed across 1,330,277 wallets — 0.0023% of it.

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

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%$19,765.61132

$19,765.61 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.

  • 0x3e13…f709 · last paid 442d ago
    $15,372.61
    10 calls

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

  • 0xa6f4…364b · last paid 452d ago
    $4,393.00
    3 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
0x3e13…f709$15,372.61$0.0010442d agoGraph
0xa6f4…364b$4,393.00$0.003452d agoGraph
0x8ec3…9ba6$0.00$1,000.001477d agoGraph
0x48d0…1754$0.00$255.932530d agoGraph

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

Data quality

73% of observed volume is with a single counterparty, in all 16 observed settlements.

Recent activity

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

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

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: 0x5c1b…738b

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