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,401,091 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%daydreams343d ago0x8cfc22…95b0f1
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams343d ago0xc7a3db…786836
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams343d ago0x5e64fb…b5783c
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams343d ago0x0ebcd6…5ddd97
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams343d ago0xe760fb…bfcf4d
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams343d ago0x8a67ac…e7ca72
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams343d ago0x62a802…72888f
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams343d ago0x66c483…a443d4
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams343d ago0xd3f8d5…482aaa
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams343d ago0xd4b07b…b9f0a6
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams344d ago0xed7021…d19c3e
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams344d ago0x746d55…1f1212
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams344d ago0x0cb01e…f762f9
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams344d ago0x6ed45f…a3efb9
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams344d ago0xaadc06…8b153e
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams344d ago0x42c5f5…a25867
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams344d ago0x7e7602…792fe6
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams344d ago0x8e6fb0…dc6009
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams344d ago0xd924e3…0e3e31
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams344d ago0x9d4825…4f7bae
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams344d ago0x063a85…a47d07
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams345d ago0x4fda08…04e888
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams345d ago0xc1ddbd…e682bb
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams345d ago0x6b3ecf…cf7f35
0xa5fa…cae80x6482…b779BaseBase$0.0001100%daydreams345d ago0xc96489…9a02cc

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.