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.00M Roundhouse has indexed across 1,400,982 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%daydreams323d ago0xed9357…e2eeff
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams323d ago0x86a0a1…5d6a0d
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams323d ago0xd4d269…a2804c
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams323d ago0x37917d…dc7c64
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams323d ago0x7a6948…e4688b
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams323d ago0x033479…c00076
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams324d ago0x217c31…739c7c
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams324d ago0x860762…10dd3d
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams324d ago0x5075b6…103f73
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams324d ago0x35fc57…4c1a58
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams324d ago0x9b905a…568b30
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams324d ago0x45bdf2…092931
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams324d ago0x3ab32b…fa7a33
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams324d ago0x204cab…b4b8c3
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams324d ago0x92d498…3cf1f7
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams324d ago0xe622aa…9ec2c2
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams324d ago0x9a2652…12fe07
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams325d ago0xc887de…ddea3d
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams325d ago0x4fe4ad…6f67b0
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams325d ago0x597fcd…aa7011
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams325d ago0xb7b870…ad910b
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams325d ago0x7dd490…5ad880
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams325d ago0xb8819a…b226d7
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams325d ago0x9356ef…e9b0c7
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams325d ago0x1f23b3…111c5f

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.