Limitless

This is a reference for the verification API’s payload adapter. For apps you can use inside a Desk, see Desk apps.

venue: limitless. Over HTTP, limitlessexchange and lmts also resolve to it.

What to send

Payload	`actionType`	`actionFamily`	Detected without `venue`
The `POST /orders` body: `{order: {...signed struct...}, ownerId, orderType, marketSlug}`, optionally with `postOnly`, `clientOrderId` or `onBehalfOf`	`order`	`order`	Yes, when `order` has a `tokenId` and a numeric `side`, and `orderType` is `GTC`, `FOK` or `FAK`
A cancel: `{orderId}`, `{orderIds: [...]}`, `{clientOrderId}` or `{clientOrderIds: [...]}`	`cancel`	`order`	No
A redeem: `{conditionId}` (bytes32), optionally with `onBehalfOf`	`redeem`	`position`	Yes, when nothing else is in the body
A withdrawal: `{amount, token?, destination?, onBehalfOf?}`	`withdraw`	`withdrawal`	No

How orders are read

side is 0 for BUY and 1 for SELL. Signed amounts are scaled by 1e6, and the classifier treats them as the source of truth over the advisory price field:

GTC and FAK: price is makerAmount / takerAmount for a buy and takerAmount / makerAmount for a sell. Shares are takerAmount (buy) or makerAmount (sell) divided by 1e6. A price field more than 0.005 away from the signed price is flagged.
FOK: makerAmount is the USDC to spend (buy) or the shares to sell (sell), and takerAmount must be 1.

The summary shows side, shares, price in cents, the outcome token, the market slug, the order type and the maximum cost or proceeds.

Live lookup

For orders, the adapter calls GET https://api.limitless.exchange/markets/{marketSlug} and adds the market title, the outcome (YES or NO), that outcome’s current price, the market status and the deadline. The timeout is 3.5 seconds and results are cached for 5 minutes. The order names its market twice: the slug at the top level and the outcome token inside the signed struct. If the token is neither the market’s YES token nor its NO token, a note says the signed order is for a different market than the one named. If the slug does not resolve, a note says the market is unverified. Both notes tell the judge to lean ESCALATE. A market status other than FUNDED or FUNDED_FLAGGED is flagged, since Limitless only accepts orders on funded markets.

Notes the classifier adds

A price outside 0.01 to 0.99, a non-zero expiration and a non-zero nonce: Limitless rejects all three.
postOnly on anything other than a GTC order.
An order with no signature, which implies delegated signing by a managed wallet.
onBehalfOf, which acts for a sub-account profile, is called out on orders, redeems and withdrawals.
Withdrawals: the amount is USDC scaled by 1e6 when token is absent and raw token units when it is present. With no destination, funds go to the caller’s default destination.

Example

const action = {
  order: {
    salt: "1778155025318314496",
    maker: "0x742d35Cc6634C0532925a3b844Bc454e4438f44e",
    signer: "0x742d35Cc6634C0532925a3b844Bc454e4438f44e",
    taker: "0x0000000000000000000000000000000000000000",
    tokenId: "77592343650315158711139664020320961095667533157390815861422126188027765194664",
    makerAmount: 20000000, // $20.00 of USDC, scaled 1e6
    takerAmount: 500000000, // 500 shares, scaled 1e6
    expiration: "0",
    nonce: 0,
    price: 0.04,
    feeRateBps: 0,
    side: 0, // BUY
    signatureType: 0,
    signature: "0x…",
  },
  ownerId: 12345,
  orderType: "GTC",
  marketSlug: "btc-100k-weekly",
};

const res = await fetch("https://harness.chance.cc/api/v1/intent", {
  method: "POST",
  headers: { "x-api-key": process.env.CHANCE_API_KEY!, "Content-Type": "application/json" },
  body: JSON.stringify({
    intent: "Favorites only: enter only when the chosen outcome is priced at 95c or more. Max $25 per market.",
    venue: "limitless",
    action,
  }),
});
const result = await res.json();
if (result.verdict !== "ALLOW") throw new Error(result.reasoning ?? result.error);
// Only now POST the body to api.limitless.exchange/orders.

From an MCP client

Instruct the agent to call verify_intent before placing any Limitless order, with your rules as intent, the exact request body as action and venue: "limitless", and to act only on ALLOW.

Integrate

Chance verification

Payload adapters

HTTP endpoints

What to send

How orders are read

Live lookup

Notes the classifier adds

Example

From an MCP client

​What to send

​How orders are read

​Live lookup

​Notes the classifier adds

​Example

​From an MCP client

What to send

How orders are read

Live lookup

Notes the classifier adds

Example

From an MCP client