Cursor with ShareQuota

Cursor takes an OpenAI key and a base URL override. The catch, stated first: Cursor’s servers make the request, so the endpoint has to be reachable from the internet.

Cursor lets you supply your own OpenAI API key and override the base URL under Settings › Models. The proxy speaks the OpenAI dialect, so the override works — but the request is made from Cursor’s own backend, not from your laptop, and localhost means nothing there. Publish the endpoint through the built-in tunnel, paste the https address with /v1 on the end, and add the routed model ids you want to use.

This tool calls from its own serversRequests do not come from your machine, so localhost is not reachable from where they start. Publish the endpoint first with the built-in tunnel — a Cloudflare quick tunnel or a Tailscale Funnel — and paste that https address instead of the local one. Put your own authentication in front of anything you expose.

Setup

1Start the proxy and publish itRun the binary, connect a plan, and turn on the tunnel so the endpoint has a public https address.
2Set the key and the base URLIn Cursor Settings › Models, paste your sq- key as the OpenAI API key and the tunnel address plus /v1 as the base URL override.
3Add a model idAdd claude/claude-sonnet-5 or any routed id as a custom model name, then verify the key.

What to set

OpenAI API Key          sq-your-internal-keyOverride OpenAI Base URL  https://<your-tunnel-host>/v1Model name              claude/claude-sonnet-5

Worth knowing

A tunnel exposes the endpoint to the internet. The sq- key is the only thing between it and anyone who finds the address; keep it secret and rotate it from the dashboard if in doubt.
Cursor features that depend on its own models — Tab completion, some agent modes — do not go through a custom base URL. Chat and Composer with the model you added do.

To undo it

Remove the entries above, or turn the integration off in the dashboard and the backup is restored. Nothing else was written.

Questions

Because Cursor’s backend makes the model request, not the editor on your machine. Any custom base URL has to be reachable from Cursor’s servers, which is what the tunnel is for.

The base URL override needs a Cursor plan that allows custom keys; check Cursor’s current terms. The model quota then comes from your own plan through the proxy, not from Cursor’s pool.

Checked against the tool’s own documentation on 2026-09-13. Settings move; if a field has been renamed, the docs link above is the source.

Download Integrations