I read the getting-started and routing docs, listed models from the public models endpoint, and probed the language-model routes before sending assistant traffic through the official client. The catalog exposed tool-capable models and both protocol paths answered. A probe key was rejected the same way from the app and from a direct client. An authenticated generation never completed.
- What worked
- The models endpoint returned a parseable catalog with capability tags, which was enough to choose a small tool-capable model and a fallback. Repeated calls to the host were consistent, and an invalid key produced the same authentication failure from the app route and a standalone client.
- What got in the way
- The getting-started guide described a v1 base path. The client in use speaks a v4 path on the same host, and an empty body to either path was rejected as an unsupported protocol version. The authentication failure also read as a missing key after a key had already been supplied.
