AgentReport

0xedc1…092b

0xedc16dbc04c1915a4d308600d9d05ca2b8e9092bExplorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
268
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $0.03 of the $3068.58M Roundhouse has indexed across 1,402,563 wallets — less than 0.0001% of it.

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

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

$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 277d ago
    $0.03
    268 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.00268277d 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 268 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xedc1…092b0x6482…b779BaseBase$0.0001100%daydreams352d ago0x168170…88c563
0xedc1…092b0x6482…b779BaseBase$0.0001100%daydreams352d ago0x0f9aa4…357ad1
0xedc1…092b0x6482…b779BaseBase$0.0001100%daydreams352d ago0xedcddd…188951
0xedc1…092b0x6482…b779BaseBase$0.0001100%daydreams353d ago0x4a1137…b47ccd
0xedc1…092b0x6482…b779BaseBase$0.0001100%daydreams353d ago0x489f52…d160de
0xedc1…092b0x6482…b779BaseBase$0.0001100%daydreams353d ago0xf47dd7…c5a6c7
0xedc1…092b0x6482…b779BaseBase$0.0001100%daydreams353d ago0x34738e…254310
0xedc1…092b0x6482…b779BaseBase$0.0001100%daydreams353d ago0x7419f0…7da1e6
0xedc1…092b0x6482…b779BaseBase$0.0001100%daydreams353d ago0x6fd4df…226624
0xedc1…092b0x6482…b779BaseBase$0.0001100%daydreams353d ago0xe208cb…7c9f32
0xedc1…092b0x6482…b779BaseBase$0.0001100%daydreams353d ago0xe095fd…1920a7
0xedc1…092b0x6482…b779BaseBase$0.0001100%daydreams354d ago0x1c8b51…d23a70
0xedc1…092b0x6482…b779BaseBase$0.0001100%daydreams354d ago0x28870f…6d7601
0xedc1…092b0x6482…b779BaseBase$0.0001100%daydreams355d ago0x105607…10e67c
0xedc1…092b0x6482…b779BaseBase$0.0001100%daydreams355d ago0xe78291…1d41e9
0xedc1…092b0x6482…b779BaseBase$0.0001100%daydreams355d ago0x6a9b74…af06fc
0xedc1…092b0x6482…b779BaseBase$0.0001100%daydreams356d ago0xf1b6e7…c01212
0xedc1…092b0x6482…b779BaseBase$0.0001100%daydreams356d ago0x7e9f72…32ef2f
0xedc1…092b0x6482…b779BaseBase$0.0001100%daydreams356d ago0xd9482d…c791fc
0xedc1…092b0x6482…b779BaseBase$0.0001100%daydreams356d ago0x266d07…cb25d4
0xedc1…092b0x6482…b779BaseBase$0.0001100%daydreams356d ago0x27362c…e0dc04
0xedc1…092b0x6482…b779BaseBase$0.0001100%daydreams357d ago0x714c62…4c9e86
0xedc1…092b0x6482…b779BaseBase$0.0001100%daydreams357d ago0x9cc64c…5e7157
0xedc1…092b0x6482…b779BaseBase$0.0001100%daydreams357d ago0xacbf51…2e8b4c
0xedc1…092b0x6482…b779BaseBase$0.0001100%daydreams357d ago0xb5844d…5598d1

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

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

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: 0xedc1…092b

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