Compatible (BYOK)Use Cursor with GlideflowAI.
An AI-first editor when its version exposes a custom endpoint. Connect it through GlideflowAI's OpenAI-compatible API with a key you control.
What this connection is for
Cursor is an editor-centered AI development environment with chat, code-generation, and repository-aware assistance close to the file tree. Its strength is the quick loop between reading code, making a local change, and asking a follow-up question without leaving the editing context. It suits individual developers who prefer an integrated editor over a terminal-only agent workflow.
Custom-provider capabilities in Cursor can vary by version, plan, and the controls exposed in a particular installation. That variability matters: a provider name or model selector is not by itself proof that an arbitrary OpenAI-compatible base URL can be changed. Before relying on a gateway connection, first find an explicit custom-base-URL control in your current Cursor build.
For that reason this page is marked Compatible, not Verified. If your version offers a standard OpenAI-compatible endpoint field, GlideflowAI's /v1 URL and an API key are the values to test. If it does not, do not try to alter undocumented files or bypass product controls. Cursor and GlideflowAI have no represented commercial relationship.
Why pair it with GlideflowAI
Where Cursor exposes the necessary BYOK controls, the same GlideflowAI key can be reused with your other compatible tools.
The model catalog and transparent USD prices give you a source of truth outside an editor's changing provider UI.
Setup
Use a new API key for the tool, select a model from the catalog, and begin with a small task. Do not put a key in a repository, screenshot, or shared configuration file.
Confirm your Cursor build exposes custom endpoint controls
Open Cursor settings and look for an OpenAI-compatible, custom provider, or custom base URL setting. The exact menu location can change, so this page deliberately does not claim one.
Enter standard compatible values if supported
Only in the exposed provider fields, enter the GlideflowAI URL, your key, and an exact model ID.
Base URL : https://api.glideflowai.com/v1 API key : sk-your-key Model ID : glm-5.2Test a small edit
Ask for an explanation or a one-file non-destructive edit. If the field is missing or the editor rejects custom models, keep Cursor on its supported providers and use one of the verified integrations instead.
Before you begin: Manual check: verify the custom base URL field in the specific Cursor version and plan you use.
Need the endpoint basics? Read authentication, browse the model catalog, or compare pricing. For tool-specific troubleshooting, see the existing guide.
Frequently asked questions
Why is Cursor only Compatible?
Its custom-provider controls vary. GlideflowAI has not represented every current Cursor version and plan as tested.
Can I force the setting through a config file?
No. This guide does not recommend undocumented configuration changes or reverse engineering.
What should I do if the endpoint is accepted but requests fail?
Verify the key and model with the docs endpoint test, then recheck Cursor's current compatible-provider requirements.
Ready to connect Cursor?
Create a key, use the setup above, and verify the connection on a small task before you scale it up.
