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.54M Roundhouse has indexed across 1,400,255 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%fluxa64d ago0xeecf8b…493442
0xd5df…cd1e0xfe80…47eeBaseBase$0.001100%fluxa64d ago0x8835da…64d80d
0xd5df…cd1e0xfe80…47eeBaseBase$0.001100%fluxa64d ago0xd14821…27e8ec
0xd5df…cd1e0xfe80…47eeBaseBase$0.001100%fluxa64d ago0xe306a2…563668
0xd5df…cd1e0xfe80…47eeBaseBase$0.001100%fluxa64d ago0xde3b47…d292e0
0xd5df…cd1e0xfe80…47eeBaseBase$0.001100%fluxa64d ago0xf14e3f…4039a6
0xd5df…cd1e0xfe80…47eeBaseBase$0.001100%fluxa64d ago0x027b60…cdda4e
0xd5df…cd1e0xfe80…47eeBaseBase$0.001100%fluxa65d ago0x08c26d…382e4b
0xd5df…cd1e0xfe80…47eeBaseBase$0.001100%fluxa65d ago0x14a38b…cd7210
0xd5df…cd1e0xfe80…47eeBaseBase$0.001100%fluxa65d ago0xc08d42…01ec60
0xd5df…cd1e0xfe80…47eeBaseBase$0.001100%fluxa65d ago0x9d1ba4…368a50
0xd5df…cd1e0xfe80…47eeBaseBase$0.001100%fluxa65d ago0xaaf93d…2f50b2
0xd5df…cd1e0xfe80…47eeBaseBase$0.001100%fluxa65d ago0xb92673…ddaf28
0xd5df…cd1e0xfe80…47eeBaseBase$0.001100%fluxa65d ago0x59c384…41a523
0xd5df…cd1e0xfe80…47eeBaseBase$0.001100%fluxa65d ago0xa84497…fa2433
0xd5df…cd1e0xfe80…47eeBaseBase$0.001100%fluxa65d ago0x32d9d5…2eb088
0xd5df…cd1e0xfe80…47eeBaseBase$0.001100%fluxa65d ago0x2afaa9…0bc743
0xd5df…cd1e0xfe80…47eeBaseBase$0.001100%fluxa65d ago0x2d0a91…06faae
0xd5df…cd1e0xfe80…47eeBaseBase$0.001100%fluxa65d ago0x6335f5…1b4b58
0xd5df…cd1e0xfe80…47eeBaseBase$0.001100%fluxa65d ago0x105ea8…d92f9d
0xd5df…cd1e0xfe80…47eeBaseBase$0.001100%fluxa65d ago0x549385…3c45ba
0xd5df…cd1e0xfe80…47eeBaseBase$0.001100%fluxa65d ago0xf745c9…decd8c
0xd5df…cd1e0xfe80…47eeBaseBase$0.001100%fluxa65d ago0x5a5bb1…979627
0xd5df…cd1e0xfe80…47eeBaseBase$0.001100%fluxa65d ago0xb99ec5…483d96
0xd5df…cd1e0xfe80…47eeBaseBase$0.001100%fluxa70d ago0x48ad63…4e446e

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.