Skip to main content
This page is the path from “we want to integrate” to real users trading. Each step links to the page with the detail.

​
1. Get set up with Kairos

Contact Kairos. You get: Decide how you authenticate:
  • An app or wallet whose users sign with their own wallets sends the partner id. Users need no Kairos account.
  • A desk trading its own wallets from a server sends an API key with trade:execute instead. See partner id or API key.

​
2. Make a first trade on staging

Follow the quickstart. It sets up a wallet, places an order that rests, reads it back and cancels it, in about 40 lines.
Staging places real orders on the real venues, with real funds. Use a test wallet with small balances, and orders priced away from the market.

​
3. Build the integration

Use the TypeScript SDK, or call the API directly: plain HTTP clients in JavaScript and Python, and the endpoint reference.

​
4. Go-live checklist

1

Every step type is handled

eth_signTypedData_v4, personal_sign, and wallet_sendCalls (Predict.fun approvals), with the eth_sendTransaction fallback for wallets without wallet_sendCalls. The wallet switches to each step’s chainId first. See the four methods.
2

Users see what they sign

Show each step’s description before the prompt, and check the request matches what the user asked for (checks). The SDK does this for you.
3

Retries never double an order

Send a clientOrderId on every order. When an order ends with ORDER_OUTCOME_UNKNOWN, or a request fails with a 5xx or a timeout, retry with the same clientOrderId, or read the wallet’s orders first (all of them, not only open ones: the order may have filled). See clientOrderId.
4

Signatures arrive in time

Polymarket and Predict.fun orders must be signed within about 60 seconds. Hyperliquid orders, and cancels on every venue, within 5 minutes. A late signature fails with SIGNATURE_EXPIRED: start a new action.
5

The sign-in token is reused

Keep the token from the login action for its 24 hours, rather than asking the user to sign in on every read. See the sign-in token.
6

Venue outages degrade gracefully

Read venues in wallet status and hide a venue that is available: false or not offered. See availability.
7

Limits fit your traffic

Requests are limited per route and per IP (120 a minute, or 1000 with an API key). New wallets are capped at about 1000 an hour per partner. Ask Kairos before a launch that needs more. See rate limits.
8

Kairos enables production

Tell Kairos your launch date. Kairos enables your partner id (and origins and fee schedule) in production.