Skip to main content
Cursor talks to OpenAI-compatible endpoints. Point it at Orbit, paste your sk-orbit- key, and pick a catalogue slug. Chat, Composer, and Tab then bill your organization at Bedrock list rates. This is a separate setup from Claude Code. Cursor uses the OpenAI surface. Claude Code uses the Anthropic surface.

​
What you need

Good defaults: claude-sonnet-5 for everyday coding, claude-opus-5 or gpt-5-6-sol for harder work, kimi-k2-5 or claude-haiku-4-5 when you want it cheaper and faster.

​
Setup

1

Create an Orbit API key

Sign in at tryorbit.cloud, open API Keys, and create a key named cursor. Copy the sk-orbit-... secret.
2

Open Cursor model settings

In Cursor, open Settings → Cursor Settings → Models.
3

Override the OpenAI base URL

  1. Paste your Orbit key into the OpenAI API Key field.
  2. Enable Override OpenAI Base URL.
  3. Set the base URL to:
Do not add /chat/completions. Cursor (like the OpenAI SDK) appends that path itself.
4

Add Orbit model slugs

Add a custom model for each slug you want in the model picker, for example:
  • claude-sonnet-5
  • claude-opus-5
  • gpt-5-6-sol
  • kimi-k2-5
Select one of those slugs as the model for Chat or Composer.
Cursor’s “Verify” button sometimes fails against third-party gateways even when chat works. If verify errors but a Chat request succeeds, keep the override enabled.

​
Alternative: OpenAI-compatible provider

Newer Cursor builds also let you add an OpenAI compatible / custom provider: Use that if you want Orbit listed as its own provider instead of overriding the built-in OpenAI slot.

​
Confirm it works

  1. Open Chat and pick an Orbit slug.
  2. Ask a short question.
  3. Check Usage — you should see a new request on the active organization.

​
How this maps to the API

Cursor sends standard Chat Completions to Orbit:
See OpenAI compatibility for the same endpoint from Python or Node.
Do not put your sk-orbit- key in a committed .env or a shared Cursor rule. Create a key you can revoke from the dashboard if a machine is lost.