AgentReport

0xa1a8…1fc3

0xa1a8c69f9ab205557d236c890ec6de40e1a61fc3Explorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
278
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,742 wallets — less than 0.0001% of it.

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

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.032781

$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
    278 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.00278276d 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 278 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams338d ago0x1f7b40…a11f31
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams338d ago0xed0074…96e8e8
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams338d ago0x874d57…dc1df8
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams338d ago0xf807b9…e1a3f6
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams338d ago0x6add6b…190cfe
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams339d ago0x4f6dd2…fe265b
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams339d ago0x8bf326…cb2ef2
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams339d ago0xd507c7…029c81
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams340d ago0x84c1d8…66bbe1
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams340d ago0x276d27…44dfd5
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams340d ago0x439bbc…c1b9b4
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams340d ago0x1c588a…81f7b8
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams340d ago0xc56323…990697
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams340d ago0x94cf67…7e3288
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams340d ago0x87c3f4…dac576
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams340d ago0x8a90b5…27e226
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams340d ago0xad8f68…4434cc
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams340d ago0x1de5b3…9d52fa
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams340d ago0x449d8e…9180d2
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams341d ago0x5c9c55…5717d5
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams341d ago0x79b195…f9103e
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams341d ago0x16fcd5…cdd679
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams341d ago0x26321e…ca7ca6
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams341d ago0x7a26f8…b52108
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams341d ago0xb4dc4c…62b294

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

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

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: 0xa1a8…1fc3

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