Scry · Evidence Layer

Evidence Layer for Solana Wallet Networks.

Scry assembles public on-chain traces into cluster evidence for Solana wallets: funding lineage, bundler signals, wallet relationships, service quarantine, and coverage gaps. Every product has one clear object — one mint, a wallet cohort, a single wallet, or a funding chain. Humans read the context here. Agents call the same evidence over x402 and pay per request — no API keys, no dashboard.

Status

x402 live

Status

Agent discovery live

Status

Evidence-only API

Status

No financial advice

Problem pages for agents

These pages map common agent questions to the Scry route that fits the object: one wallet, one funding chain, one cohort, or an orchestrator brief.

Open use-case hub

solana wallet evidence dossier

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.

solana wallet bundler private routing evidence

Solana wallet bundler and private-routing evidence

A route-selection page for agents investigating whether one Solana wallet shows bundler, tip-service, private-routing, service-quarantine, identity, and freshness context.

solana wallet source of funds evidence

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.

solana wallet to twitter handle reverse lookup

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.

solana wallet cluster and coordination peer api

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.

pumpfun wallet cohort evidence

Pump.fun wallet cohort evidence for agents

A route-selection page for agents that need Pump.fun launch-window cohort, serial-deployer, service-router, identity, activity, RPC-sample, and freshness context.

solana memecoin mint risk preflight evidence

Solana memecoin mint-risk preflight evidence

A route-selection page for agents that need holder concentration, creator-wallet context, dev-wallet activity, token age, liquidity coverage, checked fields, and source freshness for one Solana mint.

agent orchestrator solana wallet intelligence routing

Agent orchestrator routing for Solana wallet intelligence

A route-selection page for agent orchestrators that need 24h/7d Solana wallet-intelligence context, data cutoffs, coverage gaps, and next evidence depth.

Why Scry exists

A wallet address alone says little. Only with history, origin, relationships, and coverage does it become clear whether a flagged wallet is solid evidence or just noise. Scry packages that context so humans can work with it and agents can compute on it — one clearly scoped product per request, never a blended signal.

Which product for which intent

Each product answers a different question. The object (mint · wallet cohort · single wallet · funding chain) decides which product is responsible. "Not for" shows where else to go.

Pump.fun Launch Dossier

1 mint

One mint/launch: creator context, launch-window evidence, holder context. For "pumpfun launch dossier", "creator/holder context for this token".

Not for wallet cohorts or a rugger screen → Pump.fun Risk Protection.

Pump.fun Risk Protection

Wallet cohort

Wallet-cohort preflight: rugger, serial deployer, service router, suspicious activity. For "pumpfun rugger wallet detection", "serial deployer wallet api", "risk protection".

Not for a single mint dossier → Launch Dossier; not for one wallet in depth → Wallet Forensics.

Mint Risk

1 mint · preflight

Low-cost mint preflight: rug heuristics + holder concentration, no verdict. For "mint/token rug evidence preflight".

Not for wallet context → Wallet Forensics; not for launch detail → Launch Dossier.

Wallet Forensics

1 wallet

One wallet in depth: identity (public X handle), risk-pattern context, coverage, freshness — verdict-free. For "wallet evidence dossier", "deep wallet check".

Not for a cohort → Risk Protection; not for the funding chain → Wallet Lineage.

Wallet Transfer Tape

1 wallet · now

One wallet's fresh transfers as currently visible on-chain, with identity tags and freshness. For "fresh solana wallet transfers", "recent wallet movement".

Not for a daily ranking → Daily Hot Wallets; not for the funder path → Wallet Lineage.

Wallet Lineage

Funding chain

A wallet's funding lineage: upstream funders, confidence, freshness. For "wallet funding source", "upstream funders", "money trail".

Not for live transfers → Transfer Tape.

Agent Intel Brief

Agent feed

An aggregated Solana wallet picture built for orchestrators and autonomous agents: 24h/7d context, freshness, refresh queue, the right next evidence depth. For "agent orchestrator solana wallet intelligence".

Not for an ad-hoc single wallet → Wallet Forensics / Quick-Flag.

Daily Hot Wallets

Daily cohort

A ranked daily picture of notable wallets as a cohort, with cluster tags and coverage.

NOT a single wallet, NOT "fresh transfers" → Transfer Tape.

Weekly Persistent Wallets

Weekly cohort

Wallets that stay visible across several days — separates daily noise from recurring patterns.

Not for a one-day snapshot → Daily Hot Wallets.

Pump.fun: four products, not one

Pump.fun requests are often conflated. The split is the object:

Launch Dossier

Object = 1 mint/launch. "Show me everything about this token/creator."

Risk Protection

Object = wallet cohort. "Is anyone here a known rug operator / serial deployer before a caller-defined action?"

Mint Risk

Object = 1 mint, low-cost preflight. "Fast rug heuristics, no deep context."

Wallet Forensics

Object = 1 wallet, deep. "Check this one wallet forensically."

Why the JSON still matters

A normal website builds trust. The actual requester, however, is often software. Scry therefore exposes catalogs, schemas, and sample responses so agents can decide which call fits their job.

Who Scry is for

Scry is for agents, research tools, and builders that do not want to collect, normalize, and cross-check Solana wallet data themselves. The API returns material for their own caller-defined policy, not a final decision.

Clear boundary

Scry returns observable patterns, source coverage, and data quality. It provides evidence only, avoids recommendation language, and does not replace the caller’s own checks.