Skip to content
IQ

Cursor

Cursor reads model configuration from its in-app settings panel rather than from environment variables. Cursor accepts your own API keys for supported chat models; see Cursor's API-key docs for what your version supports. Sending that traffic through IQ needs Cursor to accept a custom base URL.

Drop-in switch

Open Cursor Settings → Models and choose the provider; follow Cursor's API-key setup guide for the current controls.

If your Cursor version accepts a custom base URL, use https://gateway.iq-routing.com/v1 as the base URL and your IQ API key as the key.

For connection checks and credential errors, follow Cursor's current API-key guidance.

Verify it routes

Send a short chat prompt, then use Requests to inspect the recorded model and cache-hit status; if you have X-Request-Id, open /requests/<uuid> to find that request.

Custom API keys cover Cursor chat models; Tab completion uses Cursor's built-in models, as described in its API-key docs.

Using capability aliases

Use a capability alias to request a suitable model for a task; inspect the response to see the model used and manage your organization's overrides at /settings/capabilities.

For custom model setup, use Cursor's current API-key docs instead of copying version-specific settings keys.

The resolved provider plus model surface in the x-iq-routing response header (a JSON-encoded payload with chosen_provider and chosen_model fields, among others), so the dashboard's /requests view shows which concrete model handled each Cursor request. See the capability aliases docs for the full set of defaults, the focus-mode interaction, and how to override them. The operator can override the default capability mapping via the capabilities dashboard editor at /settings/capabilities.

Common gotchas

If requests do not reach IQ, review Cursor's current setup instructions.

Check Cursor's API-key docs for its current provider setup and supported chat models.

The Composer feature (multi-file edits) sends batched requests. Each one appears as its own row in /requests; the gateway does not collapse them. If you exceed your daily budget mid-Composer-session, the gateway returns 429 with an X-RateLimit-Scope: daily_budget header and the standard OpenAI error body shape; Cursor surfaces that error message in the Composer dialog. See the FAQ for the full list of rate-limit scopes.

Review Cursor's privacy docs and the security docs before changing Cursor's “Privacy Mode” setting.

Try this in the playground

Open the playground for the Cursor recipe →