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 $3069.68M Roundhouse has indexed across 1,403,034 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%daydreams341d ago0xaf3766…ebf6e0
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams341d ago0x0dc739…8cd1d7
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams341d ago0xd1e71e…ef9f43
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams341d ago0xc62365…a681cc
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams341d ago0xa3c435…be320c
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams341d ago0x5daaff…3bc2ab
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams341d ago0x6eb1ea…269b76
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams342d ago0xb0d16b…ed854b
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams342d ago0xc16ad3…b81645
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams342d ago0xb26d2e…7cb8e4
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams342d ago0x8fafb1…e46a6a
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams342d ago0x3f769f…5b63c2
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams342d ago0xf41549…0db906
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams342d ago0xa0cae4…516198
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams342d ago0xedf22f…8066fe
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams342d ago0x2c4927…dfcd51
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams342d ago0x902192…e62593
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams342d ago0xfaf885…971eb6
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams343d ago0xfddee8…81af2d
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams343d ago0x03fac6…54d8be
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams343d ago0xa1cb68…e1b470
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams343d ago0x82aa70…54e415
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams343d ago0xc2c1a8…81713a
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams343d ago0x7dda1d…036d37
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams343d ago0xf5a873…775112

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.