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%daydreams326d ago0xaf5308…4eaa74
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams326d ago0xaedce0…395d8c
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams326d ago0xc43d28…375a3b
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams326d ago0x1e1fa0…b69406
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams326d ago0x447171…9fa823
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams326d ago0x49de80…c825d2
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams326d ago0xebd049…e70666
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams327d ago0x792da8…447c77
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams327d ago0x44ea73…ca2645
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams327d ago0x7d4315…c7cdbc
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams327d ago0x0b0edb…c65eae
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams327d ago0x374e41…dbff4e
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams327d ago0x165bb3…7e698d
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams327d ago0xe7e607…25b83d
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams327d ago0x922ff7…d6e95e
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams327d ago0x607e5e…bbeeed
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams327d ago0x17bf46…445f44
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams328d ago0xc5363b…53c09f
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams328d ago0x9c9629…129300
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams328d ago0xb9804c…f0b31d
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams328d ago0x6acd31…f742fc
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams336d ago0x868da5…b0b0e6
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams337d ago0x25d4d7…50675c
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams337d ago0x9c73d5…e93b93
0x1deb…c4400x6482…b779BaseBase$0.0001100%daydreams337d ago0x98a399…e9220a

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.