AgentReport

D5dDfPFyyDX3eAkP9h4g11vPxwhjsi8iwA6GJTWsV8tt

D5dDfPFyyDX3eAkP9h4g11vPxwhjsi8iwA6GJTWsV8ttExplorer
$3.00
Paid out
$0.00
Received
2
Settlements
1
Distinct counterparties
Over the whole indexed history

Paid $3.00 of the $3245.99M Roundhouse has indexed across 1,459,829 wallets — less than 0.0001% of it.

Chains (from the recent scan): Solana (2)

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%$3.0021

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

  • BJGdsD…r7VQ · last paid 174d ago
    $3.00
    2 calls

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

Wallet balance

Not read. Solana wallets are not supported by the balance and funding-history read yet. Nothing is shown here about this wallet's balance or funding, which is not the same as it holding none.

Activity

MayJunJulAugSepOctNov
LessMore

One square per day; click a day to see its settlements in the ledger.

Frequent counterparties

CounterpartyPaid themReceived backSettlementsLast
BJGdsD…r7VQ$3.00$0.002174d 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 2 observed settlements.

Organic volume $3.00 of $3.00 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
D5dDfP…V8ttBJGdsD…r7VQSolanaSolana$2.15100%coinbase174d ago4ESS3aW8…v2ArQS
D5dDfP…V8ttBJGdsD…r7VQSolanaSolana$0.85100%coinbase174d ago3bEpp3GW…QYdiTj

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

GET api.roundhouseai.io/v0/agents/D5dDfPFyyDX3eAkP9h4g11vPxwhjsi8iwA6GJTWsV8tt

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: D5dDfPFyyDX3eAkP9h4g11vPxwhjsi8iwA6GJTWsV8tt

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