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%daydreams323d ago0x227358…afe91d
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams323d ago0x29d0b7…18eaaa
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams324d ago0x852022…0a2864
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams324d ago0xea1054…047c8b
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams324d ago0xb775d9…6a4672
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams324d ago0x8ebff2…2f91ca
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams324d ago0x76bba3…0df73c
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams324d ago0x921edb…c67683
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams324d ago0xfc8482…056462
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams324d ago0x58896a…bcbb9d
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams324d ago0xee5ad3…46cbe8
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams324d ago0xfd0ba7…d8d242
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams324d ago0xd469fc…8cc415
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams325d ago0xda5177…6a9cb5
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams325d ago0x4383ad…13cb34
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams325d ago0x2210b7…d2345d
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams325d ago0x0d3ca7…08eca1
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams325d ago0x2bf65d…bb5c88
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams325d ago0x5652f1…1a6b04
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams325d ago0x3bf56d…db4582
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams325d ago0x17ecc4…02cec3
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams325d ago0xa7a893…a5b27a
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams325d ago0xb764e4…92b40a
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams325d ago0x751476…49e100
0xa1a8…1fc30x6482…b779BaseBase$0.0001100%daydreams326d ago0xa6c04d…e4447c

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.