Cursor

Home Docsagents/cursor

Gateway Protocol v1 · Production Reference

Documentation

One key, two compatible wire protocols, 15 frontier models. Read the quickstart or explore the API reference.

Coding agents · Cursor

Cursor is an AI code editor built on VS Code. Its own agent runs against Cursor's hosted models and does not accept a custom base URL, so the gateway reaches Cursor through the OpenAI-compatible extension path.

Create an API key on the API Keys page and export it as $SELORA_API_KEY before continuing.

Install an OpenAI-compatible agent

Cursor installs VS Code extensions, so you can run a gateway-backed agent inside it. Cline and Kilo Code both read a custom base URL, which Cursor's built-in models cannot.

Install in Cursor

code --install-extension saoudrizwan.claude-dev

Run this from Cursor's integrated terminal, or install from the Extensions panel. The extension appears in Cursor's sidebar once loaded.

Configure the extension against the gateway

Open the extension settings and choose its OpenAI-compatible provider. Enter the gateway endpoint and your Selora key.

Extension settings

API Provider:  OpenAI Compatible
Base URL:      https://api.selora.lol/v1
API Key:       sk-gw-...
Model ID:      claude-sonnet-5

Cursor's built-in chat and Tab completion keep using Cursor's own models and billing. Only the extension you configure here is billed to your Selora wallet.

Why not Cursor's own model picker

Cursor's model list is served from Cursor's backend, and its settings expose an OpenAI API key field only for Cursor's own routing. There is no supported setting that redirects Cursor's native agent at a third-party gateway, so a Selora key cannot be used there.

If your Cursor build does expose a custom base URL under Settings, it would live alongside the OpenAI API key field. Treat that as unverified: Cursor changes this surface between releases, and Cursor's own documentation does not describe a third-party gateway path.