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.
Outline
Section titled “Outline”Choose a vault guide
Section titled “Choose a vault guide”| Guide | Slug | Chains | Deposit |
|---|---|---|---|
| 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 |
Recommended integration paths
Section titled “Recommended integration paths”| Path | Best for | Primary interface | Notes |
|---|---|---|---|
| EVM Actions API | Apps, wallets, custodians, backend transaction builders | https://api.nest.credit/v1/actions | Builds same-chain EVM transaction bundles for supported vault, chain, and asset combinations. |
| Direct EVM contracts | Protocol integrations and advanced backend flows | ERC-20, NestVaultPredicateProxy, NestVault | Requires the integrator to handle compliance, quoting, allowance, calldata, simulation, and redemption lifecycle. |
| Solana transaction builder | Solana wallets and apps | https://api.nest.credit/v1/solana | Returns 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.
Common implementation rules
Section titled “Common implementation rules”- 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.