# Scry Solana Wallet Intelligence

Agent-readable Solana wallet evidence via x402: one clear object per request, public discovery files, and no account setup.

## Canonical Public Entry Points

- Human page: https://solanahub.de/en/scry/agent-discovery/
- Machine JSON: https://solanahub.de/scry-agent-discovery.json
- Well-known machine JSON: https://solanahub.de/.well-known/scry-agent-discovery.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
- Use-case hub: https://solanahub.de/en/scry/use-cases/
- Question hub: https://solanahub.de/en/scry/questions/
- Service base: https://scry.solanahub.de

## Public Discovery Files

- SOLANA HUB agent card: https://solanahub.de/.well-known/agent-card.json
  - A2A-style machine card describing the Scry discovery router, x402 evidence API, route manifests, quality gates, and skills.
- SOLANA HUB agent.json alias: https://solanahub.de/.well-known/agent.json
  - Compatibility alias for agents that probe the A2A-style /.well-known/agent.json path.
- Agent guide: https://scry.solanahub.de/x402/agent-guide.json
  - Primary machine guide with route templates, payment requirements, and response shapes.
- Product catalog: https://scry.solanahub.de/x402/products.json
  - Catalog of payable x402 products and resource objects.
- Discovery JSON: https://scry.solanahub.de/x402/discovery.json
  - Crawler-facing service discovery surface.
- OpenAPI: https://scry.solanahub.de/openapi.json
  - HTTP schema for integration tooling.
- Route contract manifest: https://solanahub.de/scry-route-contracts.json
  - Compact machine manifest of every Scry use-case route contract, buyer intent, best route, and evidence fields.
- Well-known route contract manifest: https://solanahub.de/.well-known/scry-route-contracts.json
  - Stable well-known alias for crawlers that prefer contract manifests under /.well-known/.
- Agent answers manifest: https://solanahub.de/scry-agent-answers.json
  - Question-to-route answer manifest for agents mapping Solana wallet and mint questions to Scry x402 evidence routes.
- Well-known agent answers manifest: https://solanahub.de/.well-known/scry-agent-answers.json
  - Stable well-known alias for crawlers that prefer answer manifests under /.well-known/.
- Buyer intent index: https://solanahub.de/scry-buyer-intent-index.json
  - English query-to-route index mapping buyer and agent phrases to Scry use cases, route templates, evidence fields, and payment boundaries.
- Well-known buyer intent index: https://solanahub.de/.well-known/scry-buyer-intent-index.json
  - Stable well-known alias for agents that probe intent indexes under /.well-known/.
- Agent question index: https://solanahub.de/scry-agent-question-index.json
  - Answer-first machine index mapping concrete Solana wallet-intelligence questions to Scry use cases, route contracts, x402 routes, and evidence fields.
- Well-known agent question index: https://solanahub.de/.well-known/scry-agent-question-index.json
  - Stable well-known alias for agents that probe question-answer indexes under /.well-known/.
- External discovery readiness: https://scry.solanahub.de/x402/external-discovery-readiness.json
  - Read-only crawl and registry packet with listing metadata, route-selection links, registry target names, and claim boundaries.
- Well-known external discovery readiness: https://scry.solanahub.de/.well-known/scry-external-discovery-readiness.json
  - Stable well-known alias for crawlers that prefer discovery under /.well-known/.
- Coverage snapshot: https://scry.solanahub.de/x402/coverage.json
  - Aggregate read-only coverage snapshot so agents can inspect indexed wallet, edge, cluster, identity, and cache coverage before payment.
- Freshness SLA: https://scry.solanahub.de/x402/freshness-sla.json
  - Machine-readable freshness targets, observed timestamps, stale checks, and claim boundaries for Scry evidence dimensions.
- Well-known freshness SLA: https://scry.solanahub.de/.well-known/scry-freshness-sla.json
  - Stable well-known alias for crawlers that prefer freshness and quality gates under /.well-known/.

## Agent Use-Case Hub

- Public page: https://solanahub.de/en/scry/use-cases/
- Description: English route-selection hub for agents matching Solana wallet, funding-lineage, Pump.fun cohort, and orchestrator questions to the right Scry x402 evidence route.

## Agent Route Map

### Solana wallet evidence dossier API

