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%daydreams349d ago0xf4c7d9…70cafe
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams349d ago0x488493…40756b
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams350d ago0x56927e…b0ffbb
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams350d ago0x245c2e…19805c
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams350d ago0x559013…c7d17a
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams350d ago0xcf6284…53c044
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams350d ago0x6e4626…6248bd
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams351d ago0xf1ba13…29f57d
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams351d ago0x52e17b…34a3a6
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams351d ago0x769ac7…598211
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams351d ago0x5febde…5cf89e
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams351d ago0x6338be…44b940
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams352d ago0x09960b…ff8b8d
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams352d ago0xfbf32a…eace73
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams352d ago0x462982…9edcbd
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams352d ago0x1fa206…a13f58
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams352d ago0x8e4435…18b30f
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams352d ago0x8aa43d…7d0fa8
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams352d ago0x18ebc0…51e214
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams352d ago0xc19a5b…43f420
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams352d ago0xe2c04e…bcbb29
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams352d ago0x8a189e…472642
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams353d ago0x54491a…6d7c9d
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams353d ago0xed0ffc…d756b9
0xa03a…7be80x6482…b779BaseBase$0.0001100%daydreams353d ago0xab01a9…5264ba

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.