Integration Guides

Vault-by-vault guides for integrating Nest mint and redemption flows on Arc.

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.

These guides list only vaults with Arc deposit routes. Build transactions for Arc (chain ID 5042) using a supported vault and asset from the Vault Directory.

Outline

Choose a vault guide

GuideSlugChainsDeposit
nTBILL Integration
Nest Treasury Vault
nest-treasury-vaultArc
nALPHA Integration
Nest Alpha Vault
nest-alpha-vaultArc
nBASIS Integration
Nest Basis Vault
nest-basis-vaultArc
nOPAL Integration
Nest BlackOpal LiquidStone II Vault
nest-opal-vaultArc
nCREDIT Integration
Nest Credit Vault
nest-credit-vaultArc
nWISDOM Integration
Nest Wisdom Vault
nest-wisdom-vaultArc
nACRDX Integration
Nest ACRDX Vault
nest-acrdx-vaultArc
nFXCF Integration
Nest FalconX CLO Vault
nest-falconx-cloArc
nCLO Integration
Nest BlackRock iShares AAA CLO Active ETF Vault
nest-cloa-vaultArc
FACTOR Integration
Plume Factor Vault
plume-factor-vaultArc
nPRIME Integration
Prime Vault
nprimeArc

Each vault guide includes Deposit, Deposit on behalf, and Redeem sections. The Deposit on behalf section explains the shared caller, original depositor, share receiver, attestation lifecycle and destination transaction for aggregators such as LI.FI.

PathBest forPrimary interfaceNotes
Arc Actions APIApps, wallets, custodians, backend transaction buildershttps://api.nest.credit/v1/actionsBuilds EVM transaction bundles for a supported vault and asset on Arc.
Direct Arc contractsProtocol integrations and advanced backend flowsERC-20, ComplianceProxy (V2), NestVaultRequires the integrator to handle compliance, quoting, allowance, calldata, simulation, and redemption lifecycle.

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

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.
  • Explicitly set complianceVersion: "v2" on all Actions mint quotes and builds, including vaults with V1 defaults. Require an enabled V2 deployment for the route; never fall back to V1 for deposit on behalf.
  • Execute returned EVM transactions in order from the specified sender.
  • 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 V2 compliance attestation before submitting transactions.

On this page