AgentReport

0xa03a…7be8

0xa03a7c5d7774cce3f3390e679df6c5acd30e7be8Explorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
255
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $0.03 of the $3069.68M Roundhouse has indexed across 1,403,034 wallets — less than 0.0001% of it.

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

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

$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 277d ago
    $0.03
    255 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.00255277d 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 255 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams342d ago0x8f6c5b…174e4f
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams342d ago0x1c0d28…49fb4c
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams342d ago0xcae114…caee1f
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams342d ago0x741de4…172b35
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams342d ago0xea917c…9873f8
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams342d ago0x498fe5…490947
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams342d ago0x347a1e…71759c
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams342d ago0x1db057…b4ef44
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams342d ago0xe50971…7154ba
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams342d ago0x2c77e3…9c303a
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams342d ago0xa4825d…22fe7f
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams342d ago0x64d08f…0f0f80
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams343d ago0xac075e…f74a3c
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams343d ago0x01115c…16afd1
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams343d ago0x3773ff…59e4f4
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams343d ago0xb57bd3…3a2dfb
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams343d ago0x219454…5cddd7
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams343d ago0x458272…afe43e
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams343d ago0xdc69b7…727dec
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams343d ago0x038c92…efcb8a
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams343d ago0x0846a5…7467b6
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams343d ago0x4e3e6e…0ae12e
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams344d ago0x8dcb23…dec2f5
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams344d ago0x5ae11f…6322e3
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams344d ago0x6a4784…32dffd

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

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

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: 0xa03a…7be8

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