docs: auto-update for v2.50.7

Author: github-actions[bot]

docs/api-reference/openapi.json

@@ -3,7 +3,7 @@
   "info": {
     "title": "PMXT Hosted API",
     "description": "One API for every prediction market. Cross-venue search in under 10ms, a single unified schema, and the complete venue surface from reads to trades.",
-    "version": "2.50.6"
+    "version": "2.50.7"
   },
   "servers": [
     {

docs/concepts/venues.mdx

@@ -7,7 +7,7 @@ description: "Every venue PMXT currently speaks."
   AUTO-GENERATED from pmxt-core's openapi spec (ExchangeParam enum).
   Do not edit by hand — run `npm run generate:mintlify` to regenerate.
   Source: docs/api-reference/openapi.json
-  pmxt-core version at last sync: 2.50.6
+  pmxt-core version at last sync: 2.50.7
 */}
 
 PMXT Hosted currently supports the following venues. The **wire key** is

docs/llms-full.txt

@@ -240,7 +240,7 @@ From a fresh `pmxt_api_key` to a confirmed position on Polymarket in under a min
 
 
 > **Note:**
-Hosted writes today: **Polymarket** and **Opinion**. Other venues are read-only via the hosted catalog; use [self-hosted](https://pmxt.dev/docs/guides/self-hosted) to trade them.
+Hosted writes today: **Polymarket**, **Opinion**, and **Limitless**. Other venues are read-only via the hosted catalog; use [self-hosted](https://pmxt.dev/docs/guides/self-hosted) to trade them.
 
 
 #### 1. Get an API key
@@ -519,7 +519,7 @@ deposit_tx = client.escrow.deposit_tx(amount=10.0)
 
 See [Trading quickstart](https://pmxt.dev/docs/trading-quickstart) for the full 60-second flow
 and [Escrow lifecycle](https://pmxt.dev/docs/guides/escrow-lifecycle) for the approve / deposit /
-withdraw mechanics. Hosted writes today: Polymarket and Opinion.
+withdraw mechanics. Hosted writes today: Polymarket, Opinion, and Limitless.
 
 ##### Self-hosted / direct venue credentials (advanced)
 
@@ -661,7 +661,7 @@ For on-chain venues (Polymarket, Limitless, Probable, Opinion, Baozi), "venue cr
 
 Credential type is a property of the venue, not of PMXT. See [Supported Venues](https://pmxt.dev/docs/concepts/venues) for the full credential matrix. The difference between modes is **where the credential lives**:
 
-- **Hosted (Polymarket, Opinion):** PMXT never sees the venue private key. You sign EIP-712 locally against the `PreFundedEscrow` domain; PMXT's operator submits with its own key for gas. See [Hosted trading](https://pmxt.dev/docs/concepts/hosted-trading).
+- **Hosted (Polymarket, Opinion, Limitless):** PMXT never sees the venue private key. You sign EIP-712 locally against the `PreFundedEscrow` domain; PMXT's operator submits with its own key for gas. See [Hosted trading](https://pmxt.dev/docs/concepts/hosted-trading).
 - **Self-hosted (any venue):** the venue credential lives on your machine, in your `pmxt-core` process.
 
 #### Recommendations
@@ -997,7 +997,7 @@ Hosted trading is PMXT's default execution path. You provide an API key and a wa
 
 
 > **Note:**
-  **One chain to fund: Polygon.** All hosted trading uses a single Polygon-based `PreFundedEscrow` contract for every supported venue. Fund USDC on Polygon once and your same wallet and key trade Polymarket *and* Opinion (and future venues). For non-Polygon venues like Opinion (on BSC), PMXT handles cross-chain settlement transparently — you never sign anything on a chain other than Polygon. Pass any EVM-compatible private key.
+  **One chain to fund: Polygon.** All hosted trading uses a single Polygon-based `PreFundedEscrow` contract for every supported venue. Fund USDC on Polygon once and your same wallet and key trade Polymarket, Opinion, *and* Limitless (and future venues). For non-Polygon venues like Opinion (on BSC), PMXT handles cross-chain settlement transparently — you never sign anything on a chain other than Polygon. Pass any EVM-compatible private key.
 
 
 #### When hosted mode is right
@@ -1006,7 +1006,7 @@ Hosted is the right default for:
 
 - **Web and mobile apps** — your backend holds the `pmxt_api_key`; users keep their own private keys on their devices.
 - **Trading bots that don't need sub-100ms latency** — typical hosted round-trip is ~150–300ms including the venue submit.
-- **Multi-venue strategies** — you stay on one HTTP surface even when you're trading across Polymarket and Opinion.
+- **Multi-venue strategies** — you stay on one HTTP surface even when you're trading across Polymarket, Opinion, and Limitless.
 - **Anyone who doesn't want to operate infrastructure.**
 
 A hosted trade has three actors: **your client** (holding the `pmxt_api_key` and, for writes, the user's `private_key`), **`trade.pmxt.dev`** (PMXT's hosted trading API — routes orders, operates against the escrow contract under user-signed authorization, talks to the venue), and **the venue** (Polymarket's CLOB, Opinion's matching engine, etc. — sees PMXT as the submitter).
@@ -1039,7 +1039,7 @@ Step-by-step:
 1. **Build.** The SDK calls `POST /v0/trade/build-order` with the catalog UUIDs (`market_id`, `outcome_id`), side, and amount. The server resolves the venue-native fields (token IDs, salt, expiry, fees), packages them into the venue's EIP-712 typed-data shape, and returns a `built_order_id` plus the payload to sign.
 2. **Sign.** The SDK signs the typed-data payload locally with your `private_key`. This step never leaves your process. See [Signing](https://pmxt.dev/docs/guides/signing) for the exact shape.
 3. **Submit.** The SDK calls `POST /v0/trade/submit-order` with the `built_order_id` and the signature. The server attaches the signature to the prepared order and submits to the venue.
-4. **Settle.** The venue matches the order. On Polymarket, fills come from the CLOB and are settled on Polygon via the CTF exchange. On Opinion, settlement uses a dual-signature cross-chain flow.
+4. **Settle.** The venue matches the order. On Polymarket, fills come from the CLOB and are settled on Polygon via the CTF exchange. On Opinion, settlement uses a dual-signature cross-chain flow into a BSC-side `VenueEscrow`. On Limitless, buys are settled on Polygon directly from escrow; sells use a Base-side pull leg that draws against the user's Polygon escrow.
 
 `create_order` is a convenience wrapper that chains build → sign → submit in one call. `build_order` and `submit_order` are the lower-level primitives if you want to inspect or modify the typed-data before signing.
 
@@ -1078,7 +1078,7 @@ Current operator addresses (immutable on the deployed contracts above):
 - BSC `VenueEscrow.operator`: `0x84194eae9c63C1e3A769976bb762506d3443156d`
 - Polygon `PreFundedEscrow.settlementOracle`: `0x8aD93c0D15bC655b460dD700B1E25C86D1a728EE`
 
-The operator address is currently an EOA controlled by PMXT. A multisig replacement is planned but not yet deployed; this page will be updated when it lands.
+The operator address is an EOA controlled by PMXT. Because `operator` is `immutable` on the deployed contracts, switching to a multisig would mean deploying new escrow contracts and migrating user balances — not an in-place rotation.
 
 ##### Trust model
 
@@ -1108,7 +1108,7 @@ Self-hosted runs `pmxt-core` on your own machine; the SDK talks to `localhost`.
 | **Writes** | `trade.pmxt.dev/v0/trade/{build,submit}-order` | Direct to the venue API |
 | **Custody** | Non-custodial: USDC in `PreFundedEscrow`, movable only against your EIP-712 signature | You retain venue-native custody |
 | **Latency** | ~150–300ms round-trip | Limited by venue + your network |
-| **Trading venues** | Polymarket, Opinion | Every venue PMXT supports |
+| **Trading venues** | Polymarket, Opinion, Limitless | Every venue PMXT supports |
 | **Read-only venues** | All catalog venues via Router | All catalog venues via Router |
 | **Infra to run** | None | One local process |
 | **Regulatory posture** | Non-custodial escrow; user retains beneficial ownership and unilateral withdrawal | You as direct counterparty to the venue |
@@ -1121,7 +1121,8 @@ Choose self-hosted when you need **sub-100ms latency**, want to use **raw venue
 | ----- | ------------- | ------------ | ----- |
 | Polymarket | Yes | Yes | Polygon escrow, CLOB exchange |
 | Opinion | Yes | Yes | Cross-chain (BSC settlement, dual-signature) |
-| Kalshi, Limitless, Smarkets, Probable, Myriad, Metaculus, etc. | No | Read-only via catalog | Use [self-hosted](https://pmxt.dev/docs/guides/self-hosted) for writes |
+| Limitless | Yes | Yes | Polygon buy leg, Base pull-sell leg |
+| Kalshi, Smarkets, Probable, Myriad, Metaculus, etc. | No | Read-only via catalog | Use [self-hosted](https://pmxt.dev/docs/guides/self-hosted) for writes |
 
 If a venue you need isn't here, run pmxt-core locally and pass raw venue credentials — see [Self-hosted](https://pmxt.dev/docs/guides/self-hosted).
 
@@ -1212,7 +1213,7 @@ Hosted trading on PMXT settles through a non-custodial `PreFundedEscrow` smart c
 
 
 > **Note:**
-  **You fund Polygon only.** USDC always sits in the Polygon `PreFundedEscrow` — the single funding location for *every* hosted venue (Polymarket today, Opinion today, more coming). For venues that don't live on Polygon (e.g. Opinion on BSC), PMXT operates an internal cross-chain leg that holds outcome tokens on the venue's chain; you neither fund nor sign anything on that side. Pass any EVM-compatible private key — the same key handles every venue.
+  **You fund Polygon only.** USDC always sits in the Polygon `PreFundedEscrow` — the single funding location for *every* hosted venue (Polymarket, Opinion, and Limitless today; more coming). For venues that don't live on Polygon (e.g. Opinion on BSC), PMXT operates an internal cross-chain leg that holds outcome tokens on the venue's chain; you neither fund nor sign anything on that side. Pass any EVM-compatible private key — the same key handles every venue.
 
 
 #### Why escrow at all?
@@ -1223,7 +1224,7 @@ For Opinion, the same Polygon escrow balance funds a cross-chain settlement leg
 
 #### The `client.escrow` namespace
 
-Hosted exchange clients (Polymarket, Opinion) expose an `escrow` namespace. Every method **builds an unsigned transaction**. Your wallet — MetaMask, ethers `Wallet`, viem, web3.py, etc. — is responsible for signing and broadcasting it. PMXT never holds your private key.
+Hosted exchange clients (Polymarket, Opinion, Limitless) expose an `escrow` namespace. Every method **builds an unsigned transaction**. Your wallet — MetaMask, ethers `Wallet`, viem, web3.py, etc. — is responsible for signing and broadcasting it. PMXT never holds your private key.
 
 | Method (Python / TypeScript) | Description |
 | ---------------------------- | ----------- |
@@ -1938,12 +1939,12 @@ Pick self-hosted if **any** of these apply:
 - **Sub-100ms latency** — local submission removes a network hop. Matters for latency-sensitive arb / market-making.
 - **Raw venue credentials** — Polymarket L2 API keys, Kalshi RSA, Smarkets session cookies. Hosted mode doesn't accept these.
 - **Regulatory custody** — you must be the direct counterparty with no intermediary in the custody path.
-- **Venues hosted mode can't write to yet** — hosted writes are Polymarket + Opinion. Self-hosted writes work on every venue PMXT supports (Kalshi, Limitless, Smarkets, Probable, Myriad, Metaculus, etc.).
+- **Venues hosted mode can't write to yet** — hosted writes are Polymarket, Opinion, and Limitless. Self-hosted writes work on every venue PMXT supports (Kalshi, Smarkets, Probable, Myriad, Metaculus, etc.).
 - **OSS contribution** — you're hacking on `pmxt-core` itself.
 
 #### When hosted is still the better choice
 
-Everyone else. [Hosted](https://pmxt.dev/docs/concepts/hosted-trading) is simpler to deploy (no local process), gives you on-chain custody you control via the timelock, and PMXT's server never sees a private key. If you're building a consumer app, a research notebook, or any non-latency-critical service against Polymarket or Opinion, stop here and use hosted.
+Everyone else. [Hosted](https://pmxt.dev/docs/concepts/hosted-trading) is simpler to deploy (no local process), gives you on-chain custody you control via the timelock, and PMXT's server never sees a private key. If you're building a consumer app, a research notebook, or any non-latency-critical service against Polymarket, Opinion, or Limitless, stop here and use hosted.
 
 #### 1. Install pmxt-core