list_my_positions

One row per (topic, option) the key owner holds. With v21_lmsr a user places at most one order per topic — positions cannot be added to or switched. Selling a position is only available in the SeeSaw app; a position the user sold there shows up here as sold: true. Scope: read · Annotations: readOnlyHint REST equivalent: GET /open/v1/me/positions

Parameters

Name	Type	Default	Notes
`range`	`all` \| `month`	`all`	`month` = positions placed this calendar month (Hong Kong time)
`sort`	`latest` \| `settled`	`latest`	`latest` = most recent order first; `settled` = largest ruby payout first — use it for settled outcomes
`cursor`	string	—
`limit`	integer ≤ 100	20
`language`	see languages	`en`

Returns

stake_coins is the coins the order spent. units is the raw unit count, before any ruby boost. A correct option pays units × the order’s ruby multiplier (1 without a boost), and the stake itself is not returned. While the position is open, payout_if_correct_rubies carries a guaranteed minimum — units × the order’s current multiplier; if the topic settles while a ruby boost is live, it pays at the higher multiplier. Once the topic settles, payout_rubies is what settlement actually paid. See Rubies and positions. Branch on sold first, then refunded, then settled. settled and settled_at describe the topic, so they alone do not tell you whether won is readable. A settled: true row with a null won is a sale or a refund, not a server-side error.

Field	Open	Settled	Sold (in the app)	Refunded (ruled invalid)	Refunded (ops takedown)
`sold`	`false`	`false`	`true`	`false`	`false`
`sold_rubies`	`null`	`null`	rubies the sale paid	`null`	`null`
`settled`	`false`	`true`	`true` once the topic settles	`true`	`false`
`refunded`	`false`	`false`	`false`	`true`	`true`
`invalid_reason`	`null`	`null`	`null`	e.g. `no_winner`	`null`
`won`	`null`	`true` / `false`	`null`	`null`	`null`
`payout_rubies`	`null`	what settlement paid when won, `"0.0000"` when not	`null`	`null`	`null`
`payout_if_correct_rubies`	guaranteed minimum (`v21_lmsr`)	`null`	`null`	`null`	`null`

A sold position no longer takes part in settlement. Whatever the topic’s outcome — even if the sold option wins, or the topic is ruled invalid — the row keeps won, payout_rubies and payout_if_correct_rubies at null and refunded at false. What the user received is sold_rubies. Don’t report a win or a payout for a sold row.A refunded position got its stake back — it is neither a win nor a loss, and won / payout_rubies are null exactly like an open row. The two refund paths differ: an invalid ruling is terminal and carries invalid_reason, while an ops takedown returns the stake with no ruling at all (settled: false, invalid_reason: null, and the topic may still be active). refunded: true with a null invalid_reason is valid, not a missing field. Such positions stay visible to their holder on purpose — the money moved, so the row has to be findable.

The row carries no sale time. To find when a position was sold, look for its ruby_trade_sell entry in list_my_ruby_ledger. Example — one open position placed during a 2× ruby boost, and one position sold in the app on a topic that has since settled:

{
  "data": [
    {
      "topic": {
        "id": "a3f21c48-6b19-4d7e-9c04-8e5b2f7a1d63",
        "title": "Will the Fed cut rates at the November 2026 meeting?",
        "status": "active",
        "mechanism": "v21_lmsr",
        "close_time": "2026-10-06T23:34:02.46058Z",
        "url": "https://seesaw.fun/topic/a3f21c48-6b19-4d7e-9c04-8e5b2f7a1d63"
      },
      "option": {
        "id": "b1c0d9e8-4a72-4f31-95d6-0c1e7a83b402",
        "label": "Yes",
        "index": 0
      },
      "stake_coins": "300.0000",
      "units": "596.9780",
      "entry_price": "0.4988",
      "current_price": "0.5063",
      "settled": false,
      "settled_at": null,
      "refunded": false,
      "invalid_reason": null,
      "won": null,
      "payout_rubies": null,
      "payout_if_correct_rubies": "1193.9560",
      "sold": false,
      "sold_rubies": null
    },
    {
      "topic": {
        "id": "d4e3f2a1-7c95-4b64-a8f9-2e3a9c05d624",
        "title": "Will Manchester City win the 2026 Community Shield?",
        "status": "resolved",
        "mechanism": "v21_lmsr",
        "close_time": "2026-09-20T14:00:00Z",
        "url": "https://seesaw.fun/topic/d4e3f2a1-7c95-4b64-a8f9-2e3a9c05d624"
      },
      "option": {
        "id": "e5f4a3b2-8da6-4c75-b90a-3f4b0d16e735",
        "label": "Yes",
        "index": 0
      },
      "stake_coins": "200.0000",
      "units": "380.1234",
      "entry_price": "0.5200",
      "current_price": "0.8120",
      "settled": true,
      "settled_at": "2026-09-21T11:00:00Z",
      "refunded": false,
      "invalid_reason": null,
      "won": null,
      "payout_rubies": null,
      "payout_if_correct_rubies": null,
      "sold": true,
      "sold_rubies": "285.0000"
    }
  ],
  "next_cursor": null,
  "has_more": false
}

Settled outcomes live here too — there is no separate settlements tool. Pass sort=settled to lead with them.

Example prompts

“What positions am I holding?”
“How did my settled predictions turn out?”
“Which positions did I sell in the app, and for how many rubies?”

get_my_profile · list_my_ruby_ledger · preview_order · Rubies and positions

Getting Started

Concepts

MCP Server

Platform

Parameters

Returns

Example prompts

​Parameters

​Returns

​Example prompts

​Related

Parameters

Returns

Example prompts

Related