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%daydreams341d ago0x08b2b0…dd32f8
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams341d ago0x59cf0f…6e9236
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams341d ago0x56fb81…8784cb
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams342d ago0x15c6fb…5db253
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams342d ago0x072e6c…4cae64
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams342d ago0x43cb43…ef23ba
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams342d ago0xd4ccd2…11d227
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams342d ago0x20ba69…71b3b4
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams342d ago0x8aa074…83b0b1
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams342d ago0xa82c99…260de3
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams342d ago0x5c2f22…190412
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams342d ago0x136a66…6c58ea
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams342d ago0x4a0708…56f0ad
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams343d ago0x93b1d3…5ce127
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams343d ago0xf7bc54…c568e6
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams343d ago0xe04360…86b5f1
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams343d ago0x3bec3f…a29a52
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams343d ago0x358d6c…2c59f1
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams343d ago0x6b52e9…3888c3
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams343d ago0x22bd7c…710006
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams343d ago0x522cd6…7e61d8
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams343d ago0x9fabbe…06c3f7
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams344d ago0x8e0aed…0ed99b
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams344d ago0x74f971…963e25
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams344d ago0xeb1f21…5cb6d1

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.