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%daydreams326d ago0x0ff0a1…45a445
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams326d ago0xd3e400…c70d99
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams326d ago0xc8b1cc…b21488
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams326d ago0x6a6d0e…10971e
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams326d ago0x75fbf6…27e621
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams326d ago0xcfb953…a3e1c7
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams326d ago0x96e8eb…f1fb9d
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams326d ago0xf34b84…468995
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams327d ago0xb1ab5c…8f64d7
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams327d ago0xe0bba0…3f7a17
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams327d ago0x651c91…b2873e
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams327d ago0x304e22…3bc279
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams327d ago0x15ff90…5ee119
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams327d ago0xefc101…6a1eb5
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams328d ago0xcc3e2d…3e2271
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams328d ago0xa1c373…c06534
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams328d ago0x3fe59b…fc6d83
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams328d ago0x6ad7f0…e00af0
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams335d ago0x109061…15e9b5
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams337d ago0xb3edbb…79de60
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams337d ago0xab05dd…0faef9
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams337d ago0x57cdf9…06bcc1
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams337d ago0xe2d9a5…9da2cf
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams338d ago0x03a716…122181
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams338d ago0xf819f7…7b5fc0

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.