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,396 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%daydreams336d ago0xf727df…a52bbf
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams337d ago0xf26b5f…04b26f
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams337d ago0x42c244…31f648
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams337d ago0x430e9c…d04c7a
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams337d ago0xe9b06d…95d647
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams338d ago0x11e76a…0d880a
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams338d ago0x6204bc…cb9e00
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams338d ago0xdb0116…afc017
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams338d ago0x78835a…232c6a
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams338d ago0x42d1b5…051b04
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams338d ago0x3d634e…e1a8c5
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams338d ago0x50223c…bb611d
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams338d ago0x85e1ba…5d7c1e
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams339d ago0x650e73…a52596
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams340d ago0xc89628…d176cb
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams340d ago0xda7462…21531b
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams340d ago0x02b540…ed3f1c
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams340d ago0xdef894…71704b
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams340d ago0xed0b57…ee12f6
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams340d ago0xb5cfd4…e7a6a4
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams340d ago0xad60a3…7d7120
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams340d ago0x50fc5c…ebc361
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams340d ago0xbf19ab…054e4f
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams340d ago0x514948…afca91
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams340d ago0x7b1eee…62c1d4

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.