AgentReport

0x198e…d17a

0x198eb1e3ba6650ad92aa2b5e46158dc0dd54d17aExplorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
253
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,563 wallets — less than 0.0001% of it.

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

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

$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
    253 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.00253276d 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 253 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x198e…d17a0x6482…b779BaseBase$0.0001100%daydreams346d ago0x39e1bf…1faa0b
0x198e…d17a0x6482…b779BaseBase$0.0001100%daydreams346d ago0xc32a90…d3d5b3
0x198e…d17a0x6482…b779BaseBase$0.0001100%daydreams346d ago0xc0d651…836318
0x198e…d17a0x6482…b779BaseBase$0.0001100%daydreams347d ago0x698a42…5af73b
0x198e…d17a0x6482…b779BaseBase$0.0001100%daydreams347d ago0xdf2f94…9544cc
0x198e…d17a0x6482…b779BaseBase$0.0001100%daydreams347d ago0xfba8fb…543bf3
0x198e…d17a0x6482…b779BaseBase$0.0001100%daydreams347d ago0x68e5cd…cabaef
0x198e…d17a0x6482…b779BaseBase$0.0001100%daydreams347d ago0xa64cf6…1e380e
0x198e…d17a0x6482…b779BaseBase$0.0001100%daydreams347d ago0x865a97…679893
0x198e…d17a0x6482…b779BaseBase$0.0001100%daydreams347d ago0xadd757…450084
0x198e…d17a0x6482…b779BaseBase$0.0001100%daydreams348d ago0xc21cec…7dc424
0x198e…d17a0x6482…b779BaseBase$0.0001100%daydreams348d ago0x1879dc…c3d604
0x198e…d17a0x6482…b779BaseBase$0.0001100%daydreams348d ago0xc2b367…8bc3b8
0x198e…d17a0x6482…b779BaseBase$0.0001100%daydreams348d ago0xffa6e5…adbd1e
0x198e…d17a0x6482…b779BaseBase$0.0001100%daydreams348d ago0x281ec7…19fa97
0x198e…d17a0x6482…b779BaseBase$0.0001100%daydreams348d ago0xfb8319…626cf2
0x198e…d17a0x6482…b779BaseBase$0.0001100%daydreams348d ago0x223631…c83c64
0x198e…d17a0x6482…b779BaseBase$0.0001100%daydreams348d ago0x0975d5…71becc
0x198e…d17a0x6482…b779BaseBase$0.0001100%daydreams348d ago0x99f12a…0be6c6
0x198e…d17a0x6482…b779BaseBase$0.0001100%daydreams348d ago0x2244c4…efe8ff
0x198e…d17a0x6482…b779BaseBase$0.0001100%daydreams348d ago0x8c9eae…06335a
0x198e…d17a0x6482…b779BaseBase$0.0001100%daydreams349d ago0xb6e741…8a8ac2
0x198e…d17a0x6482…b779BaseBase$0.0001100%daydreams349d ago0x4bd6c1…97db2c
0x198e…d17a0x6482…b779BaseBase$0.0001100%daydreams349d ago0x3b486c…4c2f7e
0x198e…d17a0x6482…b779BaseBase$0.0001100%daydreams349d ago0xf03d01…94eef7

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

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

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: 0x198e…d17a

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