- Public page: https://solanahub.de/en/scry/solana-wallet-evidence-dossier-api/
- Request object: one Solana wallet
- Primary route: GET https://scry.solanahub.de/x402/wallet/:address/forensics
- Query alias: GET https://scry.solanahub.de/x402/wallet-forensics?address=:address
- Payment rail: x402 v2 exact-scheme USDC
- Advertised amount: $0.05 USDC
- Max atomic USDC: 50000
- 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.
- Intent phrases: solana wallet forensics; solana wallet evidence dossier; full Solana wallet evidence dossier; one wallet solana evidence dossier; solana wallet forensic dossier; solana wallet x handle lookup api; solana wallet to twitter handle reverse lookup
- 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

### Solana wallet source-of-funds API

- Public page: https://solanahub.de/en/scry/wallet-source-of-funds-api/
- Request object: one wallet funding chain
- Primary route: GET https://scry.solanahub.de/x402/wallet/:address/lineage
- Query alias: GET https://scry.solanahub.de/x402/wallet-lineage?address=:address
- Payment rail: x402 v2 exact-scheme USDC
- Advertised amount: $0.10 USDC
- Max atomic USDC: 100000
- Use when: The agent needs upstream funders, timestamps, confidence notes, and known service context for one wallet.
- Not for: Not for a full behavioral dossier or a transfer-window tape.
- Intent phrases: who funded this solana wallet; solana wallet funding lineage; wallet source of funds evidence; upstream funders solana wallet
- Evidence fields: cached upstream funder evidence; funding hop depth; known service and identity hints when covered; confidence notes; lineage cache freshness

### Solana wallet bundler check API

- Public page: https://solanahub.de/en/scry/solana-wallet-bundler-check-api/
- Request object: one wallet routing pattern
- Primary route: GET https://scry.solanahub.de/x402/wallet/:address/bundler-check
- Query alias: GET https://scry.solanahub.de/x402/wallet-bundler-check?address=:address
- Payment rail: x402 v2 exact-scheme USDC
- Advertised amount: $0.01 USDC
- Max atomic USDC: 10000
- Use when: The agent needs a wallet-level prefilter for bundler, tip-service, private-routing, service quarantine, identity, and freshness context.
- Not for: Not for a full wallet dossier, mint review, or launch-window cohort.
- Intent phrases: solana wallet bundler check; solana wallet private routing check; wallet tip service evidence api; bundler pattern solana wallet api
- Evidence fields: bundler and tip-service pattern context; primary service when covered; service quarantine state; identity context when indexed; coverage and freshness metadata

### Pump.fun risk-protection API

- Public page: https://solanahub.de/en/scry/pumpfun-risk-protection-api/
- Request object: wallet cohort around a launch or repeated pattern
- Primary route: GET https://scry.solanahub.de/x402/solana/pumpfun-risk-protection
- Query alias: GET https://scry.solanahub.de/x402/solana/pumpfun/risk-protection
- Payment rail: x402 v2 exact-scheme USDC
- Advertised amount: $0.05 USDC
- Max atomic USDC: 50000
- Use when: The agent needs launch-window cohort context, serial deployer patterns, service routing, and activity evidence.
- Not for: Not for a single-wallet dossier or one-mint creator/holder review.
- Intent phrases: pumpfun wallet cohort evidence; pumpfun rugger wallet detection; serial deployer wallet api; solana launch wallet analysis
- Evidence fields: wallet cohort candidates; rugger-pattern and serial-deployer context; service-router quarantine context; identity and activity context when covered; RPC sample coverage and freshness

### Solana memecoin mint-risk API

- Public page: https://solanahub.de/en/scry/solana-memecoin-mint-risk-api/
- Request object: one Solana mint
- Primary route: GET https://scry.solanahub.de/x402/mint/:mint/risk
- Query alias: GET https://scry.solanahub.de/x402/mint-risk?mint=:mint
- Payment rail: x402 v2 exact-scheme USDC
- Advertised amount: $0.03 USDC
- Max atomic USDC: 30000
- Use when: The agent needs one-mint evidence before escalating to a launch dossier or creator-wallet review.
- Not for: Not for a wallet cohort or one wallet in depth.
- Intent phrases: solana memecoin mint risk api; pumpfun mint risk preflight; solana token rug evidence api; creator wallet context for solana mint
- Evidence fields: holder concentration proxy; creator-wallet context; dev-wallet activity context; token age and liquidity coverage; checked and missing evidence fields

### Agent orchestrator Solana wallet intelligence API

