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.84M Roundhouse has indexed across 1,401,919 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%daydreams349d ago0x7f7707…99d0bd
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams349d ago0xcd1a4d…cf7afb
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams349d ago0xd80939…04af3b
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams349d ago0x9a90d8…102eee
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams349d ago0xf7c1b6…7eef04
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams350d ago0x3003fb…cf25de
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams350d ago0x6cdc97…5ebd61
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams350d ago0xee2af8…f3adfa
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams350d ago0xcdbe1b…feed0e
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams351d ago0xb6ecc9…064a51
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams351d ago0x63d079…fac397
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams351d ago0x4aac1a…ef6803
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams351d ago0x4f8ea6…00dd30
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams351d ago0xfb5c36…1e19e4
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams351d ago0xf942f8…52e3d5
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams352d ago0x1246f5…b445e5
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams352d ago0xd61a0d…f37902
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams352d ago0x5aab42…41ee06
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams352d ago0xa648db…4124c7
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams352d ago0x36d944…03754d
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams352d ago0x7c93a3…8f8109
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams352d ago0x1bc270…f1b09a
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams352d ago0xef3610…831cde
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams352d ago0xc9d6d2…24f62d
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams352d ago0xba5be2…fc80e0

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.