AgentReport

0x07f3…64b8

0x07f3cb180f7f09369ba405d3dfc45bfeb7fc64b8Explorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
271
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,563 wallets — less than 0.0001% of it.

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

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

$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
    271 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.00271277d 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 271 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams341d ago0x66c518…9285d1
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams341d ago0x0eb48d…3c679a
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams341d ago0x3658c3…fb2ce4
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams341d ago0xde9cf7…85d9d0
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams341d ago0xa09f0d…cfb8db
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams341d ago0x5a5e86…fe0ab9
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams341d ago0x080eb5…9cc01a
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams341d ago0x8d86e3…16a43c
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams341d ago0x5013d4…580fb9
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams341d ago0x3bd2be…76fa3d
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams342d ago0x7d65f6…139f33
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams342d ago0xd4758e…031b97
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams342d ago0x996b01…629dfb
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams342d ago0x819f2b…c846e9
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams342d ago0x56b9f5…cd511a
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams342d ago0x3569e9…0073d8
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams342d ago0x3b108d…3702aa
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams342d ago0x248a22…7bcf9a
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams342d ago0xeb7a9a…59d06c
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams342d ago0xbce35a…039803
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams342d ago0xe2bcd0…35f10d
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams343d ago0xbd7534…7e3076
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams343d ago0x283dce…186d9f
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams343d ago0x28039c…987c0d
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams343d ago0xfed6b2…74c12b

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

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

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: 0x07f3…64b8

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