Cowrie Research

zerion

4 min read

Zerion Inc

  • Name: Zerion Inc
  • URL: https://zerion.io/
  • Category: wallet-and-onchain-data company / API operator / self-custodial app company
  • Tags: ethereum-ecosystem solana-ecosystem
  • Summary: Zerion clears the bar for a company note because the practical control surface is not just that a self-custodial wallet exists. A named company operates the wallet, web app, and API as one stack, decides which chains and protocols get normalized, issues and revokes API access, sets webhook and pricing defaults, chooses analytics and routing providers, and defines the legal and privacy perimeter around the product. The project note remains useful for the user-facing stack; this note is for the operator boundary that shapes the data and workflow users and integrators inherit.
  • What it does:
    • Operates Zerion Wallet, a non-custodial wallet across mobile and browser-extension surfaces
    • Operates the Zerion web app for multichain portfolio tracking, token and NFT views, DeFi positions, transaction history, and PnL
    • Sells Zerion API access for wallet portfolio, transactions, DeFi positions, NFTs, gas data, swap offers, and webhooks across EVM chains and Solana
    • Manages customer API accounts, billing, access codes, service-level expectations, and commercial restrictions around Zerion Data
    • Chooses the analytics, RPC, DEX-aggregation, push-notification, and support workflow wrapped around the broader product stack
  • Key claims:
    • Zerion’s official llms.txt explicitly says Zerion Wallet, Zerion Web App, and Zerion API should be treated as one stack, which is a strong primary-source signal that the company boundary matters more than treating each surface as a separate product silo
    • The developer docs say the API exposes wallet data, DeFi positions, transactions, NFTs, and realtime webhooks across EVM chains and Solana, and that the same infrastructure powers the Zerion app used by millions
    • Zerion’s terms identify Zerion Inc as the company providing the Zerion Interface and Zerion Wallet Services via app.zerion.io, mobile applications, and browser extension, which makes the legal operator boundary explicit rather than implied
    • The privacy policy says Zerion collects public wallet addresses, public blockchain data, hashed IP data where possible, device and browser information, product-usage analytics, push-token data, and API-account / billing information sourced through Clerk and Stripe for API customers
    • The privacy policy also names important packaged dependencies, including AWS and Cloudflare, RPC providers such as QuickNode, Alchemy, Triton One, DEX aggregators including 0x and 1inch, and Hashflow as a private market maker for swap flows; that is useful because the company note can record the offchain routing and observability shell the product note should not overstuff
    • The API license agreement says Zerion can deny or revoke API access, limit request frequency, change APIs and features over time, and prohibit archiving or reselling Zerion Data, which makes API-key issuance and ongoing commercial access a real operator-controlled choke point
    • Zerion repeatedly says it is non-custodial and cannot move user funds, but the more important analytical point is that the company still controls normalization, labeling, spam filtering, webhook delivery, partner packaging, and the offchain data and policy layer around those funds
  • Whitepaper: No classic Zerion company whitepaper is the point here. The strongest primary materials for this pass were the official llms.txt, developer docs, wallet terms, privacy policy, API license agreement, and security page collected in ../whitepapers/zerion-company-primary-sources-2026-08-08.md.
  • Sources:

Internal linkages

Protocol / company boundary

  • Keep zerion focused on the user-facing stack: self-custodial wallet behavior, multichain portfolio interpretation, transaction decoding, swap and bridge UX, and the broad wallet plus data layer product surface.
  • Keep this note focused on Zerion Inc as the named operator that issues API keys, sets pricing and commercial limits, chooses analytics and routing providers, defines privacy and support workflow, and decides how normalized chain and protocol data are packaged and distributed.
  • That split matters because what does the wallet or app show me? and which company controls the data, keys, contracts, billing, and observability shell around that experience? are related but not identical questions.

Control surface

  • Practical leverage sits in API-key issuance and revocation, pricing tiers and rate limits, chain and protocol coverage, spam and phishing labeling, webhook semantics, analytics and notification defaults, and the provider choices Zerion makes for routing, swaps, and data collection.

  • Even when signing stays local, Zerion still shapes what users and integrators see as canonical portfolio truth, recent activity, supported venues, and safe or unsafe assets.

  • Read Zerion Inc as the named data-and-wallet operating shell around a non-custodial product, not as neutral wallet glass.

  • Last reviewed: 2026-08-08 UTC

Graph View

Backlinks