From 74553a57b8b0c1cb9282a8bd6504dace8931e2ac Mon Sep 17 00:00:00 2001 From: Bryan Fawcett Date: Wed, 12 Aug 2026 11:32:01 +0000 Subject: [PATCH] fix(site): api.mukoko.com is an unbuilt gateway, not a legacy host; name the real WorkOS project MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Two factual errors #62 deliberately left for a separate PR, because they are different claims about different things. 1. `api.mukoko.com` was documented as a "Legacy host" (api/overview) and "Legacy production host" (api/security). It is neither. `getent hosts api.mukoko.com` returns nothing and `GET https://api.mukoko.com/health` returns 000 (connection failure, not a redirect); `https://api.nyuchi.com/health` returns 200 `{"status":"healthy",...,"version":"4.1.0"}`. Per the ecosystem architecture, api.nyuchi.com is the gateway serving traffic today (FastAPI on Fly, nyuchi/api-gateway) and api.mukoko.com is a SEPARATE Mukoko gateway still being built. "Legacy" tells a reader the opposite of what is true: that it used to work, rather than that it does not work yet. Both rows are corrected rather than deleted — the name is real (it is in the gateway's own `DEFAULT_TRUSTED_HOSTS` in gateway/lib/security.py, allow-listed ahead of the host existing), so a reader who has heard it needs somewhere to find out what it is. Each page carries a "do not reword this back" note so the not-legacy/not-yet-built distinction survives a future editing pass. 2. deployment/agentgateway named a "Nyuchi Identity" WorkOS project. No such project exists: the account (team "Mukoko Account") has exactly ONE project, `Mukoko Account` (project_01KQBBSK9062YGVJB6JWW3BMN8), with two environments — `Staging` (sandbox) and `Production`. The Connect app's environment (Production) was already right; only the project name was wrong. Swept every mention of the other three hosts plus nyuchi.dev and found no further errors: the four-host table #62 added is confirmed live (accounts.mukoko.com/.well-known/openid-configuration self-identifies as that issuer; auth.mukoko.com/.well-known/oauth-authorization-server 404s, which is exactly the dead-end #62 warns about), every api.nyuchi.com curl example is on the host that answers, and the one nyuchi.dev URL (tester.fundi.nyuchi.dev) is an explicitly internal-only agent, not a consumer surface. The Kweli MCP is documented at kweli.mukoko.com/mcp, which answers 200. Co-Authored-By: Claude Opus 5 Claude-Session: https://claude.ai/code/session_01HFaeL83iEL5gqQXhHweH6u --- site/src/content/docs/api/overview.mdx | 19 +++++++++++++++---- site/src/content/docs/api/security.mdx | 12 ++++++++++-- .../content/docs/deployment/agentgateway.mdx | 8 +++++--- 3 files changed, 30 insertions(+), 9 deletions(-) diff --git a/site/src/content/docs/api/overview.mdx b/site/src/content/docs/api/overview.mdx index 8656c11..d23c522 100644 --- a/site/src/content/docs/api/overview.mdx +++ b/site/src/content/docs/api/overview.mdx @@ -9,10 +9,21 @@ The Nyuchi API is a single versioned HTTP gateway. Every endpoint lives under a ## Base URL -| Environment | URL | -|-------------|-----| -| Production | `https://api.nyuchi.com` | -| Legacy host | `https://api.mukoko.com` | +| Host | What it is | +|------|------------| +| `https://api.nyuchi.com` | **Production — the gateway serving traffic today** (FastAPI on Fly.io). Point every client here. | +| `https://api.mukoko.com` | A **separate Mukoko gateway still being built.** It serves nothing usable yet and has no DNS record, so a request to it fails to connect. | + +