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,722 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%daydreams337d ago0xefea24…da5e93
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams338d ago0x63d960…3a1809
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams338d ago0x1f3a2e…7a995c
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams338d ago0x5ae86b…599c73
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams338d ago0x858267…7f766a
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams338d ago0x496f60…015cc2
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams338d ago0x4ac842…84d37a
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams338d ago0x1a47d1…e6ac77
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams338d ago0xf374b3…47495b
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams338d ago0x489fda…3422db
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams340d ago0x7ef16b…8b31c8
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams340d ago0x2266eb…4f7abe
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams340d ago0x754718…5b24c6
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams340d ago0xf3711b…140495
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams340d ago0x9554b6…8ca4d4
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams340d ago0x62db88…4f13c3
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams340d ago0x3b51ed…e06fa6
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams340d ago0x4f0a99…8cc96e
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams340d ago0x72a131…ba50fe
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams340d ago0xd29bc5…953b26
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams340d ago0x2ddbef…cdae08
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams341d ago0x050807…8053c5
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams341d ago0x599ad0…9167fc
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams341d ago0x69b4e2…cedf93
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams341d ago0x999b1e…c1158b

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.