SOLANA·HUB

Scry use case · Agent route selection

All Scry use cases

Solana wallet evidence dossier for agents

A route-selection page for agents that need identity context, funding lineage, cluster evidence, activity, holdings coverage, confidence, and source freshness for one Solana wallet.

Problem fit

The agent has one Solana wallet and needs the broadest wallet evidence bundle Scry can provide: public identity context when covered, funding lineage, cluster membership, coordination peers, activity context, holdings coverage when available, confidence notes, and freshness timestamps. The job is evidence retrieval and routing, not a recommendation.

Agent instruction

Use the single-wallet evidence dossier when the object is one Solana wallet and the agent needs the broadest available evidence bundle. Use narrower routes only when the job is specifically funding lineage, routing-pattern context, or identity lookup.

Route contract summary

Problem

The agent has one Solana wallet and needs the broadest wallet evidence bundle Scry can provide: public identity context when covered, funding lineage, cluster membership, coordination peers, activity context, holdings coverage when available, confidence notes, and freshness timestamps. The job is evidence retrieval and routing, not a recommendation.

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 identity, funding-lineage, cluster, and activity evidence is covered for this wallet?
  • Which coordination peers, SOL-flow context, and holdings fields should the agent inspect together?
  • What coverage confidence and source freshness should be read before using the response?
  • When should the agent use narrower funding-lineage, bundler-check, or identity lookup routes instead?

Searcher phrases

  • solana wallet evidence dossier
  • solana wallet evidence dossier api
  • full solana wallet evidence dossier
  • one wallet solana evidence dossier
  • solana wallet forensic dossier
  • solana wallet full context api
  • solana wallet evidence bundle

Endpoint

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

Agent answers

Which identity, funding-lineage, cluster, and activity evidence 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, SOL-flow context, and holdings fields should the agent inspect together?

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.

What coverage confidence and source freshness should be read before using the response?

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.

When should the agent use narrower funding-lineage, bundler-check, or identity lookup routes instead?

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

Solana wallet source-of-funds API

one wallet funding chain

Solana wallet bundler check API

one wallet routing pattern

Machine-readable discovery

Scry agent card

https://solanahub.de/.well-known/agent-card.json

Scry agent.json alias

https://solanahub.de/.well-known/agent.json

Route contract manifest

https://solanahub.de/scry-route-contracts.json

Well-known route contract manifest

https://solanahub.de/.well-known/scry-route-contracts.json

Agent answers manifest

https://solanahub.de/scry-agent-answers.json

Well-known agent answers manifest

https://solanahub.de/.well-known/scry-agent-answers.json

Buyer intent index

https://solanahub.de/scry-buyer-intent-index.json

Well-known buyer intent index

https://solanahub.de/.well-known/scry-buyer-intent-index.json

Agent question index

https://solanahub.de/scry-agent-question-index.json

Well-known agent question index

https://solanahub.de/.well-known/scry-agent-question-index.json

Scry agent machine map

https://solanahub.de/scry-agent-discovery.json

Scry markdown map

https://solanahub.de/scry-agent-discovery.md

x402 external discovery readiness

https://scry.solanahub.de/x402/external-discovery-readiness.json

x402 coverage snapshot

https://scry.solanahub.de/x402/coverage.json

x402 freshness SLA

https://scry.solanahub.de/x402/freshness-sla.json

x402 well-known freshness SLA

https://scry.solanahub.de/.well-known/scry-freshness-sla.json

x402 agent guide

https://scry.solanahub.de/x402/agent-guide.json
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.