Compare Solutions/Portfolio APIs

DeFi Orbit vs. Zerion API

Zerion API is a broad wallet data API: tokens, NFTs, transactions and DeFi positions across many chains and protocols. DeFi Orbit gives you broad position coverage too, and goes deeper on each liquidity and lending position, in Portfolio and through the API. Many teams will want both. This page shows where the two differ.

Last reviewed October 13, 2026

Zerion API is a good fit when

You are building a wallet or app that shows a full portfolio

You need tokens, NFTs and transaction history across many chains

You want a free plan to start building on

Use DeFi Orbit when

Liquidity and lending positions are the core of what you report

You need fees, PnL and impermanent loss per position, with history

You need health factor and liquidation data on lending positions

01 / Side by side

What you get from each

Zerion API

Built for

Wallets and apps that show everything an address holds

Teams that monitor and report on liquidity and lending positions

Coverage

42 chains and 4.5k+ DeFi protocols, as stated on zerion.io/api

Balances and positions across 500+ protocols on 10 chains, in Portfolio. In depth, with fees, PnL and impermanent loss per position, in Portfolio and the API: Uniswap V3, Aerodrome, Orca, Aave V3, Morpho Blue and Kamino

Shape of an LP position

One position per token. Tokens in the same pool share a group ID that you group on

One object per position, with both tokens together

Price range and in-range status

Not listed in the positions reference

Returned on the position

Uncollected fees

Not listed in the positions reference

Returned on the position

PnL

Per wallet, using FIFO, described in terms of fungible assets. No per-position PnL is listed

Per position, with impermanent loss and documented methods

Performance over time

A 1-day change on each position, plus a wallet-level chart

Event history and daily snapshots for every position

Freshness

Each position carries an updated-at time and block. The reference says updates typically occur immediately after an event changes the position; no refresh interval is stated.

Real time on every request

Lending positions

Deposit and loan positions with quantity and value. Health factor is not listed

Health factor and liquidation data included

Protocol positions on Solana

Not supported for Solana addresses yet, per the positions reference

Orca and Kamino covered in the same API

Pricing model

Monthly plans: free at 2K requests a day (3 requests per second), $149 for 250K a month (10 per second), $499 for 1M a month (25 per second). DeFi positions, portfolio chart and PnL calls are limited to 25% of the plan quota and are not covered by overages.

Prepaid credits, 1 to 15 per call, from $10. Purchased credits do not expire while the account is active

AI agent access

Pay-per-request access for agents, as stated on zerion.io/api

DeFi Orbit AI: a hosted MCP server with 52 read-only tools

02 / Breadth and depth

What you still build if you need position-level reporting

A broad positions endpoint tells you what a wallet holds and what it is worth today. If you report on how each position performed, this is the work that remains on your side.

01
Rebuild the position
Group the per-token rows back into one LP position using the group ID.
02
Read the range on-chain
Tick range, liquidity and in-range status come from the protocol contracts, using the NFT token ID.
03
Read uncollected fees
Another set of contract calls, with different maths for each protocol.
04
Collect the position history
Every deposit, withdrawal and fee collection for that position, in order.
05
Price each event
A USD value for each token at the time of each event.
06
Write the calculations
PnL against holding, impermanent loss and APR, with rules you decide and document.
07
Add lending risk
Health factor and liquidation thresholds, read from each lending protocol.

03 / From their documentation

Six things to know if LP and lending data is your core need

Each point comes from Zerion’s API reference or pricing page. These are design choices for a broad wallet API, not faults.

Coverage is wide by design

Thousands of protocols under one schema means each position carries the fields they all share: quantity, value and price.

An LP position arrives as separate rows

The reference describes one position per token, linked by a group ID. Treating the pair as one position is left to you.

The performance field is a 1-day change

The position object lists absolute and percentage change over one day. Longer history is at wallet level. Zerion’s site describes the data as real time with under 100 ms latency; that is speed of response, not depth of history.

Wallet PnL is not position PnL

The PnL endpoint returns one result per wallet, with a per-asset breakdown on request. It does not describe PnL for an LP position.

Solana protocol positions are not there yet

The positions reference states that protocol positions are not supported for Solana addresses yet.

DeFi positions have a smaller quota

The pricing page limits DeFi positions, wallet chart and wallet PnL calls to 25% of each plan’s requests.

04 / When we are not the fit

When Zerion API is the better choice

Zerion does several things we do not. If one of these is your case, use it.

You need NFTs

Zerion returns the NFTs a wallet holds, with metadata and collection data. We cover tokens and positions, not NFTs.

You need chains we don’t cover

Zerion covers 42 chains. We cover ten, with depth on each. If your users are spread across the long tail of networks, Zerion is the broader net.

You need transactions and webhooks

Decoded transaction history and wallet activity webhooks are part of Zerion API. We don’t offer either; our data starts at the position.

05 / FAQ

Questions teams ask before deciding

Can we use both?

Yes. Some teams use Zerion API for tokens, NFTs and transaction history across many chains, and DeFi Orbit for the liquidity and lending positions they report on in detail. The two answer different questions, so running both is common rather than a compromise.

The numbers that turn a position into a report: price range and in-range status, uncollected fees, PnL and impermanent loss per position, and history from the position’s first event. On lending, you get health factor and liquidation data for each position rather than a balance.

We show balances and positions across 500+ protocols on 10 chains in Portfolio. On six of them, Uniswap V3, Aerodrome, Orca, Aave V3, Morpho Blue and Kamino, we go further with fees, PnL, impermanent loss and history for each position, in Portfolio and the API, and we add more in-depth protocols as scoped Custom Data projects.

Run the API on wallets you already track and compare position by position. The methods for PnL, impermanent loss, fees and APR are documented, so where a figure differs you can see which rule explains it, and we’ll walk through any gap with you.

Each endpoint has a fixed cost of 1 to 15 credits per call, and packs start at 500 credits for $10. Failed requests are free and purchased credits don’t expire while your account is active, so there’s no monthly plan to size and no separate quota for position data.

No. Everything is read-only and works from public wallet addresses. There’s nothing to connect and nothing we could move.

See all comparisons

Sources

Statements about Zerion API are linked to Zerion’s API reference and pricing page and were last checked on October 13, 2026.

Compare the two on wallets you know

Run both APIs on the same LP and lending wallets and compare what comes back.

Get API key Book a demo