AgentReport

0x0198…71c2

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

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

$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
    259 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.00259276d 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 259 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams341d ago0xb9fe28…175c72
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams341d ago0xfa46a6…23935b
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams341d ago0x8349f7…d4755b
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams341d ago0xd68f59…e3b63c
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams341d ago0x29e6ac…460320
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams342d ago0xb86884…564dc2
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams342d ago0x99d277…b795ad
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams342d ago0x4efde8…5aa782
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams342d ago0xb0b511…b4a8e0
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams342d ago0x44ca5e…6e0cad
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams342d ago0x985da5…958e42
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams342d ago0xa50abf…d1dd6f
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams342d ago0xfe66f3…fd55dd
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams342d ago0x2f25b3…b0b60d
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams342d ago0x851988…c71b5e
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams342d ago0xd8d4f6…f21822
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams342d ago0xb71caa…9c2172
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams343d ago0x4422f0…3a2c2d
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams343d ago0xe31f22…fc4337
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams343d ago0x9576f3…0b5191
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams343d ago0x74a96c…cfa721
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams343d ago0xbaeb1d…939c5b
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams343d ago0x65bb8e…ef2a3b
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams343d ago0x761eb7…acacdc
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams343d ago0xf3f649…5a8a34

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

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

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: 0x0198…71c2

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