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,402,228 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%daydreams348d ago0xb2641d…a8d7be
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams348d ago0xc108c5…df8ff9
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams348d ago0x52329c…157740
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams348d ago0x7821f6…7f633e
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams349d ago0x725216…b91d0c
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams349d ago0xc890cd…242e28
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams349d ago0xdbf2a6…39c0d8
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams349d ago0x2e21d4…8b1489
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams349d ago0x59b73a…c087a6
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams350d ago0x2c200f…5e9a7e
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams350d ago0xa78e26…78a2a2
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams350d ago0x6cbfa1…cf8223
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams350d ago0xcc9cd9…702dac
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams351d ago0xf9e22a…ad1cb2
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams351d ago0xb02b0f…8d2ac0
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams351d ago0x285f53…abbce6
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams351d ago0xae9bc6…613116
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams351d ago0xa30de9…2c4c1d
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams351d ago0x939587…5c3ec7
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams351d ago0x4f8d5f…ba1be0
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams352d ago0x3ae9fa…597728
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams352d ago0x3f384f…b26738
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams352d ago0x84c2f6…a2672d
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams352d ago0xec00ed…7196d1
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams352d ago0xf97672…597563

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.