xpu liveBETA
Models›R1

R1

Model reference ↗

Model ranking

Not matched to the current verified ranking snapshot.

Pricing 2 Model information

Provider prices 2

Lowest input price per billing unit. Conditions in Details.

ProviderPriceProvider model IDStatusContext / max outputSource
Microsoft Azure AI FoundryNot collectedAwaiting verified pricingDeepSeek-R1Catalog-listed
Conditions

Catalog-listed; account access and regional availability may apply.

Not suppliedOfficial source ↗2026-09-28
OpenRouterNot collectedAwaiting verified pricingdeepseek/deepseek-r1Catalog-listed
Conditions

Catalog-listed; account access and regional availability may apply.

Context tokens 64000Output tokens 16000Official source ↗2026-09-28

R1 is listed in the xpu live Text & chat catalog under Deepseek. Compare its API pricing, provider availability and recorded specifications on this page. R1 accepts text and produces text. Tool calling and structured outputs are available on supported routes.

R1 specifications and capabilities

R1 has the following source-scoped details in the catalog: recorded input modalities: text; recorded output modalities: text; reference context limit: 131,072 tokens; reference maximum output: 16,000 tokens. Provider endpoints can expose different limits. Check the source attached to each field and the deployment details beside each offer before treating a limit as universal.

Catalog capabilities include Reasoning, Structured output, Tool calling. Confirm how those features are exposed by your selected endpoint; a capability label does not guarantee that every provider accepts the same request parameters.

API parameter names are reported by OpenRouter and do not describe the developer’s native API. Token limits labeled OpenRouter are route catalog limits, not universal model limits. Media limits on this page describe the linked provider endpoint; other deployments may differ. The original DeepSeek-R1 model card specifies 128K context. OpenRouter currently advertises 64,000 context and 16,000 maximum output for this route. Evaluation generation lengths are not treated as API limits.

Using R1 for your workload

For R1, estimate input and output tokens separately. Conversation history, retrieved documents and tool responses can increase input volume. Longer generated answers increase output cost. The cheapest input tariff may not be the cheapest option for an output-heavy workload.

Test the endpoint with your actual prompts, expected context length and concurrency. Compare answer quality, latency and supported API features. Batch processing, caching and reasoning settings can change the effective rate or response behavior, so match those settings when comparing offers.

The catalog marks R1 as an open-weight model. Check the recorded license and checkpoint format before self-hosting. Open weights do not by themselves define commercial permissions, runtime memory requirements or the cost of hosting.

R1 API pricing across providers

The pricing table links each R1 offer to its provider, model identifier and source. Compare the billing unit, tariff settings and last observation time. A missing price means no verified rate is recorded for that offer; it does not mean free access.

Review availability, regional restrictions and any batch or commitment conditions. Provider model IDs are important when selecting a route. Confirm the intended version before sending production requests, particularly when an offer is marked preview, legacy or unavailable.

Sources and alternatives

R1 specifications are recorded separately from provider-specific deployment limits. Open the model reference for the source details. Consult the linked sources when planning an integration and leave unknown fields as unknown rather than assuming a default.

Use the AI model rankings and pricing directory to compare other models, or browse AI API providers. For R1, choose the endpoint that fits your task, expected usage and required features rather than relying on one headline rate.

CONTEXT TOKENS131,072Developer model card
MAX OUTPUT TOKENS16,000OpenRouter catalog
PROVIDERS2Linked in this catalog
SOURCE CHECKED2026-09-29Sources reviewed; unknown fields labeled

Specifications

Catalog model ID
deepseek/deepseek-r1
Developer model ID / revision
DeepSeek-R1 (original checkpoint)Developer model card ↗
Input modalities
textOpenRouter catalog ↗
Output modalities
textOpenRouter catalog ↗
Context / input token limit
131,072Developer model card ↗
Maximum output tokens
16,000OpenRouter catalog ↗
Tool calling
SupportedOpenRouter catalog ↗
Structured output
SupportedOpenRouter catalog ↗
API parameters (source-specific)
frequency_penalty, include_reasoning, max_tokens, presence_penalty, reasoning, repetition_penalty, response_format, seed, stop, temperature, tool_choice, tools, top_k, top_pOpenRouter catalog ↗
API parameter scope
OpenRouter API; support varies by route
Weight access
Open weightsDeveloper model card ↗
Weight license / access terms
MITDeveloper model card ↗
Total parameters (billions)
671Developer model card ↗
Active parameters (billions)
37Developer model card ↗
Download size (GB)
Depends on checkpoint and precision; no verified file size
Release date
Not verified in cited sources
Added to OpenRouter
2025-01-20OpenRouter catalog ↗
Notes
API parameter names are reported by OpenRouter and do not describe the developer’s native API. Token limits labeled OpenRouter are route catalog limits, not universal model limits. Media limits on this page describe the linked provider endpoint; other deployments may differ. The original DeepSeek-R1 model card specifies 128K context. OpenRouter currently advertises 64,000 context and 16,000 maximum output for this route. Evaluation generation lengths are not treated as API limits.

Catalog entries link to their specification and availability sources. This is a curated selection, not every model each provider offers. Best prices are the lowest collected USD tariffs, not a total-cost estimate. Token offers are selected by input price, with output from the same tariff; workload mix may change the cheapest provider. Listed variants may require batch processing, off-peak hours, or specific media settings. Price coverage varies by provider; collected tariffs include their source and observation time. Arena user-preference scores are checked automatically every six hours against the latest published Text / overall dataset. Source: Arena / LMArena; CC BY 4.0. Selection and catalog matching by XPU LIVE. They apply to the shown evaluation configuration; listed prices may use different settings. Models without verified scores are not assumed to be weaker.