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%daydreams344d ago0x67f964…af4189
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams344d ago0x60835a…ae18ab
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams344d ago0x63ec95…9912b0
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams344d ago0xbfeca6…023e98
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams344d ago0xc79e88…f7918a
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams344d ago0xc10571…16b760
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams344d ago0xc1dbaf…b83dfa
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams345d ago0x79bb9f…94e5ee
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams345d ago0x4d7be2…9dcdb6
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams345d ago0x3c909f…735970
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams345d ago0x7159b1…639046
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams345d ago0xdbc5c5…bb3fc3
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams345d ago0x1725d8…1bed9d
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams345d ago0x2249e3…67c471
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams345d ago0xaec4ef…f5b954
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams345d ago0x7f7e9d…5c3438
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams345d ago0x36d5e8…e8e629
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams345d ago0x674bd4…9d808f
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams346d ago0xaef7a2…3a4008
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams346d ago0xfb9a1d…454588
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams346d ago0xe5526d…4e7f54
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams346d ago0xc5d7a6…46d965
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams346d ago0xe9608e…b75fb4
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams346d ago0x53b703…696542
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams346d ago0xdbbeac…1eac50

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.