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%daydreams326d ago0xf49037…a41d85
0xf122…78680x6482…b779BaseBase$0.0001100%daydreams326d ago0xc7f813…004579
0xf122…78680x6482…b779BaseBase$0.0001100%daydreams326d ago0xf42ef7…8e8242
0xf122…78680x6482…b779BaseBase$0.0001100%daydreams326d ago0x8078ce…935cbb
0xf122…78680x6482…b779BaseBase$0.0001100%daydreams326d ago0xa19333…2205ed
0xf122…78680x6482…b779BaseBase$0.0001100%daydreams326d ago0x440b9f…cd42ec
0xf122…78680x6482…b779BaseBase$0.0001100%daydreams327d ago0xd35519…18915c
0xf122…78680x6482…b779BaseBase$0.0001100%daydreams327d ago0x3864bb…186faa
0xf122…78680x6482…b779BaseBase$0.0001100%daydreams327d ago0x58a609…7f0875
0xf122…78680x6482…b779BaseBase$0.0001100%daydreams327d ago0xda5067…4bc6b9
0xf122…78680x6482…b779BaseBase$0.0001100%daydreams327d ago0xc22e6b…b663f5
0xf122…78680x6482…b779BaseBase$0.0001100%daydreams327d ago0x9138da…48a41d
0xf122…78680x6482…b779BaseBase$0.0001100%daydreams327d ago0x1204ea…3139c3
0xf122…78680x6482…b779BaseBase$0.0001100%daydreams327d ago0x39c97d…e84c56
0xf122…78680x6482…b779BaseBase$0.0001100%daydreams328d ago0x2dfd83…96b0e7
0xf122…78680x6482…b779BaseBase$0.0001100%daydreams328d ago0xc46fc2…29e9f1
0xf122…78680x6482…b779BaseBase$0.0001100%daydreams328d ago0x34937e…21a3e9
0xf122…78680x6482…b779BaseBase$0.0001100%daydreams328d ago0x7d6a68…0003af
0xf122…78680x6482…b779BaseBase$0.0001100%daydreams328d ago0x25529f…33f7f7
0xf122…78680x6482…b779BaseBase$0.0001100%daydreams336d ago0x0defdc…48e4b7
0xf122…78680x6482…b779BaseBase$0.0001100%daydreams337d ago0x3cde9f…15d34b
0xf122…78680x6482…b779BaseBase$0.0001100%daydreams337d ago0xd4ac91…b1d0a1
0xf122…78680x6482…b779BaseBase$0.0001100%daydreams337d ago0xfa892f…515b12
0xf122…78680x6482…b779BaseBase$0.0001100%daydreams338d ago0x1d97fc…0dd26f
0xf122…78680x6482…b779BaseBase$0.0001100%daydreams338d ago0xdf0985…95dd72

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.