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%daydreams344d ago0x351c13…bd40ad
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams344d ago0xa77d1d…34d59e
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams344d ago0xb9af2e…629e2c
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams344d ago0x6895f6…06fd44
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams344d ago0x5f1952…2d9445
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams344d ago0xec6320…edfa14
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams344d ago0xc0e24d…9b2904
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams344d ago0x7a900c…e478db
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams344d ago0xc325b6…c0e8b4
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams345d ago0x53e997…e2cccb
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams345d ago0x38ab8c…507b12
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams345d ago0x67d128…8d2571
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams345d ago0x424fc7…dca6ea
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams345d ago0x90ebc9…c8668f
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams345d ago0x9ea08e…b030ad
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams345d ago0x957611…f15fc1
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams345d ago0x7d34a7…1f29e2
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams345d ago0xab1125…3a6553
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams345d ago0xb461ca…080c6c
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams345d ago0x1b80da…95719e
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams345d ago0x5cd879…4ade1c
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams346d ago0x5bb19b…08e19c
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams346d ago0xa0a260…cf0cad
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams346d ago0x75bff4…581e62
0x661d…56b10x6482…b779BaseBase$0.0001100%daydreams346d ago0xf63cab…3a6db6

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.