AgentReport

0x5d4d…0afd

0x5d4d8b3518bf4d4c9caae75daa494cc5a65d0afdExplorer
Paid out
$0.97
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
967
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

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

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

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

$0.97 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 43d ago
    $0.83
    830 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 78d ago
    $0.14
    137 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.83$0.0083043d agoGraph
0x9c95…e299$0.14$0.0013778d agoGraph

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

Data quality

86% of observed volume is with a single counterparty, in all 967 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x5d4d…0afd0xfe80…47eeBaseBase$0.001100%fluxa44d ago0x553803…ab738f
0x5d4d…0afd0xfe80…47eeBaseBase$0.001100%fluxa44d ago0x4314ea…c98196
0x5d4d…0afd0xfe80…47eeBaseBase$0.001100%fluxa44d ago0x5da312…7ff137
0x5d4d…0afd0xfe80…47eeBaseBase$0.001100%fluxa44d ago0xadd11d…f41855
0x5d4d…0afd0xfe80…47eeBaseBase$0.001100%fluxa44d ago0xb3430d…30d772
0x5d4d…0afd0xfe80…47eeBaseBase$0.001100%fluxa44d ago0x4533da…3dec92
0x5d4d…0afd0xfe80…47eeBaseBase$0.001100%fluxa44d ago0x966236…139f26
0x5d4d…0afd0xfe80…47eeBaseBase$0.001100%fluxa44d ago0xce6d93…3d54e3
0x5d4d…0afd0xfe80…47eeBaseBase$0.001100%fluxa44d ago0x9e7060…0d8256
0x5d4d…0afd0xfe80…47eeBaseBase$0.001100%fluxa44d ago0x84fc4d…df4026
0x5d4d…0afd0xfe80…47eeBaseBase$0.001100%fluxa44d ago0x6ec8cd…c3976e
0x5d4d…0afd0xfe80…47eeBaseBase$0.001100%fluxa44d ago0x3f82e0…7f3ad8
0x5d4d…0afd0xfe80…47eeBaseBase$0.001100%fluxa44d ago0xe14357…bdf892
0x5d4d…0afd0xfe80…47eeBaseBase$0.001100%fluxa44d ago0x0f920e…40a27d
0x5d4d…0afd0xfe80…47eeBaseBase$0.001100%fluxa44d ago0x76de66…85bbd0
0x5d4d…0afd0xfe80…47eeBaseBase$0.001100%fluxa44d ago0x45b480…bdc8d4
0x5d4d…0afd0xfe80…47eeBaseBase$0.001100%fluxa44d ago0x06a112…be545f
0x5d4d…0afd0xfe80…47eeBaseBase$0.001100%fluxa44d ago0xb0fa38…ab7d21
0x5d4d…0afd0xfe80…47eeBaseBase$0.001100%fluxa44d ago0xbf8592…d4e550
0x5d4d…0afd0xfe80…47eeBaseBase$0.001100%fluxa44d ago0x37f80b…3737fc
0x5d4d…0afd0xfe80…47eeBaseBase$0.001100%fluxa44d ago0xe9e191…43e0a5
0x5d4d…0afd0xfe80…47eeBaseBase$0.001100%fluxa44d ago0x232d56…98488e
0x5d4d…0afd0xfe80…47eeBaseBase$0.001100%fluxa44d ago0xbb17bf…566a8f
0x5d4d…0afd0xfe80…47eeBaseBase$0.001100%fluxa44d ago0xbee165…b4321b
0x5d4d…0afd0xfe80…47eeBaseBase$0.001100%fluxa44d ago0xfaac16…a9f008

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

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

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: 0x5d4d…0afd

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