AgentReport

0x1deb…c440

0x1debb4d950b770fb5e1013a00385b6729ad6c440Explorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
266
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 (266)

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

$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
    266 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.00266277d 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 266 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams277d ago0xd7c960…08bdd0
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams277d ago0x0bdbe4…4af57b
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams280d ago0x72c1a3…c9c806
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams321d ago0xc29c61…e4f4d4
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams321d ago0xec2a7a…412cc9
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams321d ago0x92343c…b25175
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams322d ago0xc08ee3…1d795f
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams322d ago0x81fd3d…9a0f53
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams322d ago0xe4f1b8…d380e4
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams322d ago0xf425d1…fb2d35
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams322d ago0x3e1677…ce2802
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams322d ago0x3eaffc…41f791
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams322d ago0xa85f52…36600c
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams322d ago0x36c35f…c1cfe1
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams322d ago0x25b3c8…995f78
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams322d ago0xf7d084…f8d454
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams323d ago0x9459ef…4d15f7
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams323d ago0xecf8d0…6a2804
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams323d ago0x7061d3…561aa9
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams323d ago0x5fb2d0…a88288
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams323d ago0xd69004…86c29a
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams323d ago0x2da519…1c6c87
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams323d ago0xb862bd…b70693
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams323d ago0x11135b…6d7bab
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams323d ago0xaf6c75…13a58f

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

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

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: 0x1deb…c440

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