Model slug troubleshooting

Fix model not found errors

A model-not-found error almost always means the client sent a provider-style name, a typo, an archived slug, or a slug from a different endpoint shape. Copy the current public customer slug from Models & Slugs, keep the first retry small, and only then put the slug back into your app configuration.

model not found unknown model no such model 404 model invalid model slug

Direct answer

A model-not-found error almost always means the client sent a provider-style name, a typo, an archived slug, or a slug from a different endpoint shape. Copy the current public customer slug from Models & Slugs, keep the first retry small, and only then put the slug back into your app configuration.

Use this page for public troubleshooting only.

Private order, key, and balance details belong in the customer portal or support. Public docs can explain the diagnostic path, not reveal account-specific state.

Error phrases this guide covers

Search tools, logs, and support tickets do not always use the same wording. Treat these phrases as the same troubleshooting family before changing unrelated settings.

model not found unknown model no such model 404 model invalid model slug

Fast check before changing everything

Run the smallest check that isolates the failing layer. If the small request works, the problem is usually the client configuration, hidden context, permissions, or advanced feature path rather than the whole account.

Small slug check
curl https://base.corvusllm.com/v1/chat/completions \
  -H "Authorization: Bearer YOUR_CORVUSLLM_KEY" \
  -H "Content-Type: application/json" \
  -d '{"model":"gpt-5.5","messages":[{"role":"user","content":"Say ok."}],"max_tokens":20}'

Common causes

  • The app is using an official-provider model name instead of a public CorvusLLM customer slug.
  • The configured model contains a small typo, hidden suffix, uppercase difference, or stale alias from an older setup.
  • The selected tool caches an older provider profile and is not reading the value you just changed.
  • The request is being sent to a client path that expects a different request shape than the model family you chose.

Fix steps

  1. Open Models & Slugs and copy the exact public slug from the current catalog row.
  2. Run one tiny direct request with that slug before changing a full application or agent setup.
  3. Update only one configured model field in the affected tool, then restart the tool if it caches provider profiles.
  4. If a family route is temporarily unavailable, test a nearby public slug from the same docs page before escalating.

Verify before retrying production traffic

  • Confirm the failed request body contains the exact public slug, not an official-provider name you copied from another service.
  • Confirm the base URL still points at the intended CorvusLLM endpoint, not a different provider profile.
  • Confirm the dashboard balance did not drop repeatedly while the client kept retrying the same bad slug.
Do not use expensive retry loops as a diagnostic tool.

Use one small request first. Large retries can spend balance, hide the original cause, and create confusing logs.

Diagnostic decision tree

Work through these checks in order. The goal is to isolate the failing layer before editing unrelated settings or sending another expensive request.

Check Action Pass result Fail result
Minimal request Run the smallest check from this page with the same key, endpoint shape, and one public model slug. The account and basic route probably work; move to client settings, hidden context, tools, or retries. Fix auth, base URL, balance, model slug, or current route health before testing advanced features.
Client final URL Inspect the actual URL or provider profile the client sends, not only the visible settings field. Continue with request body, model slug, payload size, and feature compatibility checks. Correct host/base/full-endpoint confusion before changing keys or model families.
Balance movement Compare dashboard balance before and after one tiny diagnostic request. If charged and no answer arrives, collect the support packet before retrying large prompts. If not charged, focus first on request rejection, wrong endpoint, auth, or client-side failure.
Feature isolation Disable streaming, tools, images, file context, long history, and automation loops for one retry. Re-enable one feature at a time until the failing layer is identified. Keep the request small and do not use production retries as the diagnostic method.
Route health Check Service Status and try a tiny prompt on one nearby public model row if your workflow allows it. Use a documented fallback only if quality and cost are acceptable. Wait, switch safely, or contact support with timestamps instead of hammering the failing route.

Prevent it next time

Keep model slugs in one environment variable or settings profile. Do not paste hidden upstream slugs into user-facing app configs, and recheck the public catalog before bulk tests or team rollout.

Minimum support packet

Collect these details before opening support. This avoids exposing secrets while giving enough context to match logs and reproduce the public failure path.

