Cursor API Base URL Checks - Custom Keys and OpenAI-Compatible Relays

Quick answer

Use official provider keys as the safety baseline. Treat an API relay as a test candidate only when it documents Cursor API base URL behavior, model IDs, pricing, privacy policy and streaming behavior clearly.

Cursor custom API keys are configured from Cursor Settings > Models.
Cursor's visible providers and key options can change by app version. A search result that lists OpenAI, Anthropic, Google, Azure or AWS Bedrock does not prove that every key, cloud credential or endpoint is accepted.
Searches that mention `api.cursor.com` or `crsr_` should be treated as Cursor-owned account or API signals unless the provider docs say otherwise.
A provider's custom base URL docs should explain whether Cursor should use a root URL, `/v1`, or another OpenAI-compatible path.
Do not paste a full `/v1/chat/completions` or `/v1/responses` endpoint into a Base URL field.
Custom API keys apply to standard chat models; specialized Cursor models may still use Cursor's own models.
Relays need extra checks for model substitution, logging, token billing and refund rules.

Verify before testing a Cursor relay

Official docs or provider pages mention Cursor, OpenAI-compatible APIs or supported model families.
Base URL, API key format, model names, streaming behavior, `/v1` path style and error format are documented.
The provider explains whether it supports chat-completions-style calls, Responses-style calls or both.
Pricing is public enough to compare input/output token costs and failed-request billing.
Privacy, log retention, terms and support channels are visible before sending repository context.
The provider page has a clear update path so missing fields can be corrected by the provider.

Cursor-compatible provider shortlist

This shortlist is based on visible Cursor or OpenAI-compatible signals in the current public-source checks. It is a starting point for verification, not a final recommendation.

Entry	Provider	Type	Fit	Tool compatibility	Public links	Notes	Source / action
Check 1	OpenRouter openrouter.ai	Global aggregator	Benchmarking model availability, pricing, and a global API gateway baseline.	Codex CLI Cursor Cline	Official Docs Pricing 7/8 sources	Run low-balance test first	Details Website
Check 2	SiliconFlow siliconflow.com	China model platform	Low-cost DeepSeek, Qwen, embedding, image, and open model workloads.	Codex CLI Cursor Cline	Official Docs Pricing 7/8 sources	Run low-balance test first	Details Website
Check 3	302.AI 302.ai	Global aggregator	Users who want both AI tools and API access under one account, while still checking official docs, pricing and privacy links before production use.	Codex CLI Cursor Cline	Official Docs Pricing 7/8 sources	Run low-balance test first	Details Website
Check 4	DMXAPI dmxapi.com.cn	Enterprise gateway	Companies that need private deployment, auditability, and a managed API control layer.	Codex CLI Cursor Cline	Official Docs need checking Pricing needs checking 2/8 sources	Docs need checkingPricing needs checking	Details Website
Check 5	MoleAPI moleapi.com	Claude Code friendly	Developers who want one endpoint for Claude Code, Cursor, Codex CLI, and common OpenAI SDK workflows.	Claude Code Codex CLI Cursor Cline	Official Docs Pricing 6/8 sources	Run low-balance test first	Details Website
Check 6	API易 apiyi.com	Claude Code friendly	Teams that care about documentation, invoices, and visible model/pricing references.	Claude Code Codex CLI Cursor Cline	Official Docs Pricing 5/8 sources	Run low-balance test first	Details Website
Check 7	灵芽 API api.lingyaai.cn	Claude Code friendly	Users who primarily need copyable setup steps for AI coding terminals and editors.	Claude Code Codex CLI Cursor Cline	Official Docs Pricing 6/8 sources	Run low-balance test first	Details Website
Check 8	柏拉图 AI api.bltcy.ai	Claude Code friendly	Users comparing Chinese relay services with coding-tool setup support.	Claude Code Codex CLI Cursor Cline	Official Docs Pricing needs checking 5/8 sources	Pricing needs checking	Details Website

Official and public sources

These sources anchor the page. Provider-specific claims should still be checked from each provider's current docs and pricing pages.

Cursor docs Cursor models and pricing Public source checker OpenAI-compatible Base URL guide GPT/Codex candidate checks Relay risk guide

Cursor's current documentation entry point. Confirm exact API key and model settings in the installed Cursor app before testing a relay.
Cursor's current official model and provider catalog. A listed model does not by itself prove support for a direct provider key or third-party Base URL.
Generate a docs, pricing, models, privacy, terms, status and support checklist for any provider homepage.
A focused checklist for root URLs, `/v1`, model IDs, endpoints, streaming and pricing evidence.
OpenAI-compatible candidates that may also be useful for Cursor-style workflows.
Privacy, billing and model-substitution risks to check before testing relays.

Provider update and sponsored inquiries

If a Cursor-compatible provider has missing docs, pricing, model coverage, privacy or support fields, use the update path to send public sources. Sponsored placements must be labeled and do not remove risk notes.

Update an entry Risk guide

FAQ

Can Cursor use a custom API key?

Yes. Cursor has model and provider settings for custom keys, but the exact labels can change between Cursor versions. Confirm the current setting in Cursor Settings > Models before adding a relay key.

Which provider API keys can Cursor use?

Check the current Cursor Settings > Models screen and official docs. Search snippets often group OpenAI, Anthropic, Google, Azure and AWS Bedrock, but provider or model visibility does not prove that every direct key, cloud credential or custom Base URL is accepted by the installed Cursor version.

Is api.cursor.com the same as a relay Base URL?

No. Treat api.cursor.com and crsr_ style terms as Cursor-owned account or API signals, not as a third-party relay endpoint. A relay should provide its own OpenAI-compatible base URL, model IDs and API key format.

Can every OpenAI-compatible relay work with Cursor?

No. OpenAI-compatible support is only a starting signal. Verify base URL behavior, model names, streaming, pricing, privacy and whether Cursor's exact workflow accepts that provider.

Should I use a relay for sensitive Cursor projects?

Prefer official APIs, cloud-provider routes or self-hosted gateways for sensitive repositories. Test relays only with non-sensitive code and a small balance first.

Cursor API Base URL and Custom Key Checks