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 $3067.84M Roundhouse has indexed across 1,402,228 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 276d 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.00271276d 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%daydreams323d ago0x7a9462…90c96d
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams323d ago0x27785b…df8744
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams323d ago0x07e151…ceb637
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams323d ago0x32490c…938bda
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams323d ago0x8a4287…31acf8
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams324d ago0xc07c8f…21b1ce
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams324d ago0xda8d3d…c35bf1
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams324d ago0xd436dc…8c5c29
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams324d ago0x085f52…41bb0d
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams324d ago0x612e96…4bf88e
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams324d ago0xf5ad20…e93f5c
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams324d ago0x312122…637063
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams324d ago0xb3e5ea…67fdac
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams324d ago0x349427…ba6d02
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams324d ago0x87724f…3cdb3b
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams324d ago0x5549e4…c8bc9a
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams325d ago0xe04463…f7881f
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams325d ago0x10bd71…0ea6ec
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams325d ago0x05280b…240979
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams325d ago0x63eabe…afbf42
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams325d ago0x1dc2d2…36f657
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams325d ago0xc1963e…a9d932
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams325d ago0x86e2ea…0f4a9f
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams325d ago0x8566e0…4a2fed
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams325d ago0x60193e…0a45f6

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.