Nbility logoNbility Docs

Search documentation

Search guides and API reference content

Cursor's current BYOK documentation officially lists OpenAI, Anthropic, Google, Azure OpenAI, and AWS Bedrock. It also states that custom keys mainly cover standard chat models; Tab, Auto, and some Agent features continue to use Cursor services. Its API Keys guide does not promise arbitrary OpenAI-compatible gateway support.

Nbility is therefore a conditional integration when a Cursor version exposes a Base URL override, not a stable full-feature integration. For reliable custom gateways, prefer Roo Code, Codex, or OpenCode.

Completion path when the override is available: create a dedicated key → configure Cursor → verify with a short standard chat → confirm the request in Usage Logs.

If your version exposes a Base URL override

  1. Create a dedicated key on Token Management.
  2. Open Cursor Settings → Models / API Keys.
  3. Enter the key under OpenAI settings.
  4. If Override OpenAI Base URL is explicitly available, enter https://api.nbility.ai/v1.
  5. Select a standard chat model available to the key's group. Use Models as the source of truth.

Verify with a short text-only chat first. Do not use Agent, images, Tab, or Auto as the first test: those features may bypass the custom key, use Cursor-owned models, or require protocols that Cursor does not expose to compatible endpoints.

Known boundaries

  • BYOK covers the standard chat models that Cursor explicitly supports; it does not move every Cursor feature to Nbility.
  • Auto, Tab Completion, and some Agent/Apply features may still require a Cursor subscription and will not be billed to the Nbility key.
  • Model discovery, vision, tool calling, and Responses behavior for custom endpoints can change between Cursor releases.
  • If the settings page has no Base URL override, do not edit Cursor's internal database or undocumented settings to force one.

Troubleshooting

  • 401: verify the key directly with the cURL example in API Quickstart.
  • Key verification fails: Cursor may still apply official OpenAI validation. Nbility cannot fix client-side validation rules.
  • Plain chat works but Agent/images fail: use a client with explicit arbitrary OpenAI Compatible provider support.
  • Model missing: Cursor may not expose every gateway model. Use its custom-model UI when available or switch clients.

Bottom line: Cursor is a conditional compatibility option, not the preferred Nbility custom-gateway client.