Skip to main content
This guide assumes you already have:
  • A virtual key with the sk-corvex- prefix. If you don’t, ask your team admin or see Authentication.
  • The Corvex API base URL — the examples below use https://api.tokenfactory.corvex.cloud.
Never paste a key into a public Gist, a screenshot, or a client-side bundle. Treat it like a password — it carries spend and rate-limit authority for the whole workspace.

Send a chat completion

Already on the OpenAI SDK? Swap 2 lines.

The base-URL/API-key swap shown on the drop-in page is copy-paste runnable against the Corvex public endpoint.
If your client library defaults to OpenAI’s hosted endpoint, set base_url (Python) / baseURL (TypeScript) — pointing it at your Corvex gateway is the only change needed.

What you’ll get back

A successful call returns HTTP 200 and a JSON body shaped like this:

Model naming

Corvex models use bare lab-canonical Hugging Face repo ids<hf-namespace>/<model-name> (e.g. zai-org/GLM-5.2-FP8, moonshotai/Kimi-K2.7-Code). There is no corvex/ prefix; legacy corvex/<…> ids return HTTP 404. Serving is handled server-side — you only send the model id, and the platform routes it for you. Get the current list of available models for your virtual key:

When something goes wrong

If the Authorization header is missing, malformed, or the key is unknown to the workspace, the gateway returns HTTP 401:
Most often this is one of:
  • The key is unset in the shell that ran curl.
  • The key was copied with whitespace or a trailing newline.
  • The key belongs to a different workspace than the model you’re calling.
For the full error taxonomy (429 rate-limit, 403 model-blocked, etc.) see the Errors reference.

What’s next

The OpenAI SDK drop-in examples on the drop-in page are copy-paste runnable. The broader samples on this page are illustrative.