Zerion

• Name: Zerion
• URL: https://zerion.io/
• Category: self-custodial wallet / portfolio-tracking web app / wallet-data API
• Tags: ethereum-ecosystem solana-ecosystem
• Summary: Zerion is a wallet-plus-data stack. Keep this note on the product surface: the wallet and web app sit on the same multichain indexing and interpretation layer Zerion sells as an API, so the important product question is how a self-custodial wallet turns one company-run data plane into the default read layer around user accounts. Use zerion when the practical question is the named operator boundary around API keys, billing, analytics, provider choice, and data-policy defaults.
• What it does:
  • Offers a self-custodial wallet for iOS, Android, and browser extensions across Solana, Ethereum, Tron, and major EVM networks
  • Provides a web portfolio tracker that can connect any wallet or follow any address for tokens, NFTs, DeFi positions, transaction history, and PnL
  • Exposes a REST API for multichain wallet portfolio data, fungible positions, NFT holdings, transaction history, gas data, swap offers, and webhooks
  • Supports wallet UX features such as swaps and bridges in a single transaction, human-readable transaction previews, Ledger support, spam filtering, and phishing detection
  • Markets its API as infrastructure used by third-party products including wallets, consumer apps, institutional reporting tools, and AI-agent workflows
• Key claims:
  • Zerion’s llms.txt says it is “a self-custodial crypto wallet and onchain data platform” and explicitly states that Zerion Wallet, Zerion Web App, and Zerion API should be treated as one stack
  • The homepage says Zerion offers one wallet for tokens, DeFi, and NFTs across Ethereum, Solana, and major EVM networks, while the supported-blockchains page shows a wide chain matrix rather than a narrow wallet-only footprint
  • The developer docs make the API surface explicit: wallet data, token analytics, DeFi positions, transaction history, and webhooks across EVM chains and Solana under normalized schemas
  • The pricing page exposes a real API business model, which is a stronger signal than vague developer branding that the data layer itself is a product
  • The llms.txt use-case section says Zerion API is used by products including Uniswap Wallet, WalletConnect, OpenSea, Privy, Para, Infinex, Safe, Kraken, Backpack, Bitpanda, and AI-agent projects
  • The security page says Zerion is self-custodial, its core wallet codebase is open source, audits are public, and bug bounty rewards are run through Immunefi
  • Zerion’s materials repeatedly say the company cannot freeze, suspend, or move user funds, but that claim matters less than the fact that Zerion still controls the indexing, filtering, and presentation layer around those funds
• Whitepaper: No canonical standalone Zerion whitepaper or litepaper surfaced in this pass. The clearest current sources of truth were the official site, the unusually detailed llms.txt, the developer docs, the supported-blockchains matrix, the pricing page, and the wallet security page; see ../whitepapers/zerion-primary-sources-2026-04-30.md.
• Sources:
  • https://zerion.io/
  • https://zerion.io/llms.txt
  • https://developers.zerion.io/
  • https://developers.zerion.io/reference/supported-blockchains
  • https://developers.zerion.io/pricing
  • https://zerion.io/security

Internal linkages

• Company / operator boundary for API-account issuance, pricing, analytics/privacy workflow, provider selection, and commercial data access: zerion.
• Best wallet-client peers where signing stays local but interpretation does not: rabby and backpack.
• Best data-layer contrast: alchemy.

Protocol / company boundary

• Keep this note on the user-facing stack: wallet UX, multichain portfolio interpretation, transaction decoding, spam and phishing filtering, swaps and bridges, and the broad wallet plus data layer packaging visible to end users and integrators.
• Use zerion when the real question is who issues API keys, sets pricing and rate limits, chooses analytics and routing providers, constrains data use by contract, and defines the legal/privacy perimeter around the stack.
• That split matters because what does Zerion show or help me do? and which company controls the underlying normalized data service and commercial shell? are related but not identical questions.

Control surface

• Private keys stay local, but Zerion still controls chain coverage, labeling, phishing and spam heuristics, portfolio normalization, webhook delivery, and which swap or bridge routes look normal.

• The company-layer controls above that product surface now live in zerion, which keeps this note from having to carry the whole legal and API-operator story itself.

• Read it as a self-custodial wallet with a centralized interpretation layer, not as neutral wallet glass.

• Last reviewed: 2026-08-08 UTC