- Public page: https://solanahub.de/en/scry/agent-orchestrator-solana-wallet-intelligence-api/
- Request object: aggregated agent feed
- Primary route: GET https://scry.solanahub.de/x402/solana/agent-intel-brief
- Query alias: GET https://scry.solanahub.de/x402/agent-intel-brief
- Payment rail: x402 v2 exact-scheme USDC
- Advertised amount: $0.29 USDC
- Max atomic USDC: 290000
- Use when: The agent needs a compact Solana wallet-intelligence picture with 24h/7d context, data cutoffs, and next evidence depth.
- Not for: Not for an ad-hoc single-wallet question.
- Intent phrases: agent orchestrator solana wallet intelligence; x402 solana wallet intelligence api; pay per request wallet intelligence; scry x402 api
- Evidence fields: 24h and 7d wallet context; database freshness and data cutoffs; coverage gaps and refresh queue context; product-ladder route recommendations; next evidence depth notes

## Agent Use-Case Pages

### Solana wallet evidence dossier for agents

- Public page: https://solanahub.de/en/scry/use-cases/solana-wallet-evidence-dossier/
- Primary intent: solana wallet evidence dossier
- Best route id: single-wallet-forensics
- 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.
- 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.
- Search 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
- 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?

### Solana wallet bundler and private-routing evidence

- Public page: https://solanahub.de/en/scry/use-cases/solana-wallet-bundler-private-routing-evidence/
- Primary intent: solana wallet bundler private routing evidence
- Best route id: wallet-bundler-check
- Problem: The agent has one wallet and needs routing-pattern context before requesting a deeper dossier. The job is not to score the wallet; it is to decide whether bundler, tip-service, private-routing, service-quarantine, and identity evidence are covered enough to continue.
- Agent instruction: Use the wallet bundler check when the object is one wallet and the next decision is whether routing-pattern evidence exists. Escalate to the single-wallet dossier only when the agent needs broader lineage, cluster, activity, and identity context.
- Search phrases: solana wallet bundler private routing evidence; solana wallet bundler check api; solana private routing wallet evidence; wallet tip service evidence api; solana wallet service quarantine check
- Questions answered: Does the wallet have indexed bundler or tip-service context?; Is the wallet associated with known service routing patterns?; Does Scry have identity context or coverage confidence for this wallet?; Is a deeper single-wallet evidence dossier the next fit?

### Solana wallet source-of-funds evidence

- Public page: https://solanahub.de/en/scry/use-cases/solana-wallet-source-of-funds-evidence/
- Primary intent: solana wallet source of funds evidence
- Best route id: wallet-funding-lineage
- Problem: The agent has one wallet and needs to understand where funding came from, how many hops are covered, which known service or identity hints appear, and how fresh the lineage cache is.
- Agent instruction: Use the funding-lineage route when the object is the wallet funding chain. Use the full wallet dossier only when the agent also needs cluster membership, coordination peers, activity, and broader identity context.
- Search phrases: solana wallet source of funds evidence; who funded this solana wallet; solana wallet funding lineage api; upstream funders solana wallet; solana wallet lineage evidence
- Questions answered: Which upstream funders are covered by the cache?; How deep is the funding lineage for this wallet?; Are known service or identity hints available?; How fresh is the lineage evidence?

### Solana wallet to Twitter/X handle evidence

- Public page: https://solanahub.de/en/scry/use-cases/solana-wallet-to-twitter-handle-evidence/
- Primary intent: solana wallet to twitter handle reverse lookup
- Best route id: single-wallet-forensics
- 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.
- 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.
- Search 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
- 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?

### Solana wallet cluster and coordination peer evidence

- Public page: https://solanahub.de/en/scry/use-cases/solana-wallet-cluster-coordination-peer-evidence/
- Primary intent: solana wallet cluster and coordination peer api
- Best route id: single-wallet-forensics
- 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.
- 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.
- Search 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
- 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?

### Pump.fun wallet cohort evidence for agents

- Public page: https://solanahub.de/en/scry/use-cases/pumpfun-wallet-cohort-evidence/
- Primary intent: pumpfun wallet cohort evidence
- Best route id: pumpfun-wallet-cohort
- Problem: The agent is not asking about one wallet only. The object is a cohort around a launch window or repeated pattern, and the useful output is a set of candidate wallets with evidence fields, caveats, and freshness.
- Agent instruction: Use the Pump.fun cohort route when the object is a launch-window or repeated-pattern cohort. Use a single-wallet route only after the agent has selected one wallet for deeper evidence.
- Search phrases: pumpfun wallet cohort evidence; pumpfun serial deployer wallet evidence; pumpfun launch wallet analysis api; pumpfun rugger wallet detection; solana launch-window wallet cohort
- Questions answered: Which wallet cohort candidates are covered?; Are serial-deployer or repeated-pattern contexts present?; Which service-router and quarantine contexts appear?; What RPC sample coverage and freshness metadata should the agent read first?

