API key
Your CorvusLLM key authenticates requests and connects usage to prepaid balance.
One prepaid key for supported coding models — use Claude, GPT, Gemini, and DeepSeek rows in Cursor through a custom OpenAI-compatible base URL.
Independent AI API proxy. Not affiliated with OpenAI, Anthropic, Google, or Z.AI. Prepaid balance. Card, wallet, or crypto checkout. No financially backed SLA. Do not send sensitive or regulated data through shared API proxies.
CorvusLLM gives you an OpenAI-compatible endpoint that you enter in Cursor's custom provider settings. Supported Claude, GPT, Gemini, and DeepSeek rows share one prepaid access model; verify exact slugs and current rates in the live catalog before use.
The Cursor path is intentionally simple: provide the endpoint, the key, and a supported model slug. The full guide covers where those fields sit in the UI.
Your CorvusLLM key authenticates requests and connects usage to prepaid balance.
The base URL lets Cursor send OpenAI-compatible requests through CorvusLLM instead of a direct provider account.
Pick a supported coding model from the current catalog and test one small prompt before larger repo work.
Base URL: https://base.corvusllm.com/v1
API Key: YOUR_CORVUSLLM_KEY
Model: choose a supported Cursor-friendly model slug
Cursor users usually care about coding quality, model availability, and cost control. CorvusLLM keeps those decisions visible instead of hiding behind a vague package.
Start small, test your Cursor workflow, then top up if the model mix and latency fit your use case.
A CorvusLLM key, proxy base URL, and access to supported model families shown by the live catalog.
Usage is deducted from prepaid balance. The pricing tracker explains comparison logic and official-rate references.
If confirmed payment does not unlock access after a short processing delay, support can trace the order with proof.
Do not send sensitive or regulated data through shared API proxies. Cursor can expose repository context in prompts, so review your workspace and secrets before using any third-party API route.
Confirm model behavior, latency, and billing fit before using a third-party proxy for larger repositories or team workflows.
Compare the setup path, model catalog, pricing proof, and trust pages before you choose an endpoint.