Wallet / portfolio APIs

A wallet portfolio API helps a product start from a wallet-owner view: balances, positions, transactions, DeFi account context, and portfolio state. The current Discovery fixture has one direct wallet-portfolio category source, Zerion API, so this hub is intentionally narrow and should describe the supported evidence instead of pretending the category has broad provider coverage

Claim-safe statuses distinguish source profiles, evaluation-only pages, requested integrations, and available gateway/tooling surfaces without exposing paid procurement, approval, or provider-fetching flows

At a glance

Category summary

Primary query: Wallet / portfolio API
Definition: Wallet balance, portfolio, and position data sources for account-centric products.
Sources: 1
Capabilities: 1
Chain hubs: 1
Use-case groups: 2
Last verified: 2026-05-29
PubFi status: Discovery comparison and request-routing surface; individual source pages carry claim-safe integration status.

Official-source citations

Zerion API Primary coverage: Wallet balances, positions, transactions, and DeFi account context Source
Zerion API Fixture coverage: Wallet portfolio coverage for the Ethereum fixture target Source

Editorial overview

Wallet portfolio data is different from generic on-chain-state data because the user-facing question is usually account context, position visibility, and portfolio history rather than raw events or custom indexing. Zerion API is the reviewed source in the current category fixture. Moralis and Covalent may overlap on account or token data elsewhere in Discovery, but the wallet-portfolio hub should keep its direct recommendation to the source with an explicit wallet-portfolio capability mapping until more sources are added.

Start here recommendations

Zerion API

Why start here: Start here because the seed fixture maps Zerion API directly to wallet balances, positions, transactions, and DeFi account context.
Best for: Wallet-owner portfolio views

Decision criteria and landscape gaps

Evaluation criteria

Confirm whether the application needs balances, positions, transaction history, DeFi account context, or a broader on-chain-state source.
Treat wallet-portfolio coverage as source-specific until additional providers have explicit capability mappings.
Keep pricing and quota language conservative when commercial facts are conflicting or product-scope dependent.
Use request-integration language for missing wallet-portfolio coverage instead of implying a complete category marketplace.

Provider landscape gaps

The current seed category has one direct wallet-portfolio source, so the page should not imply broad category maturity.
Wallet, token, and account-data providers may overlap with portfolio needs, but the fixture does not yet support treating every overlap as a wallet-portfolio recommendation.
Public provider pages can expose portfolio features without making exact asset, protocol, and transaction-context coverage easy to compare.