### Solana memecoin mint-risk preflight evidence

- Public page: https://solanahub.de/en/scry/use-cases/solana-memecoin-mint-risk-preflight-evidence/
- Primary intent: solana memecoin mint risk preflight evidence
- Best route id: mint-risk
- Problem: The agent has one Solana mint and needs a compact evidence preflight before deciding whether deeper creator-wallet, launch-window, or wallet-cohort context is needed. The job is to inspect covered fields and missing evidence, not to produce a trading recommendation.
- Agent instruction: Use the mint-risk preflight route when the object is one Solana mint and the agent needs covered/missing evidence fields before deeper wallet or cohort work. Use the Pump.fun cohort route only when the object becomes a launch-window wallet set.
- Search phrases: solana memecoin mint risk preflight evidence; solana memecoin mint risk api; pumpfun mint risk preflight; solana token rug evidence api; creator wallet context for solana mint; solana token holder concentration api
- Questions answered: Which holder concentration and creator-wallet fields are covered for this mint?; Which dev-wallet activity, token-age, and liquidity coverage fields are present?; Which checked and missing evidence fields should the agent read before escalating?; When should the agent move from one-mint preflight to a wallet cohort or creator-wallet review?

### Agent orchestrator routing for Solana wallet intelligence

- Public page: https://solanahub.de/en/scry/use-cases/agent-orchestrator-solana-wallet-intelligence-routing/
- Primary intent: agent orchestrator solana wallet intelligence routing
- Best route id: agent-intel-brief
- Problem: The agent is orchestrating several Solana wallet-intelligence jobs and needs a compact routing layer: current context, data cutoffs, coverage gaps, and which Scry evidence depth fits next.
- Agent instruction: Use the agent-intel brief when the agent needs routing context before choosing a narrower wallet, mint, cohort, or lineage endpoint. Do not use it as a substitute for a one-wallet dossier when a specific wallet is already the object.
- Search phrases: agent orchestrator solana wallet intelligence routing; x402 solana wallet intelligence api for agents; pay per request wallet intelligence; scry x402 agent route selection; solana wallet intelligence brief api
- Questions answered: What 24h and 7d context is available for an agent workflow?; Which data cutoffs and coverage gaps should be read first?; Which Scry product depth is the next fit?; When should the agent request a wallet, mint, cohort, or lineage route?

## Agent Question Pages

### Who funded this Solana wallet?

- Public page: https://solanahub.de/en/scry/questions/who-funded-this-solana-wallet/
- Primary query: who funded this solana wallet
- Direct answer: Use the Scry wallet source-of-funds evidence route when the object is one wallet funding chain. It returns upstream funder evidence, hop depth, known service or identity hints when covered, confidence notes, and lineage freshness.
- Use case id: wallet-source-of-funds
- Intent phrases: who funded this solana wallet; solana wallet funding lineage; upstream funders solana wallet; solana wallet source of funds evidence

### How can an agent check who funded a Solana wallet?

- Public page: https://solanahub.de/en/scry/questions/how-to-check-who-funded-solana-wallet/
- Primary query: how to check who funded a solana wallet
- Direct answer: Use the Scry wallet source-of-funds evidence route when the agent needs upstream funder context for one wallet. It returns cached funder evidence, funding hop depth, known service or identity hints when covered, confidence notes, and lineage cache freshness.
- Use case id: wallet-source-of-funds
- Intent phrases: how to check who funded a solana wallet; find original funder solana wallet; solana wallet funding chain api; trace upstream wallet funders solana

### Can Scry map a Solana wallet to a Twitter or X handle?

- Public page: https://solanahub.de/en/scry/questions/solana-wallet-to-twitter-handle/
- Primary query: solana wallet to twitter handle
- Direct answer: Use the single-wallet evidence dossier when the object is one wallet and the agent needs public X-handle or Twitter-handle context together with identity, lineage, cluster, activity, confidence, and freshness metadata when covered.
- Use case id: wallet-x-handle-lookup
- Intent phrases: solana wallet to twitter handle; solana wallet x handle lookup api; solana wallet to twitter handle reverse lookup; solana public trader wallet identity api

### How can an agent find X-handle context for a Solana wallet?

