Skip to content

DEVELOPERS

Integration Guides

These guides are organized one vault per page. Use the Actions API path first for app, wallet, and backend transaction-builder integrations. Use the direct contract path only when your integration needs lower-level control over quoting, compliance, approvals, and redemption state.

GuideSlugChainsDeposit
nTBILL Integration
Nest Treasury Vault
nest-treasury-vault
nALPHA Integration
Nest Alpha Vault
nest-alpha-vault
nBASIS Integration
Nest Basis Vault
nest-basis-vault
nOPAL Integration
Nest BlackOpal LiquidStone II Vault
nest-opal-vault
nCREDIT Integration
Nest Credit Vault
nest-credit-vault
nWISDOM Integration
Nest Wisdom Vault
nest-wisdom-vault
nACRDX Integration
Nest ACRDX Vault
nest-acrdx-vault
nLCRD Integration
Nest Liquid Credit Vault
nest-lcrd-vault
nPERENA Integration
Nest Perena Vault
nest-perena-vault
nFALCON Integration
Nest FalconX CLO Vault
nest-falconx-clo
nCLOA Integration
Nest BlackRock iShares AAA CLO Active ETF Vault
nest-cloa-vault
PathBest forPrimary interfaceNotes
EVM Actions APIApps, wallets, custodians, backend transaction buildershttps://api.nest.credit/v1/actionsBuilds same-chain EVM transaction bundles for supported vault, chain, and asset combinations.
Direct EVM contractsProtocol integrations and advanced backend flowsERC-20, NestVaultPredicateProxy, NestVaultRequires the integrator to handle compliance, quoting, allowance, calldata, simulation, and redemption lifecycle.
Solana transaction builderSolana wallets and appshttps://api.nest.credit/v1/solanaReturns base64 Solana transactions for the user’s wallet to sign and broadcast.

The EVM Actions API OpenAPI JSON is available at https://api.nest.credit/v1/actions/docs.

  • Treat every API amount as a raw integer amount, not a decimal UI amount.
  • Use the decimals returned by the API when rendering user-facing amounts.
  • Execute returned EVM transactions in order.
  • Never assume an approval transaction is present. If allowance is already sufficient, the API can omit it.
  • Re-quote close to the time the user signs.
  • User-facing apps should keep API simulation enabled.
  • For direct EVM integrations, validate the selected vault, chain, asset, and compliance message before submitting transactions.