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.43M Roundhouse has indexed across 1,401,742 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%daydreams325d ago0x07450d…9eccdd
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams326d ago0x9b27da…8a5eee
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams326d ago0x3db325…515664
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams326d ago0x4dfea4…cede1f
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams326d ago0x556e4d…5098ec
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams326d ago0xa3e5ef…b49ece
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams326d ago0x0ccec2…69587a
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams326d ago0x051f77…38daa4
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams326d ago0x606047…2cd73c
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams326d ago0xba756b…8014e9
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams326d ago0x82465e…f0bfeb
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams327d ago0xf446ef…4a69cc
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams327d ago0x9fc2a4…d99697
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams327d ago0x0c223f…13232e
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams327d ago0xfb27a6…e461d6
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams327d ago0x882c5a…b9669f
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams327d ago0x6252a3…f0f176
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams327d ago0xb2df28…51869c
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams327d ago0xcd5d61…9e1ec9
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams328d ago0x0fc2af…b5656c
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams328d ago0x1e772a…99d00a
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams328d ago0xa28bd7…99669f
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams335d ago0x76d650…d53749
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams337d ago0xc278e9…4bb782
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams337d ago0xc6c733…977661

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.