Beta

Beta features are accessible using your existing API key. The endpoints below cover product areas that are being validated before general availability. Where an endpoint supports allowedProtocols or disallowedProtocols, each value may be either a broad protocol name or a full protocol ID for one product and version.

​

Solana vaults

Build Solana/SVM vault integrations alongside the EVM vault API surface. These endpoints cover Solana vault discovery, detailed vault data, wallet positions and events, idle assets, and ready-to-sign transaction construction. Detailed vault responses can include an optional lpToken object with address (the LP-token mint), tokenCaip (its CAIP-19 identifier), name, symbol, and decimals. The object is omitted when the required metadata is unavailable. Idle-asset responses include token name and symbol, plus assetLogo where available, alongside the address, decimals, and balance. For single-asset lookups, unavailable names and symbols can be empty strings.

​

Reading SVM position values

GET /beta/svm/portfolio/positions/{userAddress} returns positions in data. Each position’s asset object includes: For example, a positionValueInAsset of "1250000" with decimals: 6 represents 1.25 underlying tokens. Do not add positionValueInAsset to balanceNative: they describe the same balance. If the optional field is absent, use balanceNative. These are underlying-asset amounts, not LP-token share amounts.

​

Building SVM transactions

SVM transaction responses return one or more actions with a Solana transaction object at actions[].tx.transaction. The value is a base64-encoded serialized Solana transaction ready for wallet signing. Passing simulate=true can add a simulation object with status plus token amounts expected to be spent or received.

​

Borrow markets

Build borrow dashboards and account-health views against one borrow market model instead of wiring separate protocol-specific routes. Use these endpoints for market discovery, historical rates, user positions, user events, and ready-to-sign borrow transaction payloads.

​

Reading borrow positions

GET /beta/borrow/portfolio/positions/{userAddress} lists markets with outstanding debt, not every supply-only or collateral-only position. A market must retain an asset with nonzero borrowedNative after asset and USD-value filtering to appear in the list. Filtering out the debt asset can therefore remove the entire market, including its collateral. Use the single-market or asset-level position endpoints when inspecting a known position, including one without debt. When aggregating balances across markets, use assets[].positionId to avoid counting the same underlying position more than once.

​

Building borrow transactions

Fetch transaction context first and use the returned supplySteps, withdrawSteps, borrowSteps, or repaySteps. Their action lists depend on the protocol and collateral configuration, and may include enableCollateral or enableController alongside approval and supply/withdraw/borrow/repay actions. Do not hard-code a universal approval-and-supply sequence. Borrow market responses expose assetsData[].marketAssetId. Pass that value as {assetId} when chaining from market discovery into historical data, portfolio events, asset-level positions, or transaction endpoints.

​

Advanced analytics

Request heavier per-vault analytics only when your product needs them. Selectable analytics sections include max drawdown, withdrawal pause ratio, composition, utilization rate, and the full V2 detailed-vault payload where supported. Each request costs 1 base credit. The remaining cost scales with the number of items returned and the fields included for each item: The per-item costs are cumulative. For example, a request that returns 10 items with maxDrawdown and composition costs 1 + (10 × (2 + 3)) = 51 credits.

​

The Deep

Build AMM-style vault integrations for Deep liquidity positions. These endpoints cover vault discovery, wallet positions, and ready-to-sign deposit or withdrawal transactions.

​

Fixed Term (Pendle)

Add fixed-term yield market support for Pendle-backed opportunities. Use these endpoints to discover and compare active markets, retrieve detailed market data, preview transaction context, and generate swap-in or swap-out transactions. Fixed-term market discovery costs 1 base credit plus 3 credits per returned market. For example, 10 returned markets cost 31 credits.

​

Portfolio

Measure user returns over a selected time window instead of only showing lifetime returns. This supports performance reporting, account history views, and user-specific analytics. Beta endpoints require an API key. Sign up to get started, then watch the changelog for changes before general availability.