Calldata

Returns one ready-to-sign selfBatchDeposit transaction on the strategy's chain, covering local vault deposits plus per-remote-chain CCTP burns. The matching intent (kind deposit) is written server-side; do not post an intent separately. No auth.

Two modes. No body (or {}): the first-funding flow: strategy must be pending_setup. Body amountUsdc: a TOP-UP into an active, uncovered strategy: only the new amount is planned. Gates: a 10 USDC floor on the total; every bridged portion must clear 20x its LIVE relay cost (priced by the same relayAndDeposit simulation the rebalance fee engine uses); an in-flight-transfer guard; a 24/hour per-strategy limit. Covered strategies reject top-ups (covered_topup_not_available) until the covered phase ships. While the partial rollout flag is off, top-ups return 503 feature_disabled.

Timing: expiresAt is an advisory ~1h plan-freshness bound. The intent itself has a 30-day TTL; regenerating an unchanged plan within it returns the same intentId, and regenerating after expiry or fulfillment mints a new one. A strategy that has never received a deposit is purged about one hour after it was last touched, taking its intent with it; calling this endpoint refreshes that hour. If signing takes longer than an hour (e.g. a multisig), regenerate at least hourly until the transaction is broadcast.

Approve vault share tokens and USDC before calling: live allowances affect vault selection, and approvalsNeeded reflects what is still missing.

Submit the returned data verbatim (re-encoding breaks intent attribution) and use gasHint as the gas limit (wallet re-estimates can run out of gas).

Returns one ready-to-sign selfBatchWithdraw transaction per chain, source chain first then ascending chain id. Sign and submit in that order, data verbatim. Paused and zero-share positions are excluded. Each transaction has its own intentId (kind close), written server-side. No auth; no status gate. Optional chainIds in the JSON body restricts the plan to those chains.

If nothing is withdrawable, transactions is [] and fallback is "delete": close via DELETE /v1/strategies/{id} instead.

PARTIAL withdrawals: body amountUsdc withdraws that gross amount pro-rata across positions (intents kind partial_withdraw, standard 30-day TTL). Requires an active, uncovered strategy; the FLOOR / 90% / minimum-action gates, an in-flight-transfer guard, and a 24/hour per-strategy limit apply. Each remote chain's relay fee is withheld in shares inside that chain's own transaction (partial.feeUsdc is the total; the wallet receives partial.receiveUsdc). Body quote: true returns the policy numbers (withdraw_quote) without writing intents. While the partial rollout flag is off, both forms return 503 feature_disabled.

expiresAt and intent TTL semantics match the deposit endpoint (the pre-deposit purge does not apply). The fee quote is priced at plan time: regenerate past expiresAt rather than signing a stale plan.

Escape hatch for a stalled deposit bridge leg: fetches the finalized Circle attestation and returns one ready-to-sign emergencyClaimBridge transaction on the destination chain. Minted USDC goes directly to the burn-time beneficiary's wallet, bypassing the destination vault deposit. The matching intent (kind emergency_claim) is written server-side. No auth.

Eligibility (each failure is a 400 invalid_state): the transfer must be a deposit leg, not already confirmed or user_claimed, at least 30 minutes old, and its recorded beneficiary must be the strategy owner. If Circle has not finalized the attestation, the response is a 409 attestation_pending; poll on that status code.

approvalsNeeded is always []. expiresAt is nominal: the claim stays valid until the message nonce is consumed on the destination chain. A null gasHint with estimation_failed can mean the nonce was already consumed (the transfer completed normally); the on-chain result is authoritative.