Skip to main content
Spice Flow connects your application’s protocol calls to users’ wallet assets and Spicenet balances. Users choose how to fund an action; the SDK handles supported routes, conversions, fees, signing and execution. Your app keeps its own contracts, branding and interface. This documentation targets stable UI SDK 4.23.1 and core 0.10.0.

Start with an Action

Mount your existing wagmi, Query and Privy providers, then add SpiceFlowProvider with an explicit network. The Quick Start includes the complete provider stack and a protocol deposit example. A user can fund that deposit within the action, without first moving money into a separate account balance.

Drop-in Components

Define your destination calls once and use SpiceSupply for source selection, review and execution.

Your Own UI

Connect your form to useSpiceSupply and render the same SDK-owned quotes, fees and status.

Cash Funding

Use eligible wallet and escrow balances together inside the requested action.

Conditional Orders

Prepare, review, sign and manage supported scheduled actions and order amendments.

Account Controls

Under the provider stack, add an optional account menu:
SpiceAccount composes account balances, deposits and withdrawals. SpiceDeposit adds account funds; SpiceWithdraw withdraws Spicenet balances. Protocol actions use SpiceSupply, SpiceLock or their controlled hooks. These actions do not require a separate manual account deposit.

Integration Reference

Installation and Setup

Published package versions, peer dependencies and provider setup.

Components and Hooks

Public components, controllers, inventory and account presentation.

Migration to 4.23.1

Upgrade defaults, routed external actions, fees, completion and recovery.

Configuration

Chains, wallets, RPCs, venues and fee policy.

Execution and Recovery

An eligible same-chain action using the connected external wallet’s destination asset can execute directly, with native gas paid by that wallet and no Spicenet routing fee. Other supported actions use the SDK’s funding and execution path. The quote shows applicable fees before submission. Cross-chain actions have several independently confirmed steps. A successful source transfer is not destination completion, and later failure does not revert an earlier chain’s transaction. The SDK tracks the original backend action and verifies destination execution; settlement can continue after the destination receipt is confirmed. See How It Works and Recovery and Completion.

Cross-Chain Swap and Payment

Request a fixed destination payment while the SDK sources the required assets.

API Reference

Actions, execution status and lower-level HTTP integrations.

EIP-7702

Account delegation, signed intents and per-chain execution.

Styling

Match the SDK components to your application’s appearance.

Need Help?

Community

Get help from the Spicenet community and team.

Integration Support

Contact the team about integrating Spice Flow.