← Integrations

Use Augure with Cursor

Use Augure's Canadian, OpenAI-compatible API in Cursor by overriding the OpenAI base URL and adding Augure model names.

Updated 2026-10-26 · Configuration shown as documented by the tool; not yet verified end to end by Augure. · Markdown version

You get Augure models in Cursor's chat and inline edit through Cursor's custom OpenAI key and base URL override, with inference on Canadian infrastructure.

Prerequisites

Configure

Cursor has no config file for this; the settings are in the app.

  1. Open Cursor Settings (Cmd+Shift+J on macOS, Ctrl+Shift+J on Windows and Linux) and go to Models.
  2. In the OpenAI section, paste your Augure key into OpenAI API Key.
  3. Turn on Override OpenAI Base URL and enter:
https://api.augureai.ca/v1
  1. Click Verify. Cursor sends a test request through the key; Augure accepts OpenAI model names as aliases, so the check passes even before you add Augure models.
  2. Under the model list, choose Add model and enter an Augure model id exactly, for example ossington-5. Add rosedale-1 and tofino-3 the same way, and enable them.
  3. In the chat or Cmd+K model picker, select the Augure model.

Menu labels change between Cursor releases; the three things that matter are the key, the base URL above, and model names that match Augure ids.

Pick a model

Model When to use
ossington-5 Flagship reasoning. 256K context, 32,768 max output. Default for coding chat and edits.
rosedale-1 Premium reasoning, up to 1M context on paid plans, Canadian inference. Large codebases, long sessions.
tofino-3 Fast everyday model, 256K context, 16,384 max output, no thinking. Quick questions and small edits.

auto can also be added as a model name and lets the gateway pick. Cursor does not expose reasoning_effort, so ossington-5 thinks at its default effort; when you want the fastest answers, select tofino-3. Full list: /docs/models.

Verify it works

Open chat, select the Augure model and ask: "Which model are you, in one sentence?" A reply means the base URL and key are working. For the residency check, call the API once from a terminal:

curl -s https://api.augureai.ca/v1/chat/completions \
  -H "Authorization: Bearer $AUGURE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"model":"tofino-3","max_tokens":64,"messages":[{"role":"user","content":"Reply with the single word OK."}]}'

The JSON ends with an _augure block, for example "_augure": {"gateway_region": "ca-montreal-1", "inference_region": "ca-on-toronto", "request_id": "..."}. inference_region tells you where the model ran. Inference is on Canadian infrastructure first, with disclosed failover to vetted EU partners under zero data retention, never the US.

Notes

  • A custom key and base URL cover chat and inline edit. Tab autocomplete and some agent features use Cursor's own models and ignore this setting.
  • Cursor's documentation states that requests made with custom keys are still routed through Cursor's servers before reaching the base URL. Augure controls where inference runs, not the path through Cursor. If that matters for your residency requirements, use Continue or Augure Code, which call the API directly.
  • Aliases: if Cursor sends gpt-4o it is served by ossington-4, and gpt-4o-mini by tofino-3. Add Augure ids explicitly to control which model you get.
  • Cursor streams responses; Augure supports stream: true with usage in the final chunk.

See also