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%daydreams344d ago0xd8abf8…7533b1
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams344d ago0x04cce5…8bb5b8
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams344d ago0x3dbd95…55ffd0
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams344d ago0x511578…b4ffc4
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams344d ago0xb573b5…260ff5
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams344d ago0xfc4383…a80502
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams344d ago0x1bd38d…db8fc0
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams344d ago0x4b0a96…a9d538
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams344d ago0x79576d…53cb10
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams345d ago0xfb9a0f…6d2f33
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams345d ago0xf8d2fd…98d957
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams345d ago0xc9efc3…f8bedf
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams345d ago0x75b0f4…e1ebed
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams345d ago0x2d02e4…965812
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams345d ago0x67ec57…a4bae9
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams345d ago0x3f7750…9f8940
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams345d ago0x9dcb0d…cf4433
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams345d ago0xdd91d7…b07775
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams345d ago0x3602e2…321e2a
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams345d ago0x9d92ed…e09e88
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams346d ago0xe2a266…be06e9
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams346d ago0x1c9687…86f9dd
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams346d ago0xfcce30…bc7f10
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams346d ago0x9e2593…9267c1
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams346d ago0xec5d09…4c584b

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.