- Public page: https://solanahub.de/en/scry/questions/find-solana-wallet-x-handle/
- Primary query: find solana wallet x handle
- Direct answer: Use the single-wallet evidence dossier when the object is one wallet and the agent needs public X-handle context together with wallet identity context, funding lineage, cluster evidence, activity, confidence notes, and freshness metadata when covered.
- Use case id: wallet-x-handle-lookup
- Intent phrases: find solana wallet x handle; solana wallet x account lookup; solana wallet public identity evidence; map solana wallet to public handle

### Which Scry route checks a Solana wallet for bundler or private-routing context?

- Public page: https://solanahub.de/en/scry/questions/solana-wallet-bundler-check/
- Primary query: solana wallet bundler check
- Direct answer: Use the wallet bundler and private-routing evidence route when the object is one wallet routing pattern. It returns bundler or tip-service context, primary service context when covered, quarantine state, identity context when indexed, coverage, and freshness metadata.
- Use case id: wallet-bundler-private-routing
- Intent phrases: solana wallet bundler check; solana wallet private routing check; wallet tip service evidence api; solana wallet service quarantine check

### How can an agent detect private-routing or tip-service context for a Solana wallet?

- Public page: https://solanahub.de/en/scry/questions/detect-solana-wallet-private-routing/
- Primary query: detect solana wallet private routing
- Direct answer: Use the wallet bundler and private-routing evidence route when the object is one wallet routing pattern. It returns bundler and tip-service pattern context, primary service context when covered, service quarantine state, identity context when indexed, and source freshness metadata.
- Use case id: wallet-bundler-private-routing
- Intent phrases: detect solana wallet private routing; solana wallet tip service context; solana wallet router quarantine evidence; jito tip service wallet context solana

### Which Scry route returns a full Solana wallet evidence dossier?

- Public page: https://solanahub.de/en/scry/questions/solana-wallet-evidence-dossier-api/
- Primary query: solana wallet evidence dossier api
- Direct answer: Use the single-wallet evidence dossier when the object is one Solana wallet and the agent needs the broadest available evidence bundle: identity context when covered, funding lineage, SOL-flow graph, coordination peers, cluster membership, confidence, and source freshness.
- Use case id: single-wallet-evidence-dossier
- Intent phrases: solana wallet evidence dossier api; full solana wallet evidence dossier; one wallet solana evidence dossier; solana wallet forensic dossier

### What evidence does Scry return for one Solana wallet?

- Public page: https://solanahub.de/en/scry/questions/what-evidence-does-scry-return-for-one-solana-wallet/
- Primary query: what evidence does scry return for one solana wallet
- Direct answer: Use the single-wallet evidence dossier when the agent needs one wallet in depth. It returns wallet identity context when covered, service/router/exchange quarantine context, funding-source lineage, SOL-flow graph and coordination peers, cluster membership, coverage confidence, and source freshness timestamps.
- Use case id: single-wallet-evidence-dossier
- Intent phrases: what evidence does scry return for one solana wallet; one solana wallet evidence fields; solana wallet dossier returned fields; solana wallet identity lineage cluster evidence

### Which Scry route shows Solana wallet cluster and coordination peer evidence?

- Public page: https://solanahub.de/en/scry/questions/solana-wallet-coordination-peers/
- Primary query: solana wallet coordination peers
- Direct answer: Use the single-wallet evidence dossier when the object is one wallet and the agent needs cluster membership, coordination peers, SOL-flow relationships, service context, confidence notes, and freshness timestamps together.
- Use case id: wallet-cluster-coordination-peers
- Intent phrases: solana wallet coordination peers; solana wallet cluster evidence; solana wallet sol-flow graph; connected wallet context solana api

### How can an agent find connected Solana wallets around one wallet?

- Public page: https://solanahub.de/en/scry/questions/find-connected-solana-wallets/
- Primary query: find connected solana wallets
- Direct answer: Use the single-wallet evidence dossier when the object is one wallet and the agent needs connected-wallet context. It returns SOL-flow relationships, coordination peers, cluster membership, service context, confidence notes, and freshness timestamps together.
- Use case id: wallet-cluster-coordination-peers
- Intent phrases: find connected solana wallets; solana wallet relationship graph; solana wallet coordination cluster api; solana connected wallet evidence

### Which Scry route maps a Pump.fun wallet cohort?

