AgentReport

0x7061…2fd7

0x7061e8978a7f79cf1d2e580f2263714f61e02fd7Explorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
261
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $0.03 of the $3067.43M Roundhouse has indexed across 1,401,742 wallets — less than 0.0001% of it.

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

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

$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
    261 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.00261276d 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 261 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams346d ago0xe15d06…4924a1
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams346d ago0x1fa3c0…a1cf4c
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams346d ago0xfc2406…d211cd
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams346d ago0x7e63ab…dbc68f
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams346d ago0x2847d2…ddafdd
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams346d ago0x20ac9a…357073
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams347d ago0x5cd710…d68196
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams347d ago0x74b74a…5b55fb
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams347d ago0xc07420…e5ea15
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams347d ago0x8cf2ff…bf9584
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams347d ago0xeef60b…6a1bc2
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams347d ago0xdbbe7f…6a5aff
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams348d ago0x7b9a04…000a96
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams348d ago0xd6671c…ed733b
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams348d ago0x0c1196…2b9601
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams348d ago0x9ac4e6…331b1b
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams348d ago0x8f1231…545207
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams348d ago0xe61f55…a7903c
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams348d ago0xa627eb…2a2593
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams348d ago0x68ef3f…bb1e89
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams348d ago0x851af4…64cc55
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams348d ago0x2e8276…39d658
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams348d ago0x2bbcd7…9b6a87
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams349d ago0x2e6bad…0b7320
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams349d ago0x717841…4cd8c3

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

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

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: 0x7061…2fd7

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