Scry answer · Agent routing

Who funded this Solana wallet?

The funder of a Solana wallet is identified by following its incoming SOL and token transfers back to the upstream wallets that first funded it, then checking whether any of those are known services or exchanges. The Scry wallet source-of-funds route returns this as evidence: upstream funder wallets, funding hop depth, known service or identity hints when covered, confidence notes, and lineage freshness.

Direct answer

Who funded this Solana wallet? — route and payment facts
Question	`Who funded this Solana wallet?`
Request object	`one wallet funding chain`
Route	`https://scry.solanahub.de/x402/wallet/:address/lineage`
Payment	`0.03 USDC per request (x402 v2 exact-scheme USDC)`
Access	`No API keys, no account, x402 per request`
Evidence fields	`5`

How an agent calls this route

Send GET https://scry.solanahub.de/x402/wallet/:address/lineage and read the returned HTTP 402 payment requirements.
Sign a USDC payment for 0.03 on x402 v2 exact-scheme USDC.
Retry the request with the X-PAYMENT header to receive the paid evidence response.
Read the coverage, confidence, and freshness metadata before using the evidence in a wider workflow.

Agent decision

Request this route only when the object matches one wallet funding chain. Read coverage, confidence, and freshness metadata before using the evidence in a broader workflow.

Provider comparison · checked 2026-09-26

Solana wallet funding-source APIs compared

Helius and Birdeye's documented funded-by routes return the first or earliest native-SOL funding event rather than a multi-hop funding chain, and their endpoint documentation specifies API-key access. Conyr documents provenance tracing up to 20 hops to a known exchange or service on its $75/month Layer 2 plan. Scry's cache-first lineage route returns covered upstream funders with reported hop depth and confidence for $0.03 via x402, without an API key. Before paying Scry, query the free coverage probe and treat any required dimension marked stale as a reason to wait or choose another provider.

Comparison of Helius, Birdeye, Conyr, Nansen and Scry for Solana wallet funding-source analysis
Provider / endpoint	What it returns	Tracing depth	Access	Price	Best for	Primary sources
Helius Wallet API `GET /v1/wallet/{wallet}/funded-by`	The wallet's first incoming SOL transfer: funder, funderName and funderType when the funder is a known entity, plus amount, date, signature, slot and an explorer link. A wallet that never received SOL returns 404.	First funder only. Helius explicitly describes this as the immediate funder, not necessarily the ultimate source of funds.	API key; a paid Helius plan is required. Free-plan keys receive 403.	100 Helius credits per request; its USD value depends on the selected plan.	Labelled first-funder lookups across any supported Solana wallet.	Endpoint docs Credit schedule
Birdeye Data `GET /wallet/v2/funded-by`	Native-SOL funders associated with the earliest qualifying funding event, including label when available, amount, slot, timestamp and tx_hash.	Earliest funding event only; the endpoint does not document multi-hop tracing.	The endpoint documentation specifies X-API-KEY and Lite or higher. Birdeye separately advertises x402 access to its REST API, but this funded-by route was absent from its x402 discovery catalog when checked.	30 compute units per request. Lite is $39/month with 2.5M CU; additional CU are $23 per 1M. Birdeye x402 pricing is $0.003 per supported request.	Teams already using Birdeye for wallet, price, PnL and holder data.	Endpoint docs Pricing x402 access
Conyr `GET /v1/wallet/{addr}/provenance`	root_entity, root_source, hops, direct_funder and last_funded_ts. If no known root is found, root_entity and hops are null.	Up to 20 hops to 128 curated exchange, custody, payment, service and infrastructure origins.	Bearer API key on the Layer 2 plan.	$75/month, or $60/month billed annually; 300 requests per minute.	The deepest documented root-to-exchange tracing in this comparison.	API reference Plans and capabilities
Nansen `POST /api/v1/profiler/address/related-wallets`	Related wallets with a relation type, transaction hash, timestamp and order. Solana is one of the supported chains.	Not documented as a dedicated funding-lineage endpoint. Funding-specific relation types and hop depth are not documented.	x402 in USDC on Base, Solana or Monad; MPP; or an API key.	$0.01 per call through x402 as a Basic endpoint.	Multi-chain related-wallet context alongside Nansen data products.	x402 pricing Related Wallets schema
Scry `GET /x402/wallet/:address/lineage`	Cached upstream funder evidence, depth_reached, terminal_funder, loop_detected, known service and identity hints when covered, confidence, coverage, source_updated_at and an evidence pack.	Upstream chain with reported hop depth; no maximum depth is documented. Coverage is Scry's indexed Solana memecoin-trader cohort, not every Solana wallet.	x402 v2 exact-scheme USDC on Solana or Base; no API key or account.	$0.03 per call.	Agents that want pay-per-request lineage evidence only after the free probe confirms coverage and acceptable per-dimension freshness.	Product catalog OpenAPI Freshness policy

