AgentReport

0x5197…6c8d

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

Paid $0.03 of the $3068.58M Roundhouse has indexed across 1,402,722 wallets — less than 0.0001% of it.

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

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

$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
    257 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.00257277d 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 257 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x5197…6c8d0x6482…b779BaseBase$0.0001100%daydreams353d ago0xefe9cc…055454
0x5197…6c8d0x6482…b779BaseBase$0.0001100%daydreams353d ago0x7e621c…72456b
0x5197…6c8d0x6482…b779BaseBase$0.0001100%daydreams353d ago0x7f5618…e2e246
0x5197…6c8d0x6482…b779BaseBase$0.0001100%daydreams353d ago0x6a9290…c072cc
0x5197…6c8d0x6482…b779BaseBase$0.0001100%daydreams353d ago0x9e5635…cdb164
0x5197…6c8d0x6482…b779BaseBase$0.0001100%daydreams353d ago0xcd308f…249f2a
0x5197…6c8d0x6482…b779BaseBase$0.0001100%daydreams355d ago0x9fd86a…a0bbf6
0x5197…6c8d0x6482…b779BaseBase$0.0001100%daydreams355d ago0x0aed27…d34736
0x5197…6c8d0x6482…b779BaseBase$0.0001100%daydreams355d ago0x420e78…1075f1
0x5197…6c8d0x6482…b779BaseBase$0.0001100%daydreams355d ago0x3c8eea…ccb123
0x5197…6c8d0x6482…b779BaseBase$0.0001100%daydreams355d ago0xa5a5d2…b72925
0x5197…6c8d0x6482…b779BaseBase$0.0001100%daydreams356d ago0x32de38…083c3c
0x5197…6c8d0x6482…b779BaseBase$0.0001100%daydreams356d ago0x94ac08…9bb702
0x5197…6c8d0x6482…b779BaseBase$0.0001100%daydreams357d ago0xc7d170…655645
0x5197…6c8d0x6482…b779BaseBase$0.0001100%daydreams357d ago0xce5ebf…b7e953
0x5197…6c8d0x6482…b779BaseBase$0.0001100%daydreams357d ago0x7bf6e0…d8bc07
0x5197…6c8d0x6482…b779BaseBase$0.0001100%daydreams357d ago0x568d05…8c9b4a
0x5197…6c8d0x6482…b779BaseBase$0.0001100%daydreams357d ago0xd0154c…e066ac
0x5197…6c8d0x6482…b779BaseBase$0.0001100%daydreams358d ago0x583d9a…68993b
0x5197…6c8d0x6482…b779BaseBase$0.0001100%daydreams358d ago0x1a8db2…9b8871
0x5197…6c8d0x6482…b779BaseBase$0.0001100%daydreams358d ago0x0a80bb…b32883
0x5197…6c8d0x6482…b779BaseBase$0.0001100%daydreams359d ago0x3bd577…250699
0x5197…6c8d0x6482…b779BaseBase$0.0001100%daydreams359d ago0x02a8ac…0c99a1
0x5197…6c8d0x6482…b779BaseBase$0.0001100%daydreams359d ago0x1fdd0f…5d5497
0x5197…6c8d0x6482…b779BaseBase$0.0001100%daydreams359d ago0xa24c0a…7f4f18

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

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

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: 0x5197…6c8d

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