AgentReport

0xd1ca…e9e3

0xd1ca9d242cbbafca358991877c5e5a44cbc4e9e3Explorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
280
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $0.03 of the $3067.84M Roundhouse has indexed across 1,402,228 wallets — less than 0.0001% of it.

Chains (from the recent scan): Base (280)

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

$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
    280 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.00280276d 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 280 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xd1ca…e9e30x6482…b779BaseBase$0.0001100%daydreams352d ago0xa8f8c1…fc9c51
0xd1ca…e9e30x6482…b779BaseBase$0.0001100%daydreams352d ago0x2d7b6a…6d7b7b
0xd1ca…e9e30x6482…b779BaseBase$0.0001100%daydreams352d ago0x35e15b…d3e9bc
0xd1ca…e9e30x6482…b779BaseBase$0.0001100%daydreams352d ago0x34beaa…3aa6d4
0xd1ca…e9e30x6482…b779BaseBase$0.0001100%daydreams353d ago0xd438d0…88fb21
0xd1ca…e9e30x6482…b779BaseBase$0.0001100%daydreams353d ago0x0cfd43…f036fc
0xd1ca…e9e30x6482…b779BaseBase$0.0001100%daydreams353d ago0xf1cc3a…eb02e4
0xd1ca…e9e30x6482…b779BaseBase$0.0001100%daydreams353d ago0x374162…fdd975
0xd1ca…e9e30x6482…b779BaseBase$0.0001100%daydreams353d ago0x196463…9cce58
0xd1ca…e9e30x6482…b779BaseBase$0.0001100%daydreams353d ago0x1433a1…2a7801
0xd1ca…e9e30x6482…b779BaseBase$0.0001100%daydreams354d ago0x52a318…4b5605
0xd1ca…e9e30x6482…b779BaseBase$0.0001100%daydreams354d ago0x8ab7be…5e4e42
0xd1ca…e9e30x6482…b779BaseBase$0.0001100%daydreams355d ago0x8edfab…a6df74
0xd1ca…e9e30x6482…b779BaseBase$0.0001100%daydreams355d ago0xbf3503…4f7d74
0xd1ca…e9e30x6482…b779BaseBase$0.0001100%daydreams355d ago0x9522f8…4dd593
0xd1ca…e9e30x6482…b779BaseBase$0.0001100%daydreams355d ago0x08b896…0eeffe
0xd1ca…e9e30x6482…b779BaseBase$0.0001100%daydreams356d ago0xe8066f…ff7452
0xd1ca…e9e30x6482…b779BaseBase$0.0001100%daydreams356d ago0xd8c927…0176f4
0xd1ca…e9e30x6482…b779BaseBase$0.0001100%daydreams356d ago0xa2d59f…ef051b
0xd1ca…e9e30x6482…b779BaseBase$0.0001100%daydreams356d ago0x8edf42…95382d
0xd1ca…e9e30x6482…b779BaseBase$0.0001100%daydreams356d ago0x51610c…6bc658
0xd1ca…e9e30x6482…b779BaseBase$0.0001100%daydreams357d ago0x7457c1…1385b5
0xd1ca…e9e30x6482…b779BaseBase$0.0001100%daydreams357d ago0x9f9aa3…c74f26
0xd1ca…e9e30x6482…b779BaseBase$0.0001100%daydreams357d ago0x427e76…e2fb01
0xd1ca…e9e30x6482…b779BaseBase$0.0001100%daydreams358d ago0x5a1c10…2cd57e

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

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

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: 0xd1ca…e9e3

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