U9 AI · DOCUMENTATION
Cursor setup
Configure Cursor with the correct U9 address, model and compatibility checks.
Download Markdown ↓Compatibility and prerequisites#
This guide prepares Cursor integration with U9 AI. You need an active U9 key, sufficient credit and an available model matching the endpoint. Official documentation was checked on 2026-10-24; this is not an end-to-end test of every client version or upstream model.
Setup steps#
- First confirm your Cursor version exposes custom OpenAI Base URL and model settings. Official BYOK support does not establish arbitrary gateway compatibility.
- Only if those controls exist, open Cursor Settings → Models API settings and preserve the previous configuration.
- Point the custom base URL to the U9 /v1 address, enter your U9 key and available model ID, then test chat.
- If the controls are absent, validation rejects the gateway or the feature needs built-in models, stop and use an explicitly custom-endpoint-capable tool such as Cline or Continue.
Configuration values#
| Setting | Value |
|---|---|
| Base URL | https://u9ai.ai/v1 |
| API Key | YOUR_U9AI_API_KEY · U9 API key |
| Model | YOUR_CHAT_MODEL_ID · Available model ID |
| Expected chat endpoint | https://u9ai.ai/v1/chat/completions |
Important differences#
This is a conditional guide, not a claim of current end-to-end U9 support. Tab completion still uses built-in models. Cursor may route requests through its own backend; do not assume a direct client-to-U9 connection.
Acceptance and handoff#
First follow quickstart to check GET /v1/models without generating content. Then test a short non-streaming request, streaming and any required tool-call round trip separately. Generation tests may incur charges. Record the request ID and verify cost analysis. For failures, include client version, model ID, endpoint, status and sanitized errors in a ticket. Do not blindly resubmit timed-out jobs.
Give this Markdown file to your developer or agent. Ask it to preserve current settings, substitute only available model IDs and report untested capabilities. Never put real keys in shared Markdown.