Coding tools
Cursor
Cursor's officially documented BYOK flow covers a fixed list of named providers, not arbitrary custom endpoints. A gateway like xKiro sits outside what that flow was built for — here is exactly what is and is not documented.
Wire format
OpenAI format
Base URL
https://api.xkiro.com/v1
Configured by
Cursor Settings → Models
A custom base URL to xKiro is not officially documented
Cursor's current docs describe adding your own key for a fixed set of named providers — they do not describe pointing Cursor at a third-party base URL at all. Older pages used to document an "Override OpenAI Base URL" option; that option is no longer mentioned anywhere in the current docs, and the old deep links that used to cover it now redirect to the docs root instead of a specific page.
What Cursor officially documents#
Per Cursor's docs: open Cursor Settings > Models, paste the key, click Save. The officially supported key providers are:
- OpenAI
- Anthropic
- Azure OpenAI
- AWS Bedrock
xKiro is not one of these — this flow is for handing Cursor a key that talks directly to one of those five, not for pointing it at a gateway that happens to speak an OpenAI-compatible format.
The undocumented base-URL toggle#
Community reports — not official documentation — say a base URL override still exists under Settings → Models in the current app. We could not find it described on any current, non-redirecting Cursor docs page, so treat anything below as unverified:
- Some users report it breaks Cursor-provided models once set.
- Composer 2.5 has reportedly errored with "This model does not support custom API keys."
- Some users report no Verify button appears to confirm the endpoint is reachable.
If you try it, do not assume it behaves like the rest of your Cursor setup — a request that works today is not a guarantee the next Cursor release keeps supporting it.
Third-party requests carry a Cursor surcharge either way
Cursor's pricing docs state: "Third-party model requests include a Cursor Token Rate of $0.25 per million tokens. This rate applies on top of model API pricing for included usage, on-demand usage, and BYOK usage." That charge is separate from — and in addition to — whatever xKiro itself charges for the tokens. It applies to the officially supported BYOK path too, not just a custom endpoint.
Tab never uses this#
Regardless of which key or endpoint you configure, Cursor's own docs are explicit: "Tab completion continues using Cursor's built-in models." There is no path — documented or otherwise — that routes Tab through xKiro.
A fully supported alternative#
Cursor is a VS Code fork, so ordinary VS Code extensions run inside it. Installing Clineinside Cursor gives you a documented, stable path to xKiro — the OpenAI Compatible provider in Cline's own settings panel, no undocumented toggles involved.
If it does not work#
Send one request by hand before touching Cursor's settings again. A reply proves the URL and key are both fine, which means whatever is left is in the tool's own configuration — and that is a much smaller place to look.
curl https://api.xkiro.com/v1/chat/completions \
-H "Authorization: Bearer $XKIRO_API_KEY" \
-H "Content-Type: application/json" \
-d '{"model":"openai/gpt-5.6-sol","messages":[{"role":"user","content":"ping"}],"max_tokens":8}'An error naming an unknown model still counts as a success here: the request was authenticated before the model was rejected. Common failures and what each one means are on the overview page.