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%daydreams351d ago0xe03e2f…c65ad0
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams351d ago0x64f3e0…74c0a6
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams351d ago0x531ca0…7f9197
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams351d ago0xb93557…26946f
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams351d ago0x8bbd72…3f5644
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams352d ago0x613745…e02efe
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams352d ago0xa1b9f9…12bfc5
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams352d ago0xefc8af…1be5cd
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams352d ago0xbf2671…510447
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams352d ago0x491da5…4d3bbc
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams352d ago0xc1e489…3df286
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams352d ago0x316bc8…90a17b
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams352d ago0xec7ab9…82bf8c
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams352d ago0x367879…6f9108
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams352d ago0xb5dbc2…c164f2
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams353d ago0xd6a70e…e9d35c
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams353d ago0x21a82a…a308c7
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams353d ago0x1602ee…c57fc8
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams353d ago0xecd4b8…ab67bd
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams353d ago0xf024d1…4bf47f
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams354d ago0x8e8b38…f61fe2
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams354d ago0x0b2884…8cd897
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams354d ago0xeb76e9…c75a29
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams355d ago0xf1e6eb…e1d089
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams355d ago0xebc2d1…28fb87

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.