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%daydreams344d ago0xd8fa13…f934c6
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams344d ago0x4159d7…f8e877
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams344d ago0x382b03…9af2e4
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams344d ago0xf76b53…9efd46
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams344d ago0x133cd8…ca7a98
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams344d ago0xd8f111…eab078
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams344d ago0x669ff6…8ce724
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams344d ago0x5e0641…722d16
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams344d ago0x704e6d…da2509
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams344d ago0xdf00b8…bfadb2
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams344d ago0x00f6b4…3e178e
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams344d ago0xc54d6f…18b07b
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams345d ago0xccd409…2c4b66
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams345d ago0x97aff9…b732db
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams345d ago0x790900…2e7054
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams345d ago0x35d805…01ae35
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams345d ago0x398dc5…8d80f0
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams345d ago0xc8e042…6482bc
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams345d ago0xfbe8d9…1ea522
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams345d ago0x6150c4…fbaa87
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams345d ago0x4b5169…b83772
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams345d ago0x50bd9e…54bdb7
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams345d ago0x6f00ad…c6cf63
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams345d ago0x400dc8…6bc76b
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams346d ago0xb89717…690b97

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.