Models & pricing.
Everything below runs on the shared pool: call it with any API key, pay for the tokens you use, and never start or stop a GPU. The table is generated from the gateway's own catalog and rate card, so it is what the fleet actually serves and bills.
Shared models
Pass the model id in the request body — that is the string the gateway routes on, and the one your usage is recorded against.
| Model | Model id | Context | Input / 1M | Output / 1M |
|---|---|---|---|---|
| DeepSeek V4 FlashMoE · 167 GB fp4 | deepseek-v4-flash | 160K | $0.30 | $1.20 |
| DeepSeek V4 ProMoE · 865 GB fp4 | deepseek-v4-pro | 800K | $1.74 | $3.48 |
| Qwen3 0.6Bfine-tunable0.6B | qwen3-0.6b | 32K | $0.10 | $0.20 |
| Qwen3 4B Instructfine-tunable4B | qwen3-4b-instruct | 32K | $0.20 | $0.60 |
| Qwen3.6 27Bfine-tunable27B | qwen3-6-27b | 256K | $0.30 | $0.90 |
| Qwen3.8 27Bfine-tunable27B | qwen3-8-27b | 256K | $0.30 | $0.90 |
| GLM-5.2fine-tunableMoE · 1.51 TB bf16 | glm-5-2 | 128K | $0.50 | $2.00 |
| Kimi K3MoE · 1.56 TB mxfp4 | kimi-k3 | 1M | $0.60 | $2.50 |
| Kimi K3 TurboMoE · 1.56 TB mxfp4 | kimi-k3-turbo | 128K | $0.60 | $2.50 |
Prices are US dollars per million tokens. A request is rated on the usage block the gateway returns with it, summed over the billing period and rounded once at the invoice line — so a handful of small calls costs a fraction of a cent, not a rounded-up cent each.
What each one is for
deepseek-v4-flashDeepSeekDeepSeek V4 Flash (0731 instruct) on the shared pool: a 160K-token window with tool calling and prefix caching, billed per token.
deepseek-v4-proDeepSeekDeepSeek V4 Pro on the shared H200 pool: an 800K-token window with tool calling and prefix caching reported as cached_tokens, billed per token. The larger of the two DeepSeeks the fleet serves; deepseek-v4-flash is the cheaper, shorter-context one.
qwen3-0.6bQwenQwen3 0.6B on the shared pool: a small, fast base model billed per token, and the cheapest one to fine-tune — train a LoRA adapter on it from the training tab and call the result per token with no endpoint of its own.
qwen3-4b-instructQwenQwen3 4B Instruct (2507) on the shared pool: the fine-tunable base — call it per token, or train it on your own dataset from the training tab.
qwen3-6-27bQwenQwen3.6 27B on the shared MI325X pool: a 256K-token window on a single GPU, with tool calling and separate reasoning, billed per token. The largest base the fleet can fine-tune on one card — train a LoRA adapter from the training tab and call the result per token with no endpoint of its own.
qwen3-8-27bQwenQwen3.8 27B on the shared MI325X pool: a 256K-token window on a single GPU, with tool calling and separate reasoning, billed per token. Fine-tunable on that one card — train a LoRA adapter from the training tab and call the result per token with no endpoint of its own.
glm-5-2GLMGLM-5.2 on the shared MI325X pool: the largest model the fleet serves, with a 128K-token window, billed per token. Not fine-tunable as an adapter — vLLM's fused MoE LoRA path cannot leave a KV cache on this base, so a tuned GLM-5.2 is registered as its own merged model instead.
kimi-k3KimiKimi K3 on the shared MI325X pool: a genuine 1M-token context with separate reasoning output and tool calling, billed per token. Accepts images as OpenAI image_url parts, up to 16,384 tokens each. Accepts reasoning_effort of low, high or max — not medium.
kimi-k3-turboKimiKimi K3 with prefix caching: a repeated prompt prefix is served ~41x faster and reported as cached_tokens, which is what an agent loop resends every turn. Trade-off: recall degrades on very long context — measured 100% at ~98K tokens but 67% at 1M, and the failure is a confident wrong answer rather than an error, so this is capped at 128K. Use kimi-k3 for long-context work where accuracy matters.
Listing them from the API
The catalog is also available at runtime, which is the honest source if you are building a model picker — it includes any dedicated endpoints your workspace is running.
curl https://inference.legionedge.ai/v1/models \
-H "Authorization: Bearer $LEGIONEDGE_API_KEY"Dedicated GPU pricing
A dedicated endpoint rents whole GPUs instead of billing per token: you pay for the time it's up, whatever traffic it serves. Rates are per GPU, per hour.
| Hardware | Per GPU-hour |
|---|---|
MI325X-256GB | $4.79 |
H200-141GB | $4.79 |
An endpoint's hourly cost is this rate times the GPUs it needs — an eight-GPU model on MI325X bills eight times the row above for as long as it runs.