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%daydreams337d ago0x8ebff6…fb24a6
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams337d ago0xfead42…a9c331
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams338d ago0x41f0a7…e60946
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams338d ago0x5aff6d…1b9fdb
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams338d ago0x093e32…467bc8
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams338d ago0x71fd02…0ff77b
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams338d ago0x693929…806a59
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams338d ago0xbe159c…edb765
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams338d ago0x221052…0f3bba
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams339d ago0x0ae213…9eb204
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams339d ago0xd3b482…e515c3
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams339d ago0xe1b021…5ef3e0
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams340d ago0x56e4f9…bda03f
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams340d ago0x945308…305f25
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams340d ago0x429d15…a7d3b7
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams340d ago0x03bde5…640552
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams340d ago0xb12d20…aa71cf
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams340d ago0x5b0b9c…cdd7f9
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams340d ago0x60b65e…e25f9e
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams340d ago0x033e04…e68547
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams340d ago0x2b0aa5…800f36
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams340d ago0x05a4e9…91b88a
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams340d ago0xd60cbb…8f0d64
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams341d ago0x9fb6de…5f9c07
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams341d ago0x787801…164ee3

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.