Before choosing a model
No local install is required to read model slugs. To verify a slug, use curl or an OpenAI-compatible SDK against the live models endpoint.
| What to install | Official source | Quick check |
|---|---|---|
| CorvusLLM key | Buy or top up balance | Needed for model requests. |
| curl | Built into most terminals. | curl --version |
| Optional SDK runtimes | Python downloads or Node.js download | Useful after you pick a slug. |
curl --version Short answer
Use the public CorvusLLM model slug exactly as listed in the canonical table. The public slug is the value customers paste into SDKs, apps, and Claude-compatible tools. Internal upstream model names and provider-side aliases are implementation details.
A model may have routing rules, provider fallbacks, or internal aliases behind the scenes. Customer docs intentionally expose one recommended slug so tools do not drift across different naming styles.
How to choose a model
| Use case | Recommended choice | Why |
|---|---|---|
| Claude Code or Anthropic-native clients | Claude public slug | The Anthropic-native path keeps message semantics, tool calling, and Claude-style settings aligned. |
| OpenAI SDKs, Open WebUI, scripts, backend apps | OpenAI-compatible public slug | The /v1 endpoint is the broadest compatibility path. |
| Lowest-cost automation | Smaller or faster model family | Short prompts, extraction jobs, and simple classification usually do not need premium reasoning models. |
| Long reasoning or agentic coding | Premium reasoning-capable model | Hard coding tasks and multi-step analysis benefit from stronger reasoning even when the per-token price is higher. |
Slug check flow
- List models with the curl command below or copy a slug from the canonical table.
- Send one small non-streaming request before configuring a larger app.
- If the request fails, check the base URL, the auth header, and the exact model string before changing application code.
curl https://base.corvusllm.com/v1/models \
-H "Authorization: Bearer YOUR_CORVUSLLM_KEY"
Canonical model table
| Model | Customer slug | Provider | Best path | Best environments | CorvusLLM pricing |
|---|
Provider pricing snapshots
These tables use the live public catalog. Each provider block keeps the official prices, source link, verification state, and CorvusLLM customer price in one scan-friendly table.
Common model mistakes
- Using an official provider model ID when the tool is configured for the CorvusLLM public catalog. Use the customer slug shown here.
- Using an old slug from a copied chat or screenshot. Recheck the live docs when a model lineup changes.
- Switching the base URL but leaving a tool's default model selected. Both the base URL and model value must match the CorvusLLM setup.
- Testing a complex streaming or tool-calling workflow before a small plain chat request succeeds.
Related model resources
Browse the public model-family directory before choosing a slug.
Claude API modelsReview Claude-family rows, use cases, and setup links.
GPT API modelsReview GPT-family rows for OpenAI-compatible workflows.
Gemini API modelsReview Gemini rows, public slugs, and pricing references.
DeepSeek API modelsReview DeepSeek rows for cost-sensitive reasoning and automation workflows.
Cost calculatorEstimate request cost before using a new model in production.
Pricing trackerCheck source-linked official-rate comparison context.
Important note
They intentionally list the one slug we recommend customers copy into tools and code.