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%daydreams323d ago0x5fb507…475223
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams323d ago0xf69d86…132fed
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams323d ago0x39c0f2…4cc616
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams323d ago0x1fcaa4…730a25
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams323d ago0xefe270…d19f20
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams324d ago0x723520…062e72
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams324d ago0x22cf81…bbc011
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams324d ago0xdab70b…3bddb4
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams324d ago0x48303d…493dde
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams324d ago0x4285d8…f69963
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams324d ago0xaa918d…bda7e0
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams324d ago0x26e17c…8f3f8d
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams324d ago0x752cca…88781b
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams324d ago0x4339dd…696e0a
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams324d ago0x72b75d…3ae7e5
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams324d ago0x9d6a65…75e04d
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams325d ago0x2ca441…9039c5
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams325d ago0x0539f2…8cf594
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams325d ago0x41ea54…d0aa8c
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams325d ago0xb2fa2c…6860b4
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams325d ago0xe9346c…34a8b1
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams325d ago0x7c0f39…23499b
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams325d ago0x0fe3a6…f55712
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams325d ago0x707850…a97b2f
0xf84d…e1200x6482…b779BaseBase$0.0001100%daydreams325d ago0xea1f84…f683fa

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.