DeepseekDeepSeek R1deepTool use

R1

DeepSeek R1 is here: Performance on par with [OpenAI o1](/openai/o1), but open-sourced and with fully open reasoning tokens. It's 671B parameters in size, with 37B active in an inference pass. Fully open-source model & [technical report](https://api-docs.deepseek.com/news/news250120). MIT licensed: Distill & commercialize freely!

128K context·~96K words·8K max output
Context window128Ktokens
Max output8Ktokens

Context window

This model accepts 128K tokens in one request (~96K words of text).

Context window size128K tokens
4K32K128K1M10M

What fits in one request

  • Short document
    About 1,500 words of text
    Fits
  • Long document
    About 37K words of text
    Fits
  • Small codebase
    About 150K words of text
    Won't fit
  • Full novel
    About 375K words of text
    Won't fit

Specifications

Context size, pricing, and release info in one place.

Context window
128,000 tokens (128K)
Max output tokens
8,192 tokens (8K)
Speed tier
deep
Provider
Deepseek
Model family
DeepSeek R1
Release date
Jan 2025
Input cost
$1.35/M / 1M tokens
Output cost
$5.40/M / 1M tokens

Capabilities

See which features this model supports, such as vision, tools, and streaming.

Supported (4)
Tool use
Supported
Function calling
Supported
Extended thinking
Supported
Streaming
Supported
Not supported (4)
Vision
Not supported
Web search
Not supported
Batch API
Not supported
Prompt caching
Not supported

Best for

Jump to a guide or ranking that matches each workload.

Compare R1

Open a side-by-side comparison with one click.

Frequently asked questions

Short answers about context size and how this model behaves.

R1 has a context window of 128K tokens (128,000 tokens). This covers most professional use cases including large code files, lengthy reports, and long conversation histories.

More from Deepseek

Other models by Deepseek in our catalog.

Powered by Mem0

Use a smaller model.
Get better results.

Mem0 gives your AI long-term memory so you stop re-sending context on every call. That means you can use a smaller, faster, cheaper model — and still get better answers.

Example: a multi-turn chat session

Without Mem0~128K tokens sent
Full history
Repeated info
Old context
With Mem0~20K tokens sent
Key memories
Current turn

80% less to send — works with any model