AgentReport

0x56c6…1715

0x56c61cec57bb8634dd896a4b420573d970571715Explorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
256
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,575 wallets — less than 0.0001% of it.

Chains (from the recent scan): Base (256)

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.032561

$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
    256 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.00256276d 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 256 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x56c6…17150x6482…b779BaseBase$0.0001100%daydreams349d ago0xe46f92…a32fec
0x56c6…17150x6482…b779BaseBase$0.0001100%daydreams349d ago0x5bcf8f…466a84
0x56c6…17150x6482…b779BaseBase$0.0001100%daydreams349d ago0x49eec9…fd2749
0x56c6…17150x6482…b779BaseBase$0.0001100%daydreams350d ago0x1076f3…960edb
0x56c6…17150x6482…b779BaseBase$0.0001100%daydreams350d ago0x671c77…8f3aa9
0x56c6…17150x6482…b779BaseBase$0.0001100%daydreams350d ago0xfc9e31…4cd801
0x56c6…17150x6482…b779BaseBase$0.0001100%daydreams351d ago0xf440f4…6d4d76
0x56c6…17150x6482…b779BaseBase$0.0001100%daydreams351d ago0x646b3d…681c6d
0x56c6…17150x6482…b779BaseBase$0.0001100%daydreams351d ago0x4a4d98…0b06da
0x56c6…17150x6482…b779BaseBase$0.0001100%daydreams351d ago0x6d75a2…6c1446
0x56c6…17150x6482…b779BaseBase$0.0001100%daydreams351d ago0x605bfa…cd42a8
0x56c6…17150x6482…b779BaseBase$0.0001100%daydreams351d ago0x7f7ca2…b18ce8
0x56c6…17150x6482…b779BaseBase$0.0001100%daydreams351d ago0xdb47b5…58470c
0x56c6…17150x6482…b779BaseBase$0.0001100%daydreams351d ago0x609af6…dcbc6f
0x56c6…17150x6482…b779BaseBase$0.0001100%daydreams351d ago0xab5e86…a0bcc6
0x56c6…17150x6482…b779BaseBase$0.0001100%daydreams352d ago0xb79730…9cec3b
0x56c6…17150x6482…b779BaseBase$0.0001100%daydreams352d ago0xcf1837…cdb6a5
0x56c6…17150x6482…b779BaseBase$0.0001100%daydreams352d ago0x892a30…a15fee
0x56c6…17150x6482…b779BaseBase$0.0001100%daydreams352d ago0xc37f31…995548
0x56c6…17150x6482…b779BaseBase$0.0001100%daydreams352d ago0x422903…f8c917
0x56c6…17150x6482…b779BaseBase$0.0001100%daydreams352d ago0xc91dbf…eec71a
0x56c6…17150x6482…b779BaseBase$0.0001100%daydreams352d ago0xb31390…75c513
0x56c6…17150x6482…b779BaseBase$0.0001100%daydreams352d ago0x42e1be…281927
0x56c6…17150x6482…b779BaseBase$0.0001100%daydreams352d ago0x5acade…0a3645
0x56c6…17150x6482…b779BaseBase$0.0001100%daydreams352d ago0x92216c…6e1f1d

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 0x56c6…1715 has actually paid for over the free read API. No key, no account.

GET api.roundhouseai.io/v0/agents/0x56c61cec57bb8634dd896a4b420573d970571715

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: 0x56c6…1715

curl -s 'https://api.roundhouseai.io/v0/agents/0x56c61cec57bb8634dd896a4b420573d970571715'
curl -s 'https://api.roundhouseai.io/v0/entities/0x56c61cec57bb8634dd896a4b420573d970571715/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.