AgentReport

0xf84d…e120

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

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

$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
    277 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.00277276d 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 277 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams348d ago0xc94510…7927a5
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams348d ago0x2bfe3b…332598
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams348d ago0x0de05e…794502
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams348d ago0x1825bd…6ccc74
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams348d ago0x2a57f9…7c9111
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams348d ago0xd57175…758198
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams348d ago0x6a89d3…7c6117
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams348d ago0x1b2ec4…a32b99
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams349d ago0x524b38…9f0939
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams349d ago0x8bdc20…3446e9
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams349d ago0x8d04de…cba10a
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams349d ago0x0e59af…8e3b2e
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams349d ago0x335299…723497
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams349d ago0x927071…b7afb1
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams350d ago0xa434bf…99b71a
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams350d ago0x60d901…ab75ba
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams350d ago0xa16e86…94e21d
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams350d ago0xf27570…9d423e
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams351d ago0x932b7c…c0558e
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams351d ago0x9019a7…f204fd
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams351d ago0xa1465a…25981d
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams351d ago0xd9cc74…54de3e
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams351d ago0xafb3b3…ffb503
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams352d ago0x8acde9…77d898
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams352d ago0x5b5587…4da246

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

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

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: 0xf84d…e120

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