Cursor

Cursor has first-class support for custom OpenAI-compatible endpoints. Routing it through OpenDunes lets you use any model in the catalog — not just the ones Cursor bundles — and keeps all billing in Algerian Dinars on a single balance.

Open Cursor settings#

1. Open Cursor.
2. Go to Settings → Models (macOS: Cmd+,, then search "Models").
3. Scroll down to Custom API Base or OpenAI API Key depending on your Cursor version.

Set the base URL and key#

In the OpenAI Base URL field enter:

https://opendunes.com/api/v1

In the API Key field enter your OpenDunes key (from Dashboard → Keys):

sk-0a1b2c3d4e5f...

Save the settings. Cursor will now route all model calls through OpenDunes.

Add a custom model#

Cursor's model dropdown only shows models it knows about by default. Add OpenDunes models manually:

1. In Settings → Models, click Add Model.
2. Enter the slug exactly as it appears in the OpenDunes catalog, e.g. anthropic/claude-opus-4.8 or google/gemini-2.5-pro.
3. Save.

The model will now appear in Cursor's model picker in the chat panel and Cmd+K inline editor.

Verify#

Open the Cursor chat panel and send a test message. You should get a response within a few seconds. Check Dashboard → Analytics to confirm the request appears and see the DA cost.

Set a budget#

Cursor sessions can accumulate significant token usage — especially with large context or long refactoring sessions. Create a dedicated key with a spend cap:

1. Dashboard → Keys → New key → name it cursor.
2. Set a monthly budget in DA (e.g., 500 DA = 5,000,000 micro-DA).
3. Paste that key into Cursor's API Key field.

When the budget is hit, Cursor will show an error and pause requests until you raise the cap or add balance.

Which models work best in Cursor#

Verify current DA pricing on the models page before committing to a model.

Troubleshooting#

Next steps#

• Models — browse all models with DA pricing and capability flags.
• API Keys — create scoped keys for different tools.
• OpenCode — configure OpenCode CLI through OpenDunes.