NEW

Jev is now available

Model prices

Connect Cursor to ApiClo

Use Cursor's custom OpenAI-compatible connection for supported chat workflows. A custom API key does not automatically unlock every Cursor feature or guarantee full agent compatibility.

Before you start

  • Prepare an ApiClo API key and check the current Cursor-specific model guidance in ApiClo documentation.
  • Use a Cursor version with custom API key and Base URL settings. Setting names can differ between versions; check Cursor's current documentation.
Create an API key

Steps

  1. Open model settings

    In Cursor settings, locate the model/API key section and the OpenAI-compatible custom Base URL option.

  2. Set URL and key

    Use https://apiclo.com/v1 and your ApiClo API key. Do not use a provider's own key here and do not append /chat/completions to the Base URL.

  3. Choose the supported model ID

    Copy the Cursor-compatible ID or alias from the current ApiClo guide. An arbitrary renamed model may fail client validation even when it works through direct API.

Check the result

Enable the configured model and send a short chat message. Confirm the response and the ApiClo usage entry before attempting larger tasks. Do not use a successful chat response as proof that autocomplete, agent tools or every plan feature works.

Troubleshooting

  • Authentication failure: check the active ApiClo key and the custom endpoint setting.
  • Model validation failure: use the exact Cursor-compatible ID documented by ApiClo instead of inventing an alias.
  • Chat works but agent tools fail: this is a separate compatibility check. Consult the full guide; Cline, Kilo or Roo may suit a coding-agent workflow better.

Compatibility and billing

Cursor controls its own feature availability and subscription rules. ApiClo usage is billed separately according to the selected-model tariff. This guide does not promise that a custom key replaces a Cursor subscription, bypasses regional restrictions, or supports every agent feature.

All documentation