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%daydreams337d ago0x48595b…6f32cf
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams337d ago0x435fea…4e8608
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams337d ago0xd559f4…2619d2
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams338d ago0x57ef63…0228af
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams338d ago0x28aef9…16b7a5
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams338d ago0xb2e94a…c2343d
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams338d ago0x89673a…e9d812
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams338d ago0xf0bd52…d416e0
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams338d ago0xa06746…4335f6
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams339d ago0x560c7e…fda4d7
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams339d ago0xd7c0d2…3b0efe
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams340d ago0x4c1be9…e3368d
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams340d ago0xee54e5…43057a
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams340d ago0x1c33a4…25b1ee
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams340d ago0x9af3a1…b6e605
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams340d ago0x649f37…5b58da
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams340d ago0xc4cdb9…4e8484
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams340d ago0xfb29fa…73b425
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams340d ago0x33d7cb…4393d1
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams340d ago0x1ea047…f6be21
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams340d ago0xed3486…173bfd
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams341d ago0x3d257d…c3891b
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams341d ago0xfe067f…34a29f
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams341d ago0x7e3fcd…73ff4f
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams341d ago0x6608bc…e90074

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.