AgentReport

0xa5fa…cae8

0xa5fa8bc4fd1bdddb39004bb9482ade1b58f8cae8Explorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
277
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $0.03 of the $3067.43M Roundhouse has indexed across 1,401,367 wallets — less than 0.0001% of it.

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

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

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

  • 0x6482…b779 · last paid 276d ago
    $0.03
    277 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
0x6482…b779$0.03$0.00277276d agoGraph

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

Data quality

100% of observed volume is with a single counterparty; all observed volume is with one counterparty, in all 277 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams355d ago0x0bc65f…164d4d
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams355d ago0x1c98f4…d25070
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams355d ago0xb6c25b…3f0cd5
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams356d ago0xef4ab5…0ac370
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams356d ago0x4cd5cd…99b079
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams356d ago0x38aec3…649196
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams356d ago0x3bbe6c…c97c0d
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams357d ago0xf835e2…4d2ac5
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams357d ago0x4e12b1…13e736
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams357d ago0x0c5302…e5d527
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams357d ago0x1ddd9b…f32d9f
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams357d ago0xc1c85f…7ec2e6
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams357d ago0x68436b…f8e922
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams358d ago0x93870a…efb2d3
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams358d ago0xc15527…8bfe97
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams358d ago0xaece73…577b94
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams358d ago0xcdf4be…e583b4
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams358d ago0x1885fa…cc3287
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams359d ago0xa6d005…94d010
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams359d ago0xea79b1…3bf6b4
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams359d ago0x1ebd44…1b5151
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams359d ago0x76792d…574675
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams360d ago0x3edc77…e57a5b
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams361d ago0x6add0d…f32998
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams361d ago0x102f23…1a9fc3

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

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

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: 0xa5fa…cae8

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