Prices, endpoint behavior and access models are dated 2026-09-26. Provider terms can change; verify the linked primary sources before implementation.

When to use which

You only need the first or earliest SOL funder and an entity label

Use Helius funded-by, or Birdeye funded-by if Birdeye is already in your stack.

You need a chain traced back to a known exchange root and a monthly plan is acceptable

Use Conyr provenance; it documents up to 20 hops.

You already use Nansen across several chains

Use Nansen Related Wallets for related-wallet context. Do not treat it as a documented funding-lineage route.

Your agent pays per request and holds no API keys

Use Scry lineage only when the free coverage response says the wallet is covered and every dimension your workflow needs is fresh enough. A coverage hit is not a freshness guarantee.

You are testing an x402 client rather than buying lineage evidence

Use Scry quick-flag at $0.005 instead of the $0.03 lineage route.

Funding-source API questions

Helius funded-by vs Scry funding lineage: what is the difference?

Helius funded-by returns the first wallet that sent SOL to an address, with a name and category when the funder is a known entity. It requires an API key on a paid plan and costs 100 Helius credits per request. Scry lineage returns cached upstream funder evidence with reported hop depth, confidence and per-dimension freshness. It costs $0.03 per x402 call without an API key and covers Scry's indexed wallet cohort rather than every Solana wallet.

Is there a Solana funding-source API without an API key?

Yes. Scry's lineage route is paid per request through x402 in USDC on Solana or Base at $0.03, without an API key or account. Nansen Related Wallets also accepts x402 at $0.01, but it is not documented as a dedicated funding-lineage route. Birdeye advertises x402 for its REST API, but its funded-by endpoint was not in the x402 discovery catalog when checked. Helius and Conyr document API-key access.

Nansen vs Conyr vs Scry for wallet funding lineage?

Conyr documents the deepest tracing: up to 20 hops to 128 curated exchange and service origins on a $75/month Layer 2 plan. Nansen Related Wallets returns related wallets with relation types across many chains for $0.01 through x402, but funding-specific depth is not documented. Scry returns cached upstream funders with reported hop depth, confidence and freshness for $0.03 per x402 call, without a subscription, when the wallet is covered.

Can I trace a Solana wallet's funding beyond the first funder?

Helius and Birdeye funded-by return the first or earliest native-SOL funding event, so you would have to repeat lookups yourself. Conyr provenance traces up to 20 hops to a known root. Scry lineage returns a cached upstream chain with depth_reached, terminal_funder and loop_detected, plus confidence, coverage and freshness metadata.

How can I check Scry before paying $0.03 for lineage?

Call the free coverage probe at https://scry.solanahub.de/x402/coverage/{address}. Confirm that the wallet is in Scry's indexed cohort, then inspect every dimension required by your workflow. Coverage is not a freshness guarantee: if lineage or another required dimension is marked stale, wait for a refresh or choose another provider instead of treating the paid result as current. Use the $0.005 quick-flag route only to test an x402 payment flow.

Route contract

GET https://scry.solanahub.de/x402/wallet/:address/lineage GET https://scry.solanahub.de/x402/wallet-lineage?address=:address https://solanahub.de/en/scry/use-cases/solana-wallet-source-of-funds-evidence/#agent-route-contract