Skip to main content
Cursor currently provides OpenAI API Key and Override OpenAI Base URL settings, allowing connection to OpenAI-compatible services. This capability exists, but different versions do not handle /chat/completions, /responses, model lists, and modes such as Agent/Composer in exactly the same way. The compatibility range may vary across different Cursor versions, operating systems, and request modes. Please complete the actual mode checks according to the configuration on this page, and do not infer that all functions are available based on a single successful chat.

​
What Cursor Official BYOK Currently Guarantees

According to the Cursor official Bring your own API key documentation:
  • Supports credentials for OpenAI, Anthropic, Google, Azure OpenAI, and AWS Bedrock;
  • Custom API Keys are only used for chat models, while Tab completion continues to use Cursor’s built-in models;
  • API Keys are not persisted on Cursor servers, but each request sends the Key to the Cursor backend for final prompt building;
  • When using your own Key, Cursor’s Zero Data Retention policy does not apply, and data processing follows the policy of the selected provider.

​
Configuration

  1. Open Cursor Settings → Models.
  2. Enter your Ace Data Cloud API Token in OpenAI API Key.
  3. Enable Override OpenAI Base URL and enter https://api.acedata.cloud/v1.
  4. Select or add the exact model ID compatible with the current Cursor protocol.
  5. First send Reply only OK, then separately test the modes you actually use, such as Ask/Edit/Agent.

​
Current Boundaries

  • Custom API Keys are only used for chat models, while Tab completion continues to use Cursor’s built-in models.
  • Cursor may still perform final prompt building on the server side; please evaluate the data path together with the official privacy documentation.
  • Base URL Override may only cover some requests, or may switch between Chat Completions/Responses due to version changes.
  • A successful single chat request alone should not be used to claim that Agent, Auto, Composer, or background tasks are all connected.

​
Currently Available Options

When using the Coding Plan, prioritize clients with clearly defined configuration contracts and verification gates:

​
Complete Compatibility Check

If you want to use it long-term in a production workflow, please also complete the following checks:
  1. Fix the Cursor version and operating system;
  2. Complete a real client smoke test for that version, and record the final request protocol and path;
  3. The exact model’s Chat Completions request succeeds;
  4. Tool calls and Agent requests actually pass through the target endpoint;
  5. Usage and charges can be reconciled;
  6. Clearly record whether requests pass through Cursor servers and the corresponding privacy limitations.
After upgrading the client, these checks should be performed again to confirm that the request protocol, tool calls, and data path have not changed.

​
Official References