AgentReport

0xd5ae…cd18

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

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

$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
    252 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.00252277d 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 252 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xd5ae…cd180x6482…b779BaseBase$0.0001100%daydreams346d ago0xd07c4f…3ebb82
0xd5ae…cd180x6482…b779BaseBase$0.0001100%daydreams346d ago0x19d30c…166b3e
0xd5ae…cd180x6482…b779BaseBase$0.0001100%daydreams347d ago0xf94458…9dce16
0xd5ae…cd180x6482…b779BaseBase$0.0001100%daydreams347d ago0x3fa155…a9e787
0xd5ae…cd180x6482…b779BaseBase$0.0001100%daydreams347d ago0x713d1e…9b144b
0xd5ae…cd180x6482…b779BaseBase$0.0001100%daydreams347d ago0xf26721…db973d
0xd5ae…cd180x6482…b779BaseBase$0.0001100%daydreams347d ago0x255a87…87b3a3
0xd5ae…cd180x6482…b779BaseBase$0.0001100%daydreams347d ago0x390023…b23040
0xd5ae…cd180x6482…b779BaseBase$0.0001100%daydreams347d ago0x18063d…7f13b9
0xd5ae…cd180x6482…b779BaseBase$0.0001100%daydreams348d ago0x01e3ab…ffe88e
0xd5ae…cd180x6482…b779BaseBase$0.0001100%daydreams348d ago0x9e99d3…2d2485
0xd5ae…cd180x6482…b779BaseBase$0.0001100%daydreams348d ago0x2fc32d…38669d
0xd5ae…cd180x6482…b779BaseBase$0.0001100%daydreams348d ago0xdafa5a…11eec9
0xd5ae…cd180x6482…b779BaseBase$0.0001100%daydreams348d ago0xda616e…3fece1
0xd5ae…cd180x6482…b779BaseBase$0.0001100%daydreams348d ago0x1780c9…8acfff
0xd5ae…cd180x6482…b779BaseBase$0.0001100%daydreams348d ago0xe28515…825cb5
0xd5ae…cd180x6482…b779BaseBase$0.0001100%daydreams348d ago0x171977…502997
0xd5ae…cd180x6482…b779BaseBase$0.0001100%daydreams348d ago0x531c3e…8938dc
0xd5ae…cd180x6482…b779BaseBase$0.0001100%daydreams348d ago0xa38666…f8cc77
0xd5ae…cd180x6482…b779BaseBase$0.0001100%daydreams348d ago0xc73fca…352b03
0xd5ae…cd180x6482…b779BaseBase$0.0001100%daydreams349d ago0x45ca29…9af087
0xd5ae…cd180x6482…b779BaseBase$0.0001100%daydreams349d ago0xc7207b…2ea1cb
0xd5ae…cd180x6482…b779BaseBase$0.0001100%daydreams349d ago0xff02de…29acb6
0xd5ae…cd180x6482…b779BaseBase$0.0001100%daydreams349d ago0xd1682c…a3df01
0xd5ae…cd180x6482…b779BaseBase$0.0001100%daydreams349d ago0x41387b…765507

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

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

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: 0xd5ae…cd18

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