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 $3070.29M Roundhouse has indexed across 1,403,290 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%daydreams353d ago0x6bb0ed…96b31b
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams353d ago0xce0c9d…ffb983
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams353d ago0x8a43cd…60eaff
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams353d ago0x4c04d4…4cd123
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams353d ago0x3ae49f…580669
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams354d ago0x190c90…83083a
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams355d ago0xc7181b…2a05c1
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams355d ago0x494243…91cc69
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams356d ago0x441eb5…2d55c3
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams356d ago0x1a0ec6…801f70
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams356d ago0x2204f2…6d1f4c
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams356d ago0x4c9617…271ecd
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams356d ago0xbbc1ad…51b48a
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams356d ago0xc15ad5…50b01f
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams357d ago0x8f5e67…9a98c1
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams357d ago0x58c973…5bcef4
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams358d ago0x79ed74…0a3c59
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams358d ago0x514d70…c208a1
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams358d ago0xc51ccd…b58f5e
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams359d ago0x2cc75f…967004
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams359d ago0x47cd9f…417f56
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams359d ago0xf03def…48d316
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams359d ago0x201d8a…254770
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams360d ago0xfc3839…121c28
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams360d ago0x9af705…54e076

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.