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%daydreams343d ago0x673575…683b6b
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams343d ago0x08749e…f2192b
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams344d ago0x62d1a6…643b10
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams344d ago0x267b58…7837b0
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams344d ago0xe78a05…df00d6
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams344d ago0xbe48b0…8db1ed
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams344d ago0x38fd5d…e69bd3
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams344d ago0xe9c96e…76cf9e
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams344d ago0x27a028…67f986
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams344d ago0xae37d1…5d54ba
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams344d ago0x57333c…bfadc2
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams344d ago0x99fbf2…ce212b
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams344d ago0x321fe5…1003bb
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams344d ago0x46374e…2515e2
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams345d ago0x12d198…e9e4fd
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams345d ago0x6fb6cc…464ff3
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams345d ago0xf2f458…294f5f
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams345d ago0x933c33…d65094
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams345d ago0x5e10fd…710004
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams345d ago0x762ef0…fd35f3
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams345d ago0xbc087b…fedde3
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams345d ago0xb94743…d38ba9
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams345d ago0x3d7ea6…dcb792
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams345d ago0x410be9…5ae2ba
0x0198…71c20x6482…b779BaseBase$0.0001100%daydreams345d ago0x4c3f24…1bfcb2

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.