Field Why support needs it
Timestamp Use UTC or include timezone so logs can be matched accurately.
Endpoint path Include /v1, /anthropic, or the exact client route shape involved.
Public model slug Send the customer-facing slug, not a private key, upstream account name, or hidden route.
Exact error text Include the visible model not found message and any HTTP status shown by the client.
Minimal request result State whether the tiny check on this page works with the same key.
Balance movement State whether balance changed after the failed request or only after retries.
Client and feature flags Name the tool, SDK, streaming setting, image input, tools, file context, or automation loop involved.

When to contact support

Contact support when a minimal reproducible check still fails, when the dashboard history does not match what your client received, or when usage appears charged but no usable answer reached the client.

  • Include timestamp, endpoint path, public model slug, exact error wording, and whether the same key works on a minimal request.
  • Include whether the dashboard balance changed and whether the client retried in the background.
  • Do not send secrets, full API keys, regulated data, or private production prompts in public support messages.

Open the support bot after collecting the reproducible details.

Use these pages to verify the exact base URL, model slug, billing behavior, service status, or broader troubleshooting route before changing unrelated settings.

Models & Slugs →Use this supporting source to verify the next setup, billing, model, trust, or status step. /models →Use this supporting source to verify the next setup, billing, model, trust, or status step. Service Status →Use this supporting source to verify the next setup, billing, model, trust, or status step. Docs hub →Use this supporting source to verify the next setup, billing, model, trust, or status step. Troubleshooting hub →Use this supporting source to verify the next setup, billing, model, trust, or status step. API overview →Use this supporting source to verify the next setup, billing, model, trust, or status step. Billing, Balance & Cache →Use this supporting source to verify the next setup, billing, model, trust, or status step. Environment overview →Use this supporting source to verify the next setup, billing, model, trust, or status step. Trust Center →Use this supporting source to verify the next setup, billing, model, trust, or status step. Invalid API key →Diagnose CorvusLLM invalid API key, unauthorized, 401, and 403 errors with Bearer auth checks, dashboard key verification, and client-profile fixes. Wrong base URL →Diagnose CorvusLLM wrong base URL, double /v1, wrong endpoint path, Claude Code /anthropic, and OpenAI-compatible routing mistakes. Out of balance →Diagnose CorvusLLM out of balance, 429, insufficient credits, top-up, prepaid balance, and cache-heavy request billing errors.
Topic map

Continue with the right source

Open the exact setup, model, billing, and troubleshooting pages instead of guessing configuration values.

docs Use the canonical customer slug and keep it simple. Models & Slugs: Every customer-facing model with one customer slug, provider family, pricing. models AI Models The CorvusLLM model catalog directory helps users find current customer-facing model families, public slugs, pricing context. status Checking current status The status page shows customer-facing live checks for website, checkout, customer login, and API compatibility routes. docs Set up CorvusLLM without guessing. Overview: The clean start page: base URLs, model overview, environment overview, and where to begin. docs Most CorvusLLM issues are the same four mistakes. Troubleshooting: Clear fixes for wrong base URLs, bad model slugs, out-of-balance errors, delivery questions. docs API base URLs and request paths. API Overview: Base URLs, authentication, request formats, OpenAI-compatible vs Anthropic-native paths. docs bills against the customer key balance and stops at zero. Billing, Balance & Cache: How prepaid balance works, how same-key top-ups work, how usage deductions, out-of-balance behavior. docs Choose the path once, then stay consistent. Environment Overview: Every supported environment at a glance: which base URL to use, where to paste the key. trust Trust Center The Trust Center explains affiliation, data handling, support, refunds, compatibility evidence, pricing methodology. trust How to Verify CorvusLLM Before You Buy The verification checklist shows how to test CorvusLLM claims, endpoint setup, pricing data, status, legal pages. trust Proof of Operations Proof of Operations collects public evidence assets, published data, operational boundaries. faq Frequently Asked Questions CorvusLLM FAQ and help center with searchable answers about pricing, refunds, delivery, API setup, Cursor, Claude Code. docs Buy, paste, test, and verify your balance in minutes. Quickstart: The shortest safe path from purchase to a working request and a visible balance in the dashboard.
Browse docs
On this page