AgentReport

0xfd53…a3a8

0xfd5318610d84d95af5e52ed2cb2c975e8258a3a8Explorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
264
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 (264)

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

$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
    264 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.00264276d 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 264 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xfd53…a3a80x6482…b779BaseBase$0.0001100%daydreams352d ago0x3c497a…1b062b
0xfd53…a3a80x6482…b779BaseBase$0.0001100%daydreams352d ago0xa59fd2…af3c01
0xfd53…a3a80x6482…b779BaseBase$0.0001100%daydreams352d ago0x687960…862c06
0xfd53…a3a80x6482…b779BaseBase$0.0001100%daydreams352d ago0xc8c3c8…ec4e3e
0xfd53…a3a80x6482…b779BaseBase$0.0001100%daydreams353d ago0x55e332…b56b50
0xfd53…a3a80x6482…b779BaseBase$0.0001100%daydreams353d ago0x6dc8b4…46d249
0xfd53…a3a80x6482…b779BaseBase$0.0001100%daydreams353d ago0x1351c2…0abc6b
0xfd53…a3a80x6482…b779BaseBase$0.0001100%daydreams353d ago0xb54343…b80396
0xfd53…a3a80x6482…b779BaseBase$0.0001100%daydreams353d ago0x958066…d4329c
0xfd53…a3a80x6482…b779BaseBase$0.0001100%daydreams353d ago0x9f577a…afc138
0xfd53…a3a80x6482…b779BaseBase$0.0001100%daydreams353d ago0x4e2128…b5261a
0xfd53…a3a80x6482…b779BaseBase$0.0001100%daydreams354d ago0x0f4bc6…08d8f4
0xfd53…a3a80x6482…b779BaseBase$0.0001100%daydreams355d ago0x9ae4ca…250f79
0xfd53…a3a80x6482…b779BaseBase$0.0001100%daydreams355d ago0xc6bd04…aed9dd
0xfd53…a3a80x6482…b779BaseBase$0.0001100%daydreams355d ago0xa02da4…c2ad2a
0xfd53…a3a80x6482…b779BaseBase$0.0001100%daydreams355d ago0x9b8cc6…c79663
0xfd53…a3a80x6482…b779BaseBase$0.0001100%daydreams356d ago0xe520e2…d43747
0xfd53…a3a80x6482…b779BaseBase$0.0001100%daydreams356d ago0xfa4e36…970f54
0xfd53…a3a80x6482…b779BaseBase$0.0001100%daydreams356d ago0x10657d…2222aa
0xfd53…a3a80x6482…b779BaseBase$0.0001100%daydreams357d ago0xd40b48…0c20d2
0xfd53…a3a80x6482…b779BaseBase$0.0001100%daydreams357d ago0x55f242…f25f49
0xfd53…a3a80x6482…b779BaseBase$0.0001100%daydreams357d ago0xf5db50…533385
0xfd53…a3a80x6482…b779BaseBase$0.0001100%daydreams357d ago0x6d611f…997c19
0xfd53…a3a80x6482…b779BaseBase$0.0001100%daydreams357d ago0x32bbd7…930955
0xfd53…a3a80x6482…b779BaseBase$0.0001100%daydreams358d ago0x613333…b01de9

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

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

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: 0xfd53…a3a8

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