Scry use case · Agent route selection

All Scry use cases

Solana wallet cluster and coordination peer evidence

A route-selection page for agents that need cluster membership, coordination peers, SOL-flow context, confidence, and source freshness for one Solana wallet.

Problem fit

The agent has one wallet and needs connected-wallet context: cluster membership, coordination peers, SOL-flow evidence, known service context, confidence notes, and freshness timestamps. The job is relationship evidence, not behavioral prediction.

Agent instruction

Use the single-wallet evidence dossier when the object is one wallet and the agent needs cluster, peer, SOL-flow, identity, activity, confidence, and freshness context together. Use funding-lineage only when upstream funders are the main object.

Route contract summary

Problem

The agent has one wallet and needs connected-wallet context: cluster membership, coordination peers, SOL-flow evidence, known service context, confidence notes, and freshness timestamps. The job is relationship evidence, not behavioral prediction.

Route

GET https://scry.solanahub.de/x402/wallet/:address/forensics

Response deliverable

The response returns wallet identity context when covered, service/router/exchange quarantine context, funding-source lineage evidence, SOL-flow graph and coordination peers, cluster membership and coverage confidence, source freshness timestamps with coverage and freshness metadata.

Payment boundary

$0.05 USDC per x402 request; maxAtomicUSDC 50000.

Response deliverable

The response returns wallet identity context when covered, service/router/exchange quarantine context, funding-source lineage evidence, SOL-flow graph and coordination peers, cluster membership and coverage confidence, source freshness timestamps with coverage and freshness metadata.

Route handoff

If the request object changes, compare related routes: Solana wallet source-of-funds API, Solana wallet bundler check API.

Questions answered

  • Which cluster or connected-wallet context is covered for this wallet?
  • Which coordination peers or SOL-flow relationships should the agent inspect?
  • Which service, identity, and lineage fields should be read alongside cluster evidence?
  • How fresh are the relationship and activity evidence fields?

Searcher phrases

  • solana wallet cluster and coordination peer api
  • solana wallet cluster evidence
  • solana wallet coordination peers
  • solana wallet network evidence api
  • solana wallet sol-flow graph
  • connected wallet context solana api

Endpoint

GET https://scry.solanahub.de/x402/wallet/:address/forensics GET https://scry.solanahub.de/x402/wallet-forensics?address=:address

Agent answers

Which cluster or connected-wallet context is covered for this wallet?

Single wallet evidence dossier is the route fit. Ask it when the object is one Solana wallet; read wallet identity context when covered, service/router/exchange quarantine context, funding-source lineage evidence plus coverage and freshness metadata before escalating.

Which coordination peers or SOL-flow relationships should the agent inspect?

Single wallet evidence dossier is the route fit. Ask it when the object is one Solana wallet; read wallet identity context when covered, service/router/exchange quarantine context, funding-source lineage evidence plus coverage and freshness metadata before escalating.

Which service, identity, and lineage fields should be read alongside cluster evidence?

Single wallet evidence dossier is the route fit. Ask it when the object is one Solana wallet; read wallet identity context when covered, service/router/exchange quarantine context, funding-source lineage evidence plus coverage and freshness metadata before escalating.

How fresh are the relationship and activity evidence fields?

Single wallet evidence dossier is the route fit. Ask it when the object is one Solana wallet; read wallet identity context when covered, service/router/exchange quarantine context, funding-source lineage evidence plus coverage and freshness metadata before escalating.

Decision checklist

Request object
one Solana wallet
Use when
The agent needs one wallet in depth: public identity context when covered, activity evidence, confidence, source freshness, and connected-wallet context.
Not for
Not for a token launch dossier, daily wallet cohort, or transfer-window-only review.
Payment rail
x402 v2 exact-scheme USDC
Advertised amount
$0.05 USDC per x402 request
Max atomic USDC
50000

Evidence fields

wallet identity context when covered
service/router/exchange quarantine context
funding-source lineage evidence
SOL-flow graph and coordination peers
cluster membership and coverage confidence
source freshness timestamps

Related Scry routes

Scry is an evidence layer. It is not financial, investment, or trading advice. Coverage changes as the index refreshes; agents should read source freshness timestamps, confidence notes, and payment requirements before requesting evidence.