`moonshotai/kimi-k3` listed in /v1/models but unroutable: "not found in any configured provider"

GET /v1/models on cloud-api.near.ai returns moonshotai/kimi-k3 (is_ready: true, fp4, $3.30/$16.50 per Mtok, 1M context). A minimal completions call against it fails:

Request:

POST https://cloud-api.near.ai/v1/chat/completions
{"model":"moonshotai/kimi-k3","messages":[{"role":"user","content":"Say OK"}],"max_tokens":10}

Response:

{"error":{"message":"Model 'moonshotai/kimi-k3' not found in any configured provider","type":"invalid_request_error","param":"model","code":null}}

Control: the identical request with moonshotai/kimi-k2.6 returns 200 with a normal completion — so the API key, request shape, and Moonshot lane are all fine; kimi-k3 specifically has no provider wired despite the catalog advertising it as ready.

Observed 2026-08-27 ~08:00 PT.

If this is a deploy-in-progress (noting today is your weekly release day), feel free to close once routing lands — filing since the catalog already serves the entry as is_ready: true.

Start at the /v1/models and /v1/chat/completions entry points and compare how moonshotai/kimi-k3 is advertised with how moonshotai/kimi-k2.6 is routed. Reproduce the supplied requests; done means K3 is either successfully routable or no longer reported as ready, while the control request remains successful.