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%daydreams342d ago0x7e4f90…9fc76f
0xd5ae…cd180x6482…b779BaseBase$0.0001100%daydreams342d ago0xff8e58…920184
0xd5ae…cd180x6482…b779BaseBase$0.0001100%daydreams342d ago0x0fabfc…6dea65
0xd5ae…cd180x6482…b779BaseBase$0.0001100%daydreams342d ago0xcfa850…4fe944
0xd5ae…cd180x6482…b779BaseBase$0.0001100%daydreams342d ago0x1ef3ab…f0a75b
0xd5ae…cd180x6482…b779BaseBase$0.0001100%daydreams342d ago0x60fdf8…5681f1
0xd5ae…cd180x6482…b779BaseBase$0.0001100%daydreams342d ago0x5927cb…4b64c7
0xd5ae…cd180x6482…b779BaseBase$0.0001100%daydreams342d ago0x65d7ad…143ad6
0xd5ae…cd180x6482…b779BaseBase$0.0001100%daydreams342d ago0x5a2434…c4678e
0xd5ae…cd180x6482…b779BaseBase$0.0001100%daydreams343d ago0xca0cfc…c84fe0
0xd5ae…cd180x6482…b779BaseBase$0.0001100%daydreams343d ago0x71dc08…195cc7
0xd5ae…cd180x6482…b779BaseBase$0.0001100%daydreams343d ago0x9e5a00…ec5df4
0xd5ae…cd180x6482…b779BaseBase$0.0001100%daydreams343d ago0x89dde5…a8fd6b
0xd5ae…cd180x6482…b779BaseBase$0.0001100%daydreams343d ago0xe79b9e…d00953
0xd5ae…cd180x6482…b779BaseBase$0.0001100%daydreams343d ago0xc11a11…829b55
0xd5ae…cd180x6482…b779BaseBase$0.0001100%daydreams343d ago0xf96206…224ebb
0xd5ae…cd180x6482…b779BaseBase$0.0001100%daydreams343d ago0x241fad…2c4d5a
0xd5ae…cd180x6482…b779BaseBase$0.0001100%daydreams343d ago0x4b64bb…cb1dbb
0xd5ae…cd180x6482…b779BaseBase$0.0001100%daydreams343d ago0xc0494b…188b50
0xd5ae…cd180x6482…b779BaseBase$0.0001100%daydreams343d ago0x5ce903…52e5c0
0xd5ae…cd180x6482…b779BaseBase$0.0001100%daydreams344d ago0xfd1d21…5ebcce
0xd5ae…cd180x6482…b779BaseBase$0.0001100%daydreams344d ago0x4a51e1…2ef97d
0xd5ae…cd180x6482…b779BaseBase$0.0001100%daydreams344d ago0xbe565b…ff7563
0xd5ae…cd180x6482…b779BaseBase$0.0001100%daydreams344d ago0x02d2e8…761957
0xd5ae…cd180x6482…b779BaseBase$0.0001100%daydreams344d ago0x183ea2…18f1b9

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.