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%daydreams341d ago0x558d4b…dc9c8f
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams341d ago0x54a337…87cd00
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams341d ago0x530358…85a349
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams342d ago0x8b0065…4bbb73
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams342d ago0xbeccc6…bfc012
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams342d ago0x5f4d5c…5a9857
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams342d ago0x94e8f3…daa91e
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams342d ago0x7a0816…d49206
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams342d ago0x839e79…c7f956
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams342d ago0x4acf34…b5bafe
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams342d ago0x30161c…2a1443
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams342d ago0x070e46…f2d618
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams342d ago0xfa2197…c4e1a5
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams343d ago0x11d989…dd7473
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams343d ago0x74e09a…f2fbf8
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams343d ago0xd97950…1cf9df
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams343d ago0x66ecb9…e75f0d
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams343d ago0x81dbcc…aed656
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams343d ago0xddfc1f…d114eb
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams343d ago0xa52ec5…91df7a
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams343d ago0x64f36b…ee9279
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams343d ago0xdd1c85…4d045e
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams343d ago0x4dbc17…d195df
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams343d ago0x5f1dba…52f0d8
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams344d ago0x0100b7…7ba0ca

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.