SOLANA·HUB

Scry use case · Agent route selection

All Scry use cases

Solana wallet source-of-funds evidence

A route-selection page for agents that need upstream funder, funding-hop, service-context, confidence, and freshness evidence for one Solana wallet.

Problem fit

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.

Route contract summary

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.

Route

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

Response deliverable

The response returns cached upstream funder evidence, funding hop depth, known service and identity hints when covered, confidence notes, lineage cache freshness with coverage and freshness metadata.

Payment boundary

$0.10 USDC per x402 request; maxAtomicUSDC 100000.

Response deliverable

The response returns cached upstream funder evidence, funding hop depth, known service and identity hints when covered, confidence notes, lineage cache freshness with coverage and freshness metadata.

Route handoff

If the request object changes, compare related routes: Solana wallet evidence dossier API, Solana wallet bundler check API.

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?

Searcher 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

Endpoint

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

Agent answers

Which upstream funders are covered by the cache?

Wallet funding lineage is the route fit. Ask it when the object is one wallet funding chain; read cached upstream funder evidence, funding hop depth, known service and identity hints when covered plus coverage and freshness metadata before escalating.

How deep is the funding lineage for this wallet?

Wallet funding lineage is the route fit. Ask it when the object is one wallet funding chain; read cached upstream funder evidence, funding hop depth, known service and identity hints when covered plus coverage and freshness metadata before escalating.

Are known service or identity hints available?

Wallet funding lineage is the route fit. Ask it when the object is one wallet funding chain; read cached upstream funder evidence, funding hop depth, known service and identity hints when covered plus coverage and freshness metadata before escalating.

How fresh is the lineage evidence?

Wallet funding lineage is the route fit. Ask it when the object is one wallet funding chain; read cached upstream funder evidence, funding hop depth, known service and identity hints when covered plus coverage and freshness metadata before escalating.

Decision checklist

Request object
one wallet funding chain
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.
Payment rail
x402 v2 exact-scheme USDC
Advertised amount
$0.10 USDC per x402 request
Max atomic USDC
100000

Evidence fields

cached upstream funder evidence
funding hop depth
known service and identity hints when covered
confidence notes
lineage cache freshness

Related Scry routes

Solana wallet evidence dossier API

one Solana wallet

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.