Skip to main content
The Wallet API is in Beta. Endpoints and response formats may change.

Overview

The Wallet Funding Source endpoint identifies who originally funded a Solana wallet by analyzing its first incoming SOL transfer. It is valuable for attribution, compliance, understanding wallet relationships, and identifying exchange-funded wallets. The funder’s name and category come from the same identity system used by the Identity endpoint, so when the funder is a known entity you get a human-readable label and category directly in the response. This endpoint requires a paid plan. Requests made with a Free-plan API key return 403 Forbidden. See Plan requirements for the full coverage table.

When to use this

Use the Wallet Funding Source API for:
  • Wallet attribution: track where new wallets are being funded from.
  • Exchange detection: identify wallets funded directly from centralized exchanges.
  • Compliance and AML: flag wallets funded by known entities for compliance checks.
  • Bot detection: identify bot farms funded from the same source.
  • Airdrop analysis: track which wallets received initial funding from a project.
  • Sybil detection: find clusters of wallets funded by the same address.

Quickstart

Basic funding lookup

Find out who funded a wallet:

Response format

A successful response describes the wallet’s first incoming SOL transfer:
If a wallet has never received SOL, the API returns a 404:

Field notes

  • funder: the address that sent the first SOL transfer to this wallet.
  • funderName: human-readable name if the funder is a known entity (e.g., exchange, protocol); null otherwise.
  • funderType: category of the funder (e.g., exchange, defi-protocol); null if not in the identity database.
  • mint: token mint address (So11111111111111111111111111111111111111111 for SOL).
  • symbol: token symbol (always SOL for funding transactions).
  • amount: initial SOL amount received (human-readable, e.g., 0.05 SOL).
  • amountRaw: raw amount in lamports as a string (e.g., "50000000" for 0.05 SOL).
  • decimals: number of decimal places for the token (9 for SOL).
  • date: ISO 8601 formatted date string (e.g., "2024-01-01T00:00:00.000Z").
  • signature: transaction signature of the funding transfer.
  • timestamp: Unix timestamp (in seconds) when the wallet was funded.
  • slot: Solana slot number when the funding transaction was confirmed.
  • explorerUrl: direct link to view the transaction on Orb.

Use cases

Detect exchange-funded wallets

Identify wallets funded directly from centralized exchanges:

Find wallet clusters (Sybil detection)

Identify groups of wallets funded by the same source:

Track airdrop recipients

Analyze where airdrop recipients came from:

Build a wallet timeline

Create a timeline starting from the wallet’s creation:

Compliance risk scoring

Assign risk scores based on funding source:

Attribution tracking

Track which sources are creating the most new wallets:

Funder types

The funderType field indicates the category of the wallet that funded the address. All values from the Identity Categories are supported.
Common funder types:The complete list includes: Airdrop, Authority, Cross-chain Bridge, Casino & Gambling, DAO, DeFi, DePIN, Centralized Exchange, Exploiter/Hackers/Scams, Fees, Fundraise, Game, Genesis Block Distribution, Governance, Hacker, Jito, Key Opinion Leader, Market Maker, Memecoin, Multisig, NFT, Non-Circulating Supply, Oracle, Other, Payments, Proprietary AMM, Restaking, Rugger, Scammer, Spam, Stake Pool, System, Tools, Trading App/Bot, Trading Firm, Transaction Sending, Treasury, Validator, Vault, and X402.See the Identity Categories section for the complete list with descriptions.

Best practices

  • Handle 404 responses. Wallets that have never received SOL return a 404. This is expected for newly created but unfunded wallets.
  • Combine with the Identity API. The response includes funderName and funderType, but you can call the Identity endpoint on the funder address for more detail.
  • Cache funding data. A wallet’s funding source never changes. Cache this data permanently to avoid repeated API calls.
  • Check age for context. The timestamp tells you when the wallet was first funded. Combine age with funding source for better context.

Common errors

Limitations

  • This endpoint only tracks the first SOL transfer to a wallet.
  • If a wallet was created via airdrop or program initialization without a SOL transfer, it won’t have funding data.
  • The funding source represents the immediate funder, not necessarily the ultimate source of funds.
  • Historical data is only available for wallets created after this feature was deployed.

Next steps

Wallet Identity

Resolve the funder address to a full label, category, and tags.

Wallet API Overview

All Wallet API endpoints and shared conventions.

API Reference

Request and response schemas for funding source lookup.