AgentReport

0xf122…7868

0xf122c4d0740f6459e0ce6cabed105fbe25207868Explorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
258
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $0.03 of the $3068.58M Roundhouse has indexed across 1,402,722 wallets — less than 0.0001% of it.

Chains (from the recent scan): Base (258)

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

$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 277d ago
    $0.03
    258 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.00258277d 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 258 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xf122…78680x6482…b779BaseBase$0.0001100%daydreams323d ago0x15add0…a081d6
0xf122…78680x6482…b779BaseBase$0.0001100%daydreams323d ago0x47b86e…bb4fc0
0xf122…78680x6482…b779BaseBase$0.0001100%daydreams324d ago0x1dbe63…bf3af0
0xf122…78680x6482…b779BaseBase$0.0001100%daydreams324d ago0xdb4186…f19a48
0xf122…78680x6482…b779BaseBase$0.0001100%daydreams324d ago0xbd3d4d…799b38
0xf122…78680x6482…b779BaseBase$0.0001100%daydreams324d ago0x1d373b…395ce8
0xf122…78680x6482…b779BaseBase$0.0001100%daydreams324d ago0x5bbafa…7b4a85
0xf122…78680x6482…b779BaseBase$0.0001100%daydreams324d ago0xe53409…c17aac
0xf122…78680x6482…b779BaseBase$0.0001100%daydreams324d ago0x94a615…50a39e
0xf122…78680x6482…b779BaseBase$0.0001100%daydreams324d ago0x5469b4…6d3136
0xf122…78680x6482…b779BaseBase$0.0001100%daydreams324d ago0x16c9ad…fcbcb5
0xf122…78680x6482…b779BaseBase$0.0001100%daydreams325d ago0x163540…2949f6
0xf122…78680x6482…b779BaseBase$0.0001100%daydreams325d ago0x6d40ad…708c46
0xf122…78680x6482…b779BaseBase$0.0001100%daydreams325d ago0x8200d3…44b58a
0xf122…78680x6482…b779BaseBase$0.0001100%daydreams325d ago0xe1d4a4…641e43
0xf122…78680x6482…b779BaseBase$0.0001100%daydreams325d ago0xf6f5e7…aca366
0xf122…78680x6482…b779BaseBase$0.0001100%daydreams325d ago0xdcb59f…548fdb
0xf122…78680x6482…b779BaseBase$0.0001100%daydreams325d ago0xa8614e…3c2a68
0xf122…78680x6482…b779BaseBase$0.0001100%daydreams325d ago0xa033f5…b54f33
0xf122…78680x6482…b779BaseBase$0.0001100%daydreams325d ago0xf1313c…d1be9f
0xf122…78680x6482…b779BaseBase$0.0001100%daydreams325d ago0x1a7861…f693a8
0xf122…78680x6482…b779BaseBase$0.0001100%daydreams325d ago0x6dd212…60d661
0xf122…78680x6482…b779BaseBase$0.0001100%daydreams326d ago0xafd60e…680626
0xf122…78680x6482…b779BaseBase$0.0001100%daydreams326d ago0x0ae538…138c7c
0xf122…78680x6482…b779BaseBase$0.0001100%daydreams326d ago0x99c765…717f31

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

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

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: 0xf122…7868

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