AgentReport

0x3ba5…dca0

0x3ba52010ebad42c7aef489bd1de7077d71dfdca0Explorer
Paid out
$142.80
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
5
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $142.80 of the $3218.17M Roundhouse has indexed across 1,446,529 wallets — less than 0.0001% of it.

Chains (from the recent scan): Base (1) · Ethereum (4)

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%$142.8052

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

  • 0x5c7b…35c5 · last paid 51d ago
    $79.80
    4 calls

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

  • 0x47c5…4fc3 · last paid 3d ago
    $63.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
0x5c7b…35c5$79.80$0.00451d agoGraph
0x47c5…4fc3$63.00$0.0013d agoGraph

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

Data quality

56% of observed volume is with a single counterparty, in all 5 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x3ba5…dca00x47c5…4fc3BaseBase$63.0070%0x573b…0d283d ago0xc2eae4…fd9fdf
0x3ba5…dca00x5c7b…35c5EthereumEthereum$18.9070%0xe459…e4de51d ago0x9a0395…68a1b3
0x3ba5…dca00x5c7b…35c5EthereumEthereum$31.5070%0xc10a…ae5d143d ago0x3b54d1…0c6680
0x3ba5…dca00x5c7b…35c5EthereumEthereum$25.2070%0xc10a…ae5d156d ago0xa5cfd2…232107
0x3ba5…dca00x5c7b…35c5EthereumEthereum$4.2070%0xd016…b67a202d ago0x311d1b…324c64

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

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

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: 0x3ba5…dca0

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