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,396 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 276d 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.00268276d 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%daydreams343d ago0x949245…5f6abf
0xedc1…092b0x6482…b779BaseBase$0.0001100%daydreams343d ago0x93db03…ba955a
0xedc1…092b0x6482…b779BaseBase$0.0001100%daydreams344d ago0xa8bf0a…164beb
0xedc1…092b0x6482…b779BaseBase$0.0001100%daydreams344d ago0x4c7cce…37b2b5
0xedc1…092b0x6482…b779BaseBase$0.0001100%daydreams344d ago0x72af88…b3c7ca
0xedc1…092b0x6482…b779BaseBase$0.0001100%daydreams344d ago0x28fbfd…c36158
0xedc1…092b0x6482…b779BaseBase$0.0001100%daydreams344d ago0x8e2794…eeea3f
0xedc1…092b0x6482…b779BaseBase$0.0001100%daydreams344d ago0x3d85f4…02e6dc
0xedc1…092b0x6482…b779BaseBase$0.0001100%daydreams344d ago0xa56571…233216
0xedc1…092b0x6482…b779BaseBase$0.0001100%daydreams344d ago0x2563ac…44db08
0xedc1…092b0x6482…b779BaseBase$0.0001100%daydreams344d ago0x24a92b…456fa7
0xedc1…092b0x6482…b779BaseBase$0.0001100%daydreams344d ago0xa8d33e…8ed1b0
0xedc1…092b0x6482…b779BaseBase$0.0001100%daydreams344d ago0x81bc81…49583e
0xedc1…092b0x6482…b779BaseBase$0.0001100%daydreams344d ago0x57ef07…386598
0xedc1…092b0x6482…b779BaseBase$0.0001100%daydreams345d ago0x0e17c7…339c8a
0xedc1…092b0x6482…b779BaseBase$0.0001100%daydreams345d ago0xa534cb…ec47c2
0xedc1…092b0x6482…b779BaseBase$0.0001100%daydreams345d ago0x645d26…b2b81a
0xedc1…092b0x6482…b779BaseBase$0.0001100%daydreams345d ago0x30b16d…046d2c
0xedc1…092b0x6482…b779BaseBase$0.0001100%daydreams345d ago0xde434f…b21637
0xedc1…092b0x6482…b779BaseBase$0.0001100%daydreams345d ago0xbea776…9d3447
0xedc1…092b0x6482…b779BaseBase$0.0001100%daydreams345d ago0x6111d7…a39ec5
0xedc1…092b0x6482…b779BaseBase$0.0001100%daydreams345d ago0x5bf3e4…2f63d1
0xedc1…092b0x6482…b779BaseBase$0.0001100%daydreams345d ago0x3dfd32…63a001
0xedc1…092b0x6482…b779BaseBase$0.0001100%daydreams345d ago0xe6f89e…550e3d
0xedc1…092b0x6482…b779BaseBase$0.0001100%daydreams345d ago0x144ee6…aad4a4

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.