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%daydreams352d ago0x3a41bc…50155a
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams353d ago0xca0023…e221e9
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams353d ago0xc85a9b…ffbf2d
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams353d ago0xf110e0…4352b5
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams353d ago0x6d1ab8…8ca161
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams353d ago0xfd1350…804508
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams354d ago0x808d1a…5910af
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams355d ago0xef819c…960141
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams355d ago0x917f50…f24ffc
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams355d ago0x8fd593…fc7007
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams355d ago0x9fb4b7…569eba
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams355d ago0xce29c2…469a3b
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams356d ago0xae01df…899457
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams356d ago0x105504…efd63a
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams356d ago0x6f39b0…33e771
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams356d ago0xbd2faa…ea27e6
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams357d ago0xda80d8…458ed0
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams357d ago0x6bdd8a…bd2b92
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams357d ago0x419c90…8e3f72
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams357d ago0x78067a…675325
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams357d ago0x1135fe…f31d8b
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams358d ago0x99cb32…77d5d6
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams358d ago0x2967a7…50dc6d
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams358d ago0xc1f3dd…49f2b4
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams359d ago0x9278ea…cc1001

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.