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%daydreams353d ago0xdf28ed…a06461
0x198e…d17a0x6482…b779BaseBase$0.0001100%daydreams354d ago0xd73f35…82caf6
0x198e…d17a0x6482…b779BaseBase$0.0001100%daydreams355d ago0x0218d7…fb8d63
0x198e…d17a0x6482…b779BaseBase$0.0001100%daydreams355d ago0xb2bb5a…c29bd6
0x198e…d17a0x6482…b779BaseBase$0.0001100%daydreams355d ago0x0b7136…7480ce
0x198e…d17a0x6482…b779BaseBase$0.0001100%daydreams356d ago0xf3cc5f…77c8cb
0x198e…d17a0x6482…b779BaseBase$0.0001100%daydreams356d ago0x95f506…73a904
0x198e…d17a0x6482…b779BaseBase$0.0001100%daydreams356d ago0x703fe9…08a099
0x198e…d17a0x6482…b779BaseBase$0.0001100%daydreams356d ago0x58b22e…48e341
0x198e…d17a0x6482…b779BaseBase$0.0001100%daydreams357d ago0xb929b2…cdcfef
0x198e…d17a0x6482…b779BaseBase$0.0001100%daydreams357d ago0x31a6cd…e65b73
0x198e…d17a0x6482…b779BaseBase$0.0001100%daydreams357d ago0xf55bef…650df9
0x198e…d17a0x6482…b779BaseBase$0.0001100%daydreams358d ago0x750a1c…61fc2c
0x198e…d17a0x6482…b779BaseBase$0.0001100%daydreams358d ago0xd77342…25a8e1
0x198e…d17a0x6482…b779BaseBase$0.0001100%daydreams358d ago0x18bb1f…0a57f2
0x198e…d17a0x6482…b779BaseBase$0.0001100%daydreams359d ago0x31b3f8…88c800
0x198e…d17a0x6482…b779BaseBase$0.0001100%daydreams359d ago0x980303…571181
0x198e…d17a0x6482…b779BaseBase$0.0001100%daydreams359d ago0xf4f821…2feabc
0x198e…d17a0x6482…b779BaseBase$0.0001100%daydreams359d ago0x9a7a07…e0fffd
0x198e…d17a0x6482…b779BaseBase$0.0001100%daydreams360d ago0xddd626…4535ae
0x198e…d17a0x6482…b779BaseBase$0.0001100%daydreams360d ago0xdf012d…523b62
0x198e…d17a0x6482…b779BaseBase$0.0001100%daydreams360d ago0xe0d5d5…093ffc
0x198e…d17a0x6482…b779BaseBase$0.0001100%daydreams361d ago0xd3eaa0…ffbf74
0x198e…d17a0x6482…b779BaseBase$0.0001100%daydreams361d ago0x9dc691…a9ba27
0x198e…d17a0x6482…b779BaseBase$0.0001100%daydreams361d ago0xc16fd5…193814

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.