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%daydreams348d ago0x78da5b…73c4ec
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams348d ago0xf26c9e…05e1f3
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams348d ago0x74ba22…f5713d
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams348d ago0x3a3db8…1b3e46
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams348d ago0xbfcd06…dcdbe7
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams348d ago0x7db7b9…815c18
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams349d ago0xc8e61e…9a1b35
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams349d ago0x695dee…6309b0
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams349d ago0x196594…f47888
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams349d ago0x60c783…3032b0
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams349d ago0xd4dc5f…9284ec
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams349d ago0xaccf94…0c528c
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams349d ago0x038a4e…70cf83
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams349d ago0xbc8466…5c2dab
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams350d ago0xcfbad3…cbd7b6
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams350d ago0x99a9be…6330fc
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams350d ago0xcfcccb…92ce0c
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams350d ago0xd77258…07ddfa
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams350d ago0x5517a8…f344a0
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams351d ago0x587bea…427322
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams351d ago0x62bf41…fed23e
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams351d ago0xc8ab79…4c3e91
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams351d ago0xe9f7e0…3458a0
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams351d ago0x543762…8773b3
0x07f3…64b80x6482…b779BaseBase$0.0001100%daydreams352d ago0x1ebd81…a93b25

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.