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.00M Roundhouse has indexed across 1,401,091 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%daydreams346d ago0x66b1fe…e50abd
0x56c6…17150x6482…b779BaseBase$0.0001100%daydreams346d ago0x0acd55…9f260e
0x56c6…17150x6482…b779BaseBase$0.0001100%daydreams346d ago0x554cd1…7d9c28
0x56c6…17150x6482…b779BaseBase$0.0001100%daydreams346d ago0x6d8b44…7441f1
0x56c6…17150x6482…b779BaseBase$0.0001100%daydreams346d ago0x27b1a7…7f9dee
0x56c6…17150x6482…b779BaseBase$0.0001100%daydreams346d ago0x822715…483fe2
0x56c6…17150x6482…b779BaseBase$0.0001100%daydreams346d ago0x46a466…c5face
0x56c6…17150x6482…b779BaseBase$0.0001100%daydreams347d ago0x936d59…133b52
0x56c6…17150x6482…b779BaseBase$0.0001100%daydreams347d ago0xa9f86b…57e364
0x56c6…17150x6482…b779BaseBase$0.0001100%daydreams347d ago0x7590e7…d6c3fd
0x56c6…17150x6482…b779BaseBase$0.0001100%daydreams347d ago0xb050f9…bf81a7
0x56c6…17150x6482…b779BaseBase$0.0001100%daydreams347d ago0xe16168…3d6cc6
0x56c6…17150x6482…b779BaseBase$0.0001100%daydreams348d ago0xb690de…33c1df
0x56c6…17150x6482…b779BaseBase$0.0001100%daydreams348d ago0xb676d2…4fe63f
0x56c6…17150x6482…b779BaseBase$0.0001100%daydreams348d ago0x1aa8b7…b6a007
0x56c6…17150x6482…b779BaseBase$0.0001100%daydreams348d ago0x8e4770…45d968
0x56c6…17150x6482…b779BaseBase$0.0001100%daydreams348d ago0x461bbc…c11139
0x56c6…17150x6482…b779BaseBase$0.0001100%daydreams348d ago0x3f5232…b50418
0x56c6…17150x6482…b779BaseBase$0.0001100%daydreams348d ago0x21cfaa…d0f359
0x56c6…17150x6482…b779BaseBase$0.0001100%daydreams348d ago0x538603…fa6eb8
0x56c6…17150x6482…b779BaseBase$0.0001100%daydreams348d ago0x51524c…b15395
0x56c6…17150x6482…b779BaseBase$0.0001100%daydreams348d ago0x8229a8…2de535
0x56c6…17150x6482…b779BaseBase$0.0001100%daydreams348d ago0x18c2bf…cf932f
0x56c6…17150x6482…b779BaseBase$0.0001100%daydreams349d ago0xa03c29…b238a5
0x56c6…17150x6482…b779BaseBase$0.0001100%daydreams349d ago0xd33574…fd55a4

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.