Lucida Developer Platform

Build with Lucida

Access Lucida Vault data, account positions, rates, unsigned transaction construction, LUX data, and event notifications through a production-oriented developer interface.

Explore API View Documentation

Solana NativeUnsigned TransactionsVault DataAccount PositionsLUX DataWebhooks

Developer Overview

Build wallet, Vault, rates, positions, and LUX surfaces.

Vault discovery

Read supported Lucida Vaults, configured assets, network settings, and strategy readiness.

Rate data

Fetch estimated SOL and USDC APY data with source metadata. APY is informational and not guaranteed.

Transaction construction

Construct deposit and withdrawal flows while the user's wallet remains the signer.

Account positions

Resolve wallet-level Vault shares, principal, redeemable assets, estimated yield, and update status.

LUX data

Read off-chain LUX participation metrics, referral data, accrual state, and leaderboard records.

Event notifications

Plan for signed event delivery where webhook infrastructure is enabled.

Base URL and Environments

Use https://lucidafi.xyz/api.

Integrators should use the official Lucida domain, verify the active network in every wallet flow, and confirm program IDs before signing transactions.

Environment	Base URL	Status
Production API	https://lucidafi.xyz/api	Official Lucida Mainnet API base URL.
Application	https://lucidafi.xyz	Official Lucida web application.
Endpoint format	https://lucidafi.xyz/api/{route}	Append the documented route to the production API base URL.

Authentication and API Keys

Protect server-side access.

Lucida integrations should keep secret keys on trusted servers, separate environments, rotate credentials regularly, and revoke keys immediately after suspected exposure.

Public app endpoints

Application access

Browser-facing Lucida routes support the web application experience.

Admin endpoints

Session/admin protected

Administrative strategy and governance routes require the configured admin session.

Partner API keys

Server-side only

Never expose secret keys in frontend code. Use separate keys for server, staging, analytics, and automation integrations.

Environment separation

Required

Keep keys, RPC URLs, program IDs, and webhook secrets separated by environment.

API Reference

Lucida API endpoints.

Use Lucida API responses for Vault data, rates, transaction workflows, positions, LUX, and event-driven integrations. Confirm final transaction state on-chain before persisting user-facing settlement.

Contact Support

Vaults API

Discover Lucida network and Vault settings for the active application environment.

GET/api/deposit/config

Network, program ID, Vault addresses, USDC mint, and strategy readiness

GET/api/nav

Protocol metadata, emergency-pause flag, strategy governance notes, and fee policy

Rates API

Read estimated rate and display-price data. Rates are estimates and must not be used as Vault settlement truth.

GET/api/apy

Est. APY for SOL and USDC

GET/api/price

SOL display price metadata

GET/api/insights/rates?asset=USDC&range=30d

Historical benchmark-rate data where supported

Transactions API

Prepare strategy-aware transaction payloads and index confirmed wallet-signed transactions. The API does not sign for users or custody private keys.

POST/api/deposit/strategy

Prepare a Lucida deposit transaction payload

POST/api/withdraw/strategy

Prepare a Lucida withdrawal transaction payload

POST/api/deposit

Verify and record a confirmed deposit transaction

POST/api/withdraw

Verify and record a confirmed withdrawal transaction

Positions API

Query wallet positions without mixing SOL and USDC settlement. USD values may appear only as display fields or LUX inputs.

GET/api/dashboard?wallet={wallet}

Portfolio, shares, principal, balances, and activity

GET/api/withdraw?wallet={wallet}

Withdrawable balances and share availability

GET/api/positions/live?wallet={wallet}

Live on-chain position preview where program configuration is available

LUX API

Read Lucida's off-chain participation record for future eligibility review, including Vault activity, referral data, accrual state, and leaderboard records.

GET/api/lux?wallet={wallet}

Wallet LUX summary, vault breakdown, referral data, and rules

GET/api/lux/leaderboard

Leaderboard records

Webhooks

Receive Lucida event notifications for approved integrations. Integrators should require signed events, timestamp tolerance, idempotency, and replay protection.

Eventdeposit.confirmed

Confirmed deposit event

Eventwithdrawal.confirmed

Confirmed withdrawal event

Eventposition.updated

Position accounting event

Eventlux.updated

LUX update event

Eventvault.paused / vault.resumed

Vault state change events

SDK availability

Use the Lucida API directly for integrations. SDK package availability and supported versions are communicated through official Lucida channels.

const response = await fetch("https://lucidafi.xyz/api/deposit/config");
if (!response.ok) throw new Error("Lucida configuration unavailable");

const config = await response.json();

// Before signing a transaction payload returned by Lucida:
// 1. verify network and programId
// 2. verify vault, mint, amount, destination, and fee payer
// 3. simulate the transaction
// 4. confirm final state on-chain

Transaction validation

NetworkProgram IDInstructionVaultMintAmountDestinationFee payerRecent blockhash

API responses are not final chain state. Simulate before signing, then confirm the final transaction and account state on-chain.

Data trust model

Treat every RPC response, account payload, transaction log, and webhook body as untrusted until validated against Lucida schemas, configured addresses, and signatures where supported.

Error Handling, Rate Limits, and Idempotency

Handle failures explicitly.

Integrations should treat every failed response as non-final, surface actionable messages to users, and confirm transaction state on-chain before retrying settlement-sensitive operations.

Code	Meaning
INVALID_REQUEST	Malformed request body, missing wallet, unsupported asset, or invalid parameter.
UNAUTHORIZED	Authentication is required for protected admin routes.
FORBIDDEN	The caller is authenticated but not authorized for the requested action.
NOT_FOUND	Requested user, Vault, transaction, or resource was not found.
RATE_LIMITED	Rate limit handling is production-dependent and should be checked through response headers where supported.
VAULT_PAUSED	Vault operations are unavailable because a pause control is active.
INSUFFICIENT_BALANCE	The wallet or Lucida position cannot cover the requested operation.
TRANSACTION_SIMULATION_FAILED	The transaction did not simulate successfully.
TRANSACTION_EXPIRED	The recent blockhash or transaction payload is stale and must be reconstructed.
INTERNAL_ERROR	The server could not complete the request.

Rate limits

Rate limits may vary by endpoint and API access tier. Limit metadata is returned through response headers where supported. Do not assume a fixed request-per-minute value unless it is published for your access tier.

Idempotency

Use transaction signatures and integration-level request identifiers to avoid duplicate processing. Do not retry settlement-sensitive operations without checking on-chain state first.

Security Guidelines

Integrate defensively.

Lucida transaction construction does not replace wallet approval or on-chain verification. Integrators are responsible for validating payloads before presenting them to users.

Never request user seed phrases.

Never store private keys.

Verify the Lucida program ID.

Verify the mint and token program.

Verify transaction instructions before wallet approval.

Simulate before signing.

Set request timeouts.

Reject stale blockhashes.

Verify webhook signatures when webhooks are enabled.

Log request IDs where available.

Do not trust display prices for settlement.

Confirm final state on-chain.

Changelog

API change log structure.

Use this structure for public API releases, breaking changes, and migration notes.

Date	API version	Change	Breaking change	Migration notes
Official release date	Application routes	Documented Lucida API surface	No	Use official Lucida migration notes when a versioned API changes

Build against Lucida carefully.

Start with protocol documentation, verify every transaction payload, simulate before signing, and confirm final state on-chain.

Contact Support Read Docs