AgentReport

0x661d…56b1

0x661d8f302a45fb41b97d0449d43f076209a556b1Explorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
257
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 (257)

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

$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
    257 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.00257276d 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 257 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams326d ago0xd9b2a1…99f4d4
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams326d ago0x7646f8…9ba3d0
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams326d ago0xa898aa…303c86
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams326d ago0xcd5c60…7bdbf7
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams326d ago0x03940b…aa2ac6
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams326d ago0xf323dc…426c40
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams326d ago0x6bcce1…f63fa6
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams327d ago0x3741d9…f9f9f6
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams327d ago0xf47b14…2c9b3a
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams327d ago0xa849a8…78b35c
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams327d ago0x435bec…9d1a22
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams327d ago0x920943…2d0ea5
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams327d ago0xfd319f…ed5094
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams327d ago0xdb5fcb…6cd0b4
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams327d ago0xb58fd0…21d3fc
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams328d ago0x404710…2374fa
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams328d ago0x329e20…7a6c04
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams328d ago0x31fb80…fa7468
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams328d ago0x8cc146…6c4d61
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams335d ago0x4454ef…96cea3
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams337d ago0x50a6dc…488535
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams337d ago0x74a0c5…65cbf8
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams337d ago0x3060e9…24f616
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams337d ago0xf75d24…c6cad7
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams338d ago0x8fbd17…bbdf79

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

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

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: 0x661d…56b1

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