Before calling the API
You can call CorvusLLM with plain HTTP, so curl is enough for the first check. Install Python or Node.js only if you want to use an SDK instead of raw requests.
| What to install | Official source | Quick check |
|---|---|---|
| CorvusLLM key | Buy or top up balance | Send as a Bearer token. |
| curl | Built into most terminals. | curl --version |
| Optional SDK runtimes | Python downloads or Node.js download | Use only for application code. |
curl --version
python --version
node --version Zero-to-working setup
Use this block when you want the shortest reliable path from a clean install to one successful HTTP / curl / fetch request through CorvusLLM.
Use a terminal, script, backend service, or fetch-capable runtime that can send HTTPS requests.
- Use Authorization: Bearer YOUR_CORVUSLLM_KEY
- Send JSON to https://base.corvusllm.com/v1/chat/completions
- Run one small curl request with model gpt-5.5
- Confirm the response and dashboard balance movement before larger tests
A JSON response returns message content and your dashboard balance moves by a small amount.
| Value | Paste this |
|---|---|
| Base URL | https://base.corvusllm.com/v1 |
| Endpoint | https://base.corvusllm.com/v1/chat/completions |
| Auth header | Authorization: Bearer YOUR_CORVUSLLM_KEY |
| Starter model | gpt-5.5 |
Use this path first when debugging. Do not paste /anthropic into OpenAI-compatible HTTP clients.
Authentication
Use your delivered CorvusLLM key as a Bearer token or the equivalent auth field in the environment you are configuring.
Primary endpoints
| Path | What it is for |
|---|---|
/v1/models
|
List the public customer-facing model lineup. |
/v1/chat/completions
|
The main OpenAI-compatible chat path. |
/v1/responses
|
Responses API style integration. Keep the first implementation non-stream. |
/anthropic/v1/messages
|
Anthropic-native path used by Claude Code and similar tools. |
First test request
curl https://base.corvusllm.com/v1/models ^
-H "Authorization: Bearer YOUR_CORVUSLLM_KEY"
Short answer
Use CorvusLLM like an OpenAI-compatible API when your tool expects a /v1 endpoint. Use the Anthropic-native endpoint only for Claude Code style tools that expect Anthropic message semantics. Do not mix the two paths inside one client configuration.
CorvusLLM is an independent AI API proxy. It is not affiliated with OpenAI, Anthropic, Google, or Z.AI. Treat the key as a CorvusLLM key, not as a direct provider account key.
Request shape
The OpenAI-compatible path is the safest first integration path for SDKs, backend apps, scripts, n8n, Open WebUI, ChatBox, and any client that lets you override the base URL. Your app sends the CorvusLLM key in the same place it would normally send an OpenAI API key.
| Client type | Base URL | Auth field | Model value |
|---|---|---|---|
| OpenAI SDKs | https://base.corvusllm.com/v1 | apiKey | Public CorvusLLM slug |
| Raw HTTP | https://base.corvusllm.com/v1 | Authorization: Bearer | Public CorvusLLM slug |
| Claude Code | https://base.corvusllm.com/anthropic | ANTHROPIC_AUTH_TOKEN | Claude public slug |
Common mistakes
- Do not append
/v1twice. If the SDK asks for a base URL, pastehttps://base.corvusllm.com/v1exactly. - Do not use
/anthropicfor OpenAI SDKs. That path is for Anthropic-native clients. - Do not invent model names. Copy the public customer slug from Models & Slugs.
- Do not debug inside a complex app first. Run the model-listing curl command before changing app code.
Balance rule
If the key has no balance left, the API stops with 429 out of balance. It does not silently continue spending. Check the personal dashboard after a small test request if you need to confirm that usage is being deducted from the expected key.
Related next steps
Move from delivered key to first working request with the shortest setup path.
After you buyConfirm key delivery, dashboard balance, first request behavior, and top-up flow.
OpenAI SDK setupConfigure Node.js, Python, or other OpenAI-compatible clients.
Claude Code setupUse the Anthropic-native path for Claude Code style clients.
Model slugsCopy the exact customer-facing slug before testing a request.
Billing and cacheUnderstand prepaid balance, cache reads, cache writes, and 429 behavior.
Troubleshooting errorsDiagnose auth, base URL, model slug, balance, image, tool, and streaming issues.
OpenAI-compatible API pageBuyer-facing service overview, pricing entry points, and independent-service disclosures.
Pricing trackerCompare current public CorvusLLM model rates with source-linked official rates.
Trust CenterReview data handling, no-SLA boundary, support expectations, and provider affiliation notes.