Cursor Access to Ace Data Cloud (Experimental)

Cursor currently provides OpenAI API Key and Override OpenAI Base URL settings, allowing connection to OpenAI-compatible services. This capability exists, but different versions handle /chat/completions, /responses, model lists, and Agent/Composer modes inconsistently.

Therefore, this route is marked as experimental: it can be configured and verified according to this page, but there is no commitment that all features will be available until a complete closed loop of the specified Cursor version, operating system, and request mode is achieved.

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 Key is only used for chat models, Tab completion continues to use Cursor's built-in models;
  • API Key is not persisted on Cursor servers, but is sent to the Cursor backend with each request for final prompt building;
  • When using your own Key, Cursor's Zero Data Retention policy does not apply, and data processing follows the policies of the selected provider.

Configuration

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

Current Boundaries

  • Custom API Key is only used for chat models, Tab completion continues to use Cursor's built-in models.
  • Cursor may still complete final prompt building on the server side; please evaluate the data path in conjunction with the official privacy statement.
  • Base URL Override may only cover part of the requests, or switch between Chat Completions/Responses due to version changes.
  • One successful chat request should not be the sole basis for claiming that Agent, Auto, Composer, or background tasks are all connected.

Current Optional Solutions

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

Conditions for Upgrading to Verified Route

Cursor will only upgrade from "experimental" to "verified" route if the following conditions are met:

  1. Fixed Cursor version and operating system;
  2. Complete real client smoke tests for that version, and record the final request protocol and path;
  3. Successful requests for exact model's Chat Completions;
  4. Tool calls and Agent requests indeed go through the target endpoint;
  5. Usage and billing can be verified;
  6. Clearly record whether requests went through Cursor servers and the corresponding privacy restrictions.

If verification records expire or client behavior changes, the selector will automatically disable that combination again.

Official References