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 $3066.54M Roundhouse has indexed across 1,400,689 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%daydreams323d ago0x7be500…d8f236
0x56c6…17150x6482…b779BaseBase$0.0001100%daydreams323d ago0xe6ca70…f4fe2d
0x56c6…17150x6482…b779BaseBase$0.0001100%daydreams323d ago0x72acae…0b68f3
0x56c6…17150x6482…b779BaseBase$0.0001100%daydreams323d ago0x022ade…3d9b2f
0x56c6…17150x6482…b779BaseBase$0.0001100%daydreams323d ago0x294ea2…aed1e8
0x56c6…17150x6482…b779BaseBase$0.0001100%daydreams324d ago0x46cd68…d604f4
0x56c6…17150x6482…b779BaseBase$0.0001100%daydreams324d ago0x106e5a…ae093c
0x56c6…17150x6482…b779BaseBase$0.0001100%daydreams324d ago0x4c99dd…cdc7d9
0x56c6…17150x6482…b779BaseBase$0.0001100%daydreams324d ago0x63528d…ed1de2
0x56c6…17150x6482…b779BaseBase$0.0001100%daydreams324d ago0x14ae72…997ba5
0x56c6…17150x6482…b779BaseBase$0.0001100%daydreams324d ago0x755773…5b12ce
0x56c6…17150x6482…b779BaseBase$0.0001100%daydreams324d ago0x68bea6…057857
0x56c6…17150x6482…b779BaseBase$0.0001100%daydreams324d ago0x9aa08b…3b7069
0x56c6…17150x6482…b779BaseBase$0.0001100%daydreams324d ago0xb02661…cfa582
0x56c6…17150x6482…b779BaseBase$0.0001100%daydreams324d ago0xda9fe5…7584b6
0x56c6…17150x6482…b779BaseBase$0.0001100%daydreams325d ago0x3440f7…0535fc
0x56c6…17150x6482…b779BaseBase$0.0001100%daydreams325d ago0x55068e…54a75d
0x56c6…17150x6482…b779BaseBase$0.0001100%daydreams325d ago0xeb05d2…51ab19
0x56c6…17150x6482…b779BaseBase$0.0001100%daydreams325d ago0xba11c1…dab5f1
0x56c6…17150x6482…b779BaseBase$0.0001100%daydreams325d ago0xa514a9…e84672
0x56c6…17150x6482…b779BaseBase$0.0001100%daydreams325d ago0x1292bb…0e06ac
0x56c6…17150x6482…b779BaseBase$0.0001100%daydreams325d ago0xa061ba…a9b1b0
0x56c6…17150x6482…b779BaseBase$0.0001100%daydreams325d ago0x84d85a…961cc7
0x56c6…17150x6482…b779BaseBase$0.0001100%daydreams325d ago0xd81934…2bae72
0x56c6…17150x6482…b779BaseBase$0.0001100%daydreams326d ago0x3bb864…c4939b

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.