Manifest DEX Integration Guide

Build trading, routing, portfolio, and frontend integrations on top of Manifest's permissionless orderbook.

Overview

Use this skill when the task involves:

Reading Manifest market state or orderbooks

Placing, canceling, depositing, or withdrawing via the Manifest SDK

Choosing between local market balances and global balances

Handling wrapper setup, seat claims, and wallet-adapter flows

Understanding Limit, PostOnly, ImmediateOrCancel, Global, Reverse, and ReverseTight order types

Load supporting references as needed:

resources/manifest-actions.md

resources/manifest-sdk.md

docs/troubleshooting.md

examples/read-market/read-market.ts

examples/wallet-order/place-order.ts

examples/global-liquidity/global-order.ts

examples/reverse-liquidity/amm-style-batch.ts

templates/manifest-setup.ts

Instructions

Determine whether the task is read-only market access or transaction-building.

For read-only access, prefer Market reads or ManifestClient.getClientReadOnly(...).

For transaction-building, use getClientForMarket(...) for signer-controlled flows, or use getSetupIxs(...) first and then getClientForMarketNoPrivateKey(...) for wallet-adapter flows.

Decide whether liquidity should be market-local (wrapper balances plus a market seat) or global (global account plus OrderType.Global).

If the task involves recurring two-sided liquidity, evaluate Reverse or ReverseTight instead of ordinary limit orders.

For UI/orderbook work, prefer bidsL2() and asksL2() for display-ready levels.

When documenting or implementing cleanup behavior, distinguish wrapper-level cancels from core-level cancels. cancelAllIx() does not fully cover all reverse/global edge cases; cancelAllOnCoreIx() is the stronger cleanup path.

State assumptions explicitly:

cluster

market address

trader/signer model

whether wrapper/global setup already exists

Examples

#