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.84M Roundhouse has indexed across 1,401,919 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%daydreams353d ago0x0bb0cf…e61819
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams353d ago0xb9eae1…259954
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams353d ago0xced37a…045aac
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams353d ago0xd46d88…9eb1fe
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams353d ago0xeeb04b…999ad9
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams354d ago0x25eca2…86bd59
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams355d ago0xcb5596…18c750
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams355d ago0x13b2f4…00ca15
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams355d ago0x822dee…68e2ca
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams355d ago0x349d8c…95b945
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams356d ago0xdd2b43…917f4c
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams356d ago0xb6d76d…800031
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams356d ago0xb3347c…6e84fa
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams356d ago0x122711…9beff5
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams357d ago0xaf85cc…38cf7b
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams357d ago0xcc8fda…a090e6
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams357d ago0xb23bad…8949e7
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams357d ago0x746c46…f96cfb
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams357d ago0xc8fc62…220acd
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams358d ago0x149376…ffdfcd
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams358d ago0x05e26a…3aadb1
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams358d ago0xb5a5b7…af534e
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams359d ago0x31726f…a8fa3d
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams359d ago0xbe9077…6e34b9
0x7061…2fd70x6482…b779BaseBase$0.0001100%daydreams359d ago0x43c2c8…110996

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.