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%daydreams346d ago0x72932e…7d3158
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams346d ago0xf57dd8…e46e4e
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams346d ago0x2abb5c…19c5b3
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams346d ago0x8c9413…c05279
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams346d ago0x186258…877bcf
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams346d ago0xc4cd33…eed5e3
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams346d ago0x61890b…88e2ff
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams346d ago0xc6297b…61572d
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams346d ago0x0d45f0…9ef2d9
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams346d ago0x582393…672ca2
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams346d ago0xb77296…bc9aa4
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams347d ago0xbb99f9…7771ef
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams347d ago0x55a260…59d805
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams347d ago0xf70d53…fff636
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams347d ago0x86d88e…77d99a
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams347d ago0x205998…c7430b
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams347d ago0x1c8b02…b4ecce
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams347d ago0xdf481d…8b6d7f
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams348d ago0x3a0c81…43dd68
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams348d ago0x796b02…2e8540
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams348d ago0x95486e…858883
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams348d ago0x823dd5…a490c4
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams348d ago0xd22095…474244
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams348d ago0x334e7a…314a2c
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams348d ago0x3cee75…26729a

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.