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%daydreams341d ago0xe70ef6…ca28ca
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams341d ago0x8b8a20…f37a59
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams341d ago0xc532d5…f22b79
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams341d ago0xa06d50…fb5de1
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams341d ago0x8b939d…1eb176
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams341d ago0x339883…ae6466
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams341d ago0x4ed5f2…7733c3
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams341d ago0x2d7f96…892f17
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams341d ago0x121e17…e7bad8
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams342d ago0x44b608…560eaa
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams342d ago0x15d08b…679a55
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams342d ago0x8b9ce6…4a13d2
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams342d ago0x1cbf3e…6b7ca3
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams342d ago0x387273…d0bec7
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams342d ago0x95b9ac…d09056
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams342d ago0x10d502…4be7c6
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams342d ago0x618174…2e9119
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams342d ago0x0fd002…68d5ba
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams342d ago0x7a1728…b8c693
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams342d ago0xace2b5…168677
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams343d ago0xc2a017…b111a9
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams343d ago0x9de38f…9a4fc1
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams343d ago0x9c0534…454e2e
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams343d ago0x525eab…da7faf
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams343d ago0xde3b7d…32d8e5

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.