AgentReport

DYAME6NxWkVT5ej93gwsUuYKx4RhbXSAUfA6Htq7C3SP

DYAME6NxWkVT5ej93gwsUuYKx4RhbXSAUfA6Htq7C3SPExplorer
$0.16
Paid out
$0.00
Received
2
Settlements
1
Distinct counterparties
Over the whole indexed history

Paid $0.16 of the $3225.84M Roundhouse has indexed across 1,450,293 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
Reference Data100%$0.1621

Every merchant paid publishes at least one catalogued endpoint.

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.

  • Stock historical barsagent402.toolsEquity quote?Endpoint up
    J7aN3P…3xwg · last paid 45d ago
    $0.16
    2 calls
    ▸1 catalogued endpoints, none priced at an amount this agent paid

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
Solana token lookup (Jupiter)$0.16$0.00245d 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 $0.16 of $0.16 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
DYAME6…C3SPSolana token lookup (Jupiter)SolanaSolana$0.08100%coinbase45d ago2RMLUayE…cRLDB3
DYAME6…C3SPSolana token lookup (Jupiter)SolanaSolana$0.08100%coinbase45d ago5vi9iuqZ…mmTxio

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

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

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

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