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%daydreams346d ago0x6e7cbd…959a29
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams346d ago0xa6a72c…b45dbd
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams346d ago0xa97d5e…b98750
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams346d ago0xb17ff8…1bf548
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams346d ago0xfd4a00…2f22c3
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams346d ago0xb375a9…13fb21
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams347d ago0x2c24ac…7b0ac9
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams347d ago0x3bb25d…d05e9d
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams347d ago0xc2c188…bcff0d
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams347d ago0x4c6f02…4d9246
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams347d ago0xade7b9…e5f34a
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams347d ago0xbae87a…c9d9d0
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams347d ago0xb67ac0…f6ea2d
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams348d ago0xb46eae…09be48
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams348d ago0x299bcc…64756e
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams348d ago0x4bcc57…ae0f69
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams348d ago0x2f3379…e0bbb8
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams348d ago0xda357d…022db7
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams348d ago0x37d6a6…29c11c
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams348d ago0x09ff1a…209c1f
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams348d ago0xc94632…cd5cea
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams348d ago0x7e9698…384ad9
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams348d ago0x7a827d…9cc83a
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams348d ago0x35ecb1…b05c3c
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams349d ago0x744eec…873127

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.