release: 2.50.8 — canonical Hosts section + rate-limits disambiguated

Author: realfishsam

changelog.md

@@ -2,6 +2,17 @@
 
 All notable changes to this project will be documented in this file.
 
+## [2.50.8] - 2026-06-18
+
+### Docs
+
+- **Canonical "Hosts" section.** PMXT serves two hostnames — `api.pmxt.dev` (reads, Router, MCP, venue passthrough) and `trade.pmxt.dev` (hosted writes + hosted account state) — and the docs explained that split in different words on `docs/introduction.mdx`, `docs/sdk/server.mdx`, and implicitly across hosted-trading/security/migrate. A builder reading any one page in isolation couldn't see the full picture; a builder reading `docs/authentication.mdx` or `docs/rate-limits.mdx` (which only mentioned `api.pmxt.dev`) couldn't tell `trade.pmxt.dev` existed. Three parallel agents pinned this to one canonical location.
+- **`docs/authentication.mdx`**: Added a `## Hosts` section at the top of the page (slug `#hosts`). Nine lines: lists both hosts and what each serves, confirms the same `pmxt_api_key` authenticates against both, one line on why the split exists (latency and availability profile for the signed-order submission hot path).
+- **`docs/rate-limits.mdx`**: Disambiguated which limits apply to which host. Added a line after the intro stating the per-API-key limits apply across both hosts (linking to `/authentication#hosts`), and clarified below the table that the `/v0/*` row covers both `api.pmxt.dev/v0/*` (Router) and `trade.pmxt.dev/v0/*` (trading) under the same per-key budget.
+- **`docs/introduction.mdx`**: Replaced the bullet that listed both hosts inline with a link to the canonical section, and replaced the matching code comment. Two single-line edits.
+- **`docs/sdk/server.mdx`**: Replaced one inline mention of both hosts with a link to the canonical section.
+- **Files reviewed but not edited (host being USED, not re-explained):** `quickstart.mdx`, `mcp.mdx`, `security.mdx`, `concepts/hosted-trading.mdx`, `concepts/catalog-uuid-vs-venue-id.mdx`, `guides/hosted-errors.mdx`, `guides/migrate-to-hosted-trading.mdx`, `guides/self-hosted.mdx`, `router/search.mdx`, `router/matching.mdx`, `router/event-matching.mdx`. 24 hostname mentions reviewed across all docs; 3 edited across 2 files (plus the canonical section + rate-limits clarification). Every other mention was the host being called in a code example or named in a flow diagram — those stay.
+
 ## [2.50.7] - 2026-06-18
 
 ### Fixed

docs/authentication.mdx

@@ -3,6 +3,17 @@ title: Authentication
 description: "API keys, SDK setup, and venue credentials."
 ---
 
+## Hosts
+
+PMXT serves two hostnames.
+
+- `api.pmxt.dev` — reads, catalog search via Router, MCP server, venue passthrough (`/api/*`).
+- `trade.pmxt.dev` — hosted writes (build / submit / cancel) and hosted account state (orders, positions, balances, trades) via `/v0/trade/*`, `/v0/user/*`, and `/v0/orders/*`.
+
+The same `pmxt_api_key` authenticates against both — no separate credentials.
+
+Reads and writes have different latency and availability profiles; the trading host is the hot path for signed-order submission and is operated independently.
+
 ## API key
 
 Every request to `https://api.pmxt.dev` needs a Bearer token. Get one

docs/introduction.mdx

@@ -20,7 +20,7 @@ New to prediction markets? Start at the [101](/concepts/prediction-markets-101)
 
 It runs two ways:
 
-- **Hosted (default)** — `api.pmxt.dev` and `trade.pmxt.dev` give you a
+- **Hosted (default)** — PMXT's [hosts](/authentication#hosts) give you a
   shared catalog, cross-venue search, and end-to-end [hosted
   trading](/concepts/hosted-trading) with [PreFundedEscrow](/concepts/prediction-markets-101#prefundedescrow) custody. Set
   an API key and the SDK is fully operational.
@@ -34,7 +34,7 @@ The code is identical either way:
 ```python
 import pmxt
 
-# Hosted (default): talks to api.pmxt.dev / trade.pmxt.dev
+# Hosted (default): talks to PMXT's hosts — see /authentication#hosts
 poly = pmxt.Polymarket(pmxt_api_key="pmxt_live_...")
 
 markets = poly.fetch_markets(query="fed rate cut", limit=5)

docs/rate-limits.mdx

@@ -6,6 +6,9 @@ description: "How much traffic your API key gives you."
 Every API key includes the full surface — cross-venue search, unified
 schema, and the complete venue pass-through.
 
+Limits are **per API key** and apply across both hosts (`api.pmxt.dev`
+and `trade.pmxt.dev`) — see [hosts](/authentication#hosts).
+
 ## Limits
 
 {/* HOSTED-AUTOGEN:rate-limits-table:START */}
@@ -15,8 +18,10 @@ schema, and the complete venue pass-through.
 | `/api/*` | 60 | 25,000 |
 {/* HOSTED-AUTOGEN:rate-limits-table:END */}
 
-Every request to `/v0/*` or `/api/*` counts as **1 request**, regardless
-of how much data it returns. Health checks are free.
+The `/v0/*` row covers both `api.pmxt.dev/v0/*` (Router) and
+`trade.pmxt.dev/v0/*` (trading) — the same per-key limits apply across
+both hosts. Every request to `/v0/*` or `/api/*` counts as **1 request**,
+regardless of how much data it returns. Health checks are free.
 
 ## Rate limit responses
 

docs/sdk/server.mdx

@@ -5,8 +5,8 @@ description: "The SDK auto-spawns and manages pmxt-core when running self-hosted
 
 <Note>
 This page covers the **self-hosted** local server. If you're using a
-`pmxt_api_key`, you can ignore this page — the SDK talks to
-`api.pmxt.dev` / `trade.pmxt.dev` directly and never spawns a local
+`pmxt_api_key`, you can ignore this page — the SDK talks to PMXT's
+[hosts](/authentication#hosts) directly and never spawns a local
 process. See [Hosted trading](/concepts/hosted-trading).
 </Note>