@c8ntinuum/infinity-interop-sdk is the TypeScript SDK for the Infinity hub’s partner API. It runs
the whole order flow for you: quote, the user’s wallet steps, submission, tracking, history and
refunds. It checks every quote against what the user asked for before anything is signed.
It is built only on the partner contract (the API reference), and calls
the hub’s gateway under /v1 with your secret API key or your public project id.
How a partner uses it
Your secret API key stays on your backend. A web page reaches the hub one of two ways: through your backend’s proxy server (createInteropProxy), which forwards its calls with your key, or
straight to the hub’s gateway with your public project id (projectTransport), which opens
every route but the order history:
- Backend only (bots, treasury moves, scripts):
hubTransport+createInteropClient, with keys the server holds. See the quickstart. - Browser app with your backend: your backend mounts
createInteropProxy; the browser usesproxyTransportand the user’s own wallet. Every route is open this way, the order history and refunds included, and your backend keeps each user’s orders to that user: by its own records, or by naming the user to the hub (X-Infinity-Subject). See Partner backend and Browser apps. - Browser app with a project id: no server of yours; the browser uses
projectTransport, and follows and refunds the orders it submits itself. Only the order history is not open to a project id. See Browser apps.
What it handles
Entry points
Installation
Requirements, the package and its entry points.
Quickstart
Quote, check and execute a bridge from Node with your secret key.
Partner backend
Hold the secret key and serve your frontend 1:1 with
createInteropProxy.Browser apps
proxyTransport or a project id with projectTransport, the user’s wallet, and a bridge screen step by step.Wallets
EIP-1193, viem, Wallet Standard and server-held keys, with chain-instance pins.
Lanes
What the user does on each lane, and what the SDK checks.
Quotes and checks
Requests, reverse quotes, preview and prepare, timing, and the pre-signing checks.
Executing orders
executeQuote, its events and result, tracking and lost answers.Order history
Paging, readable rows and tracking an order later.
Refunds
When an order is refundable, and refunding it on EVM and Solana.
Errors
Error classes, what to tell the user, and what to retry.
API reference
Every export by entry point, and the route each low-level call maps to.
Testing
The test hub, keys from the hub dashboard, safe test wallets, and the runnable examples.