Настройка Cursor
1. What Cursor is and what to prepare
Section titled “1. What Cursor is and what to prepare”Cursor is an AI IDE based on VS Code. It supports chat, code generation, edits, and explanations directly in the editor.
Before connecting Cursor through RouteAPI, prepare:
- The Cursor desktop app installed and signed in
- Your RouteAPI key
- An OpenAI protocol standard chat model available in the RouteAPI console
- The RouteAPI OpenAI-compatible endpoint
https://www.routeapi.ai/v1
2. Install and open model settings
Section titled “2. Install and open model settings”Install and sign in to Cursor
Section titled “Install and sign in to Cursor”Install the desktop app from the Cursor website and sign in with your Cursor account.
Open Cursor Settings > Models
Section titled “Open Cursor Settings > Models”Open Settings in Cursor, then go to Models.
3. Configure RouteAPI
Section titled “3. Configure RouteAPI”3.1 Enter OpenAI provider access information
Section titled “3.1 Enter OpenAI provider access information”Find the OpenAI settings on the Models page. Field names may vary by Cursor version, but the required information is:
OpenAI API Key: your RouteAPI keyOpenAI Base URL:https://www.routeapi.ai/v1
After entering the values, click Verify.
3.2 Select a model
Section titled “3.2 Select a model”After verification succeeds, open Cursor’s model picker and select an available OpenAI-compatible model returned by RouteAPI.
A safer approach is:
- Prefer a standard chat or coding model marked as OpenAI protocol in the RouteAPI console
- Do not prioritize reasoning models, because Cursor’s official docs state that custom OpenAI API keys only support standard, non-reasoning chat models
3.3 Start using it
Section titled “3.3 Start using it”After configuration, you can use RouteAPI models directly in Cursor Chat or Composer.
4. Notes
Section titled “4. Notes”- The custom API key path mainly affects Chat / Composer standard chat capabilities and does not replace every built-in Cursor capability
- Tab Completion, some Agent capabilities, or features that require dedicated models may still use Cursor’s built-in models
- According to Cursor’s official FAQ, API keys are not stored, but each request is still sent to Cursor’s servers for final prompt assembly
5. Common troubleshooting
Section titled “5. Common troubleshooting”- If
Verifyfails, check the API key and ensure the address ishttps://www.routeapi.ai/v1 - If the expected model is missing, confirm that it supports the OpenAI protocol and is a standard chat model rather than a reasoning model
- If you updated the key or address but Cursor still shows the old state, close and reopen Cursor, then run
Verifyagain - For terminal coding agents, also read Codex configuration, Claude configuration, and OpenCode configuration