Set Up ASI:One in Cursor
Set Up ASI:One in Cursor
Overview
Use your ASI:One models with Cursor with your existing ASI:One subscription.
Prerequisites
- Cursor installed.
- An ASI:One API key. Create one at asi1.ai/developer.
Keys start with
sk_. - An ASI:One plan that includes
asi1-ultra. The same key also works forasi1,asi1-ultra-1mandasi1-mini.
Point Cursor at ASI:One
- Open Cursor Settings → Models.
- In API Keys, paste your ASI:One key into the OpenAI API key field.
- Turn on Override OpenAI Base URL and enter:
Add the models
Cursor doesn’t discover ASI:One models on its own, so add them by name.
- Still in Models, click Add Custom Model.
- Enter
asi1-ultra. - Repeat for
asi1,asi1-ultra-1mandasi1-miniif you want them in the picker too. - Make sure each one is turned on.
Choose the model
Open a chat, pick asi1-ultra in the model picker, and send a message. Use
asi1-ultra for deep refactors, debugging and reviews, and switch to asi1 or
asi1-mini for routine edits where speed matters more. See ASI:One
Models for the tradeoffs.
Things to know
The base URL override applies to every OpenAI model in Cursor, not just the
ASI:One ones. While it is on, picking a GPT model sends that name to ASI:One,
which answers 404. Turn those models off, or turn the override off when you
want them back.
- Tab completion is not affected. Tab and some built-in features run on Cursor’s own models and can’t be billed to your key, so they keep working as before and don’t use ASI:One.
- Context windows. Cursor manages how much context it sends. The limits for each model are on the Models page.
Troubleshooting
Next steps
- Codex: the same models in the Codex CLI
- OpenCode: the same models in OpenCode
- ASI:One Models: choosing between
asi1,asi1-ultra,asi1-ultra-1mandasi1-mini - OpenAI Compatibility: which parameters each endpoint supports