> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tryorbit.cloud/llms.txt
> Use this file to discover all available pages before exploring further.

# Cursor

> Point Cursor at Orbit's OpenAI-compatible API and run the agent on organization credits.

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](/agents/claude-code). Cursor uses the **OpenAI** surface. Claude Code uses the **Anthropic** surface.

## What you need

* Cursor desktop
* An Orbit API key from [API Keys](https://tryorbit.cloud/api-keys)
* A model slug from the [catalogue](https://tryorbit.cloud/models)

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

<Steps>
  <Step title="Create an Orbit API key">
    Sign in at [tryorbit.cloud](https://tryorbit.cloud), open [API Keys](https://tryorbit.cloud/api-keys), and create a key named `cursor`. Copy the `sk-orbit-...` secret.
  </Step>

  <Step title="Open Cursor model settings">
    In Cursor, open **Settings → Cursor Settings → Models**.
  </Step>

  <Step title="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:

    ```txt theme={"theme":"github-dark"}
    https://api.tryorbit.cloud/api/v1
    ```

    Do not add `/chat/completions`. Cursor (like the OpenAI SDK) appends that path itself.
  </Step>

  <Step title="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.
  </Step>
</Steps>

<Note>
  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.
</Note>

## Alternative: OpenAI-compatible provider

Newer Cursor builds also let you add an **OpenAI compatible** / custom provider:

| Field    | Value                                  |
| -------- | -------------------------------------- |
| Base URL | `https://api.tryorbit.cloud/api/v1`    |
| API key  | `sk-orbit-...`                         |
| Model    | Catalogue slug, e.g. `claude-sonnet-5` |

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](https://tryorbit.cloud/usage) — you should see a new request on the active organization.

## How this maps to the API

Cursor sends standard Chat Completions to Orbit:

```http theme={"theme":"github-dark"}
POST https://api.tryorbit.cloud/api/v1/chat/completions
Authorization: Bearer sk-orbit-...
```

See [OpenAI compatibility](/api/openai) for the same endpoint from Python or Node.

<Warning>
  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.
</Warning>