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 $3067.84M Roundhouse has indexed across 1,401,919 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%daydreams326d ago0xc25d3b…098b29
0x198e…d17a0x6482…b779BaseBase$0.0001100%daydreams326d ago0xafb70d…751776
0x198e…d17a0x6482…b779BaseBase$0.0001100%daydreams326d ago0xccad3f…bdadc6
0x198e…d17a0x6482…b779BaseBase$0.0001100%daydreams326d ago0x33ebf3…2fee35
0x198e…d17a0x6482…b779BaseBase$0.0001100%daydreams326d ago0xb7df27…0ea98f
0x198e…d17a0x6482…b779BaseBase$0.0001100%daydreams326d ago0xcd0c80…713e98
0x198e…d17a0x6482…b779BaseBase$0.0001100%daydreams327d ago0xd17aac…6fac83
0x198e…d17a0x6482…b779BaseBase$0.0001100%daydreams327d ago0x63bc40…e1cad0
0x198e…d17a0x6482…b779BaseBase$0.0001100%daydreams327d ago0xf72922…fadcf1
0x198e…d17a0x6482…b779BaseBase$0.0001100%daydreams327d ago0xcceec0…af16d6
0x198e…d17a0x6482…b779BaseBase$0.0001100%daydreams327d ago0x3d4121…ef6f50
0x198e…d17a0x6482…b779BaseBase$0.0001100%daydreams327d ago0x974229…1fff64
0x198e…d17a0x6482…b779BaseBase$0.0001100%daydreams327d ago0xb1a6cd…60410b
0x198e…d17a0x6482…b779BaseBase$0.0001100%daydreams327d ago0x8a730d…85bc86
0x198e…d17a0x6482…b779BaseBase$0.0001100%daydreams328d ago0x4890bf…35d99a
0x198e…d17a0x6482…b779BaseBase$0.0001100%daydreams328d ago0xe511a4…9d574e
0x198e…d17a0x6482…b779BaseBase$0.0001100%daydreams328d ago0x7a71ce…83e608
0x198e…d17a0x6482…b779BaseBase$0.0001100%daydreams328d ago0x3e4115…802ae3
0x198e…d17a0x6482…b779BaseBase$0.0001100%daydreams335d ago0x89533b…d707af
0x198e…d17a0x6482…b779BaseBase$0.0001100%daydreams337d ago0x7101e7…edca3d
0x198e…d17a0x6482…b779BaseBase$0.0001100%daydreams337d ago0x1648c7…061cc8
0x198e…d17a0x6482…b779BaseBase$0.0001100%daydreams337d ago0xf1ffd5…acff62
0x198e…d17a0x6482…b779BaseBase$0.0001100%daydreams337d ago0xbcfdf3…5a6a39
0x198e…d17a0x6482…b779BaseBase$0.0001100%daydreams338d ago0x7d350d…560a3f
0x198e…d17a0x6482…b779BaseBase$0.0001100%daydreams338d ago0x42ef46…cae568

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.