AgentReport

0xd5df…cd1e

0xd5df5dbe0e7d429f8be5ef58923a76cd6727cd1eExplorer
Paid out
$0.78
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
779
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $0.78 of the $3066.17M Roundhouse has indexed across 1,400,092 wallets — less than 0.0001% of it.

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

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

$0.78 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.

  • 0xfe80…47ee · last paid 61d ago
    $0.53
    529 calls

    This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.

  • 0x9c95…e299 · last paid 77d ago
    $0.25
    250 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
0xfe80…47ee$0.53$0.0052961d agoGraph
0x9c95…e299$0.25$0.0025077d agoGraph

Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.

Data quality

68% of observed volume is with a single counterparty, in all 779 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xd5df…cd1e0xfe80…47eeBaseBase$0.001100%fluxa62d ago0xf8eb0c…bda63c
0xd5df…cd1e0xfe80…47eeBaseBase$0.001100%fluxa62d ago0xf3cdf4…4bbccb
0xd5df…cd1e0xfe80…47eeBaseBase$0.001100%fluxa62d ago0x4c304e…571222
0xd5df…cd1e0xfe80…47eeBaseBase$0.001100%fluxa62d ago0xacb91f…59c543
0xd5df…cd1e0xfe80…47eeBaseBase$0.001100%fluxa62d ago0xc86e89…cd73d4
0xd5df…cd1e0xfe80…47eeBaseBase$0.001100%fluxa62d ago0xfacbcb…1c69d5
0xd5df…cd1e0xfe80…47eeBaseBase$0.001100%fluxa62d ago0x408950…1d4a9e
0xd5df…cd1e0xfe80…47eeBaseBase$0.001100%fluxa62d ago0x29d5e6…9ab1a1
0xd5df…cd1e0xfe80…47eeBaseBase$0.001100%fluxa62d ago0x159ce3…e47d36
0xd5df…cd1e0xfe80…47eeBaseBase$0.001100%fluxa62d ago0xa5f58b…1ff1fa
0xd5df…cd1e0xfe80…47eeBaseBase$0.001100%fluxa62d ago0x7594a1…b01e61
0xd5df…cd1e0xfe80…47eeBaseBase$0.001100%fluxa62d ago0x126fa0…a333e9
0xd5df…cd1e0xfe80…47eeBaseBase$0.001100%fluxa62d ago0x2fab16…4a7d5c
0xd5df…cd1e0xfe80…47eeBaseBase$0.001100%fluxa62d ago0x2854dd…6f6b74
0xd5df…cd1e0xfe80…47eeBaseBase$0.001100%fluxa62d ago0xa0af23…25539d
0xd5df…cd1e0xfe80…47eeBaseBase$0.001100%fluxa62d ago0x60ba10…ac0d0c
0xd5df…cd1e0xfe80…47eeBaseBase$0.001100%fluxa62d ago0x5cba64…139b23
0xd5df…cd1e0xfe80…47eeBaseBase$0.001100%fluxa62d ago0x7dab07…e5c788
0xd5df…cd1e0xfe80…47eeBaseBase$0.001100%fluxa62d ago0x44bd3c…3c3dbd
0xd5df…cd1e0xfe80…47eeBaseBase$0.001100%fluxa62d ago0xe3526e…35fa46
0xd5df…cd1e0xfe80…47eeBaseBase$0.001100%fluxa62d ago0x68d41a…e8884f
0xd5df…cd1e0xfe80…47eeBaseBase$0.001100%fluxa62d ago0x4b50ac…272cb3
0xd5df…cd1e0xfe80…47eeBaseBase$0.001100%fluxa63d ago0x8ff189…624009
0xd5df…cd1e0xfe80…47eeBaseBase$0.001100%fluxa63d ago0xe08508…4017aa
0xd5df…cd1e0xfe80…47eeBaseBase$0.001100%fluxa63d ago0xd8db89…8f39ad

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

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

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: 0xd5df…cd1e

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