- Public page: https://solanahub.de/en/scry/questions/pumpfun-wallet-cohort-evidence/
- Primary query: pumpfun wallet cohort evidence
- Direct answer: Use the Pump.fun wallet cohort evidence route when the object is a launch-window or repeated-pattern cohort. It returns candidate wallets, serial-deployer context, service-router context, identity or activity context when covered, RPC sample coverage, and freshness metadata.
- Use case id: pumpfun-wallet-cohort
- Intent phrases: pumpfun wallet cohort evidence; pumpfun serial deployer wallet evidence; pumpfun launch wallet analysis api; solana launch-window wallet cohort

### How can an agent review wallets around a Pump.fun launch?

- Public page: https://solanahub.de/en/scry/questions/analyze-pumpfun-launch-wallets/
- Primary query: analyze pumpfun launch wallets
- Direct answer: Use the Pump.fun wallet cohort evidence route when the object is a launch-window or repeated-pattern cohort. It returns candidate wallets, serial-deployer context, service-router context, identity or activity context when covered, RPC sample coverage, and freshness metadata.
- Use case id: pumpfun-wallet-cohort
- Intent phrases: analyze pumpfun launch wallets; pumpfun launch window wallets; pumpfun wallet cohort api; pumpfun repeated deployer wallet context

### Which Scry route gives a Solana memecoin mint evidence preflight?

- Public page: https://solanahub.de/en/scry/questions/solana-memecoin-mint-risk-preflight/
- Primary query: solana memecoin mint risk preflight evidence
- Direct answer: Use the Solana memecoin mint-risk preflight route when the object is one mint. It returns holder concentration proxy, creator-wallet context, dev-wallet activity context, token age and liquidity coverage, and checked or missing evidence fields.
- Use case id: memecoin-mint-risk-preflight
- Intent phrases: solana memecoin mint risk preflight evidence; solana memecoin mint risk api; pumpfun mint risk preflight; creator wallet context for solana mint

### How can an agent check creator-wallet context for a Solana mint?

- Public page: https://solanahub.de/en/scry/questions/check-solana-mint-creator-wallet-context/
- Primary query: check solana mint creator wallet context
- Direct answer: Use the Solana memecoin mint-risk preflight route when the object is one mint. It returns holder concentration proxy, creator-wallet context, dev-wallet activity context, token age and liquidity coverage, and checked or missing evidence fields.
- Use case id: memecoin-mint-risk-preflight
- Intent phrases: check solana mint creator wallet context; solana mint creator wallet evidence; solana token creator wallet context api; solana mint dev wallet activity evidence

### Which Scry route should an orchestrator agent call before choosing wallet, mint, cohort, or lineage depth?

- Public page: https://solanahub.de/en/scry/questions/x402-solana-wallet-intelligence-api/
- Primary query: x402 solana wallet intelligence api
- Direct answer: Use the agent orchestrator Solana wallet intelligence brief when the agent needs a compact routing layer first: 24h and 7d context, data cutoffs, coverage gaps, product-ladder route recommendations, and next evidence depth notes.
- Use case id: agent-orchestrator-wallet-intelligence
- Intent phrases: x402 solana wallet intelligence api; agent orchestrator solana wallet intelligence routing; pay per request wallet intelligence; scry x402 agent route selection

### How should an agent choose the right Scry wallet intelligence route?

- Public page: https://solanahub.de/en/scry/questions/choose-solana-wallet-intelligence-route/
- Primary query: choose solana wallet intelligence route
- Direct answer: Use the agent orchestrator Solana wallet intelligence brief when the agent has not yet selected the object depth. It returns compact 24h and 7d context, data cutoffs, coverage gaps, product-ladder route recommendations, and next evidence depth notes.
- Use case id: agent-orchestrator-wallet-intelligence
- Intent phrases: choose solana wallet intelligence route; which scry endpoint should an agent call; x402 solana evidence route selection; agent router for solana wallet intelligence

## Manual Dossier Paths

- Scry Forensics Dossier: https://solanahub.de/en/intel/pricing/
  - Price: $249 one-time
  - Use when: Use when a human-readable report is needed with evidence, caveats, confidence, and a concise narrative.
- Priority Case: https://solanahub.de/en/planet/intake/?package=scry_priority_case
  - Price: from $799
  - Use when: Use when timing, reputation sensitivity, or manual triage matters more than automated endpoint depth.

## Agent Posture

- Evidence layer only; not financial, investment, or trading advice.
- Discovery files are public; evidence routes require valid x402 payment.
- Agents should inspect payment requirements first and submit a fresh payment payload per paid request.
- Coverage changes as the index refreshes; use source freshness timestamps and confidence notes.