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%daydreams338d ago0x4ab224…fb1db1
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams338d ago0x0b8052…ed89a7
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams338d ago0xb6a05a…ddbfd7
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams338d ago0x7e7934…10ad7f
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams338d ago0xde1e37…9ce826
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams339d ago0x4436b5…81610e
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams339d ago0xcc5004…6a6262
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams339d ago0x2e26a8…11e819
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams340d ago0x05ceb2…b3ccdd
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams340d ago0xdd8895…867894
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams340d ago0x35ada1…adee47
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams340d ago0x46be8f…a22359
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams340d ago0x39e026…85e066
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams340d ago0x1ecbcd…5b5c96
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams340d ago0xadc4a7…4a7d50
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams340d ago0x3ece47…7b8ef2
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams340d ago0x5e50e0…172325
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams340d ago0x2ac8b2…7b710e
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams340d ago0x43c1af…36a25a
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams341d ago0x968f9b…a48b9f
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams341d ago0x04a761…d85cb5
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams341d ago0xb1a62d…40ae9d
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams341d ago0x8b9474…6b3c80
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams341d ago0x136e13…0fe397
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams341d ago0x00785f…f4f04c

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.