Scry use case · Agent route selection

All Scry use cases

Solana wallet to Twitter/X handle evidence

A route-selection page for agents that need public X-handle or Twitter-handle context for one Solana wallet when Scry coverage contains identity evidence.

Problem fit

The agent has one wallet and needs to know whether Scry has public identity context, X-handle linkage, known service context, confidence notes, and freshness timestamps. The job is evidence retrieval and routing, not reputation scoring.

Agent instruction

Use the single-wallet evidence dossier when the object is one wallet and the agent needs public identity context together with lineage, cluster, activity, confidence, and freshness metadata. Use funding-lineage or bundler-check only when identity context is not part of the job.

Route contract summary

Problem

The agent has one wallet and needs to know whether Scry has public identity context, X-handle linkage, known service context, confidence notes, and freshness timestamps. The job is evidence retrieval and routing, not reputation scoring.

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

  • Does Scry have public X-handle or Twitter-handle context for this wallet when covered?
  • Which identity, service, and cluster context should the agent inspect together?
  • How fresh is the identity and wallet evidence returned by the dossier route?
  • Should the agent use a full wallet dossier or a narrower funding/routing route?

Searcher phrases

  • solana wallet to twitter handle reverse lookup
  • solana wallet to twitter handle
  • solana wallet x handle lookup api
  • solana wallet x handle lookup
  • solana public trader wallet identity api
  • solana kol wallet identity lookup api

Endpoint

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

Agent answers

Does Scry have public X-handle or Twitter-handle context for this wallet when covered?

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 identity, service, and cluster context 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.

How fresh is the identity and wallet evidence returned by the dossier route?

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.

Should the agent use a full wallet dossier or a narrower funding/routing route?

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.