Reka · Official-source model record
reka-flash-3.1
reka · Version reka-flash-3.1
Publisher-sourced inventory. Specifications come from official documentation and model cards. “Not documented” means we have no verified value. This inventory is separate from our editorial reviews.
Coverage & sources ↗Current catalog answers
What to know about reka-flash-3.1
AI-compiled from linked model documentation. This is a catalog reference, not an independent performance review. Catalog checked October 23, 2026.
Which reka-flash-3.1 does this page describe?
reka-flash-3.1 is a model record from Reka in the reka family. Source
The recorded model identifier or checkpoint is reka-flash-3.1. Use that exact identifier when checking documentation or a provider listing. Source
How can you access reka-flash-3.1?
The catalog documents Open weights access for reka-flash-3.1. Source
As of the catalog check, this version was listed without confirmed general availability. Source
Open weights means the model weights are distributed for use under their stated terms. It does not establish a hosted API, an open-source license, or a hardware requirement.
What can reka-flash-3.1 receive and generate?
Documented inputs: Text. Source
Documented outputs: Text. Source
Input support and output generation are separate capabilities. Reading an image does not establish image generation; a text output listing does not establish speech output. File sizes, formats and media limits depend on the documented implementation.
What license is recorded for reka-flash-3.1?
The recorded license label is apache-2.0. Source
Read the linked license and associated use terms for this exact version before redistribution, commercial deployment or fine-tuning. A label alone does not establish every permission, restriction or obligation, and it does not determine the terms of a separate hosted service.
What distinguishes reka-flash-3.1?
These details come from the linked publisher material for this model. Reported capabilities and training descriptions are publisher statements, not independent test results.
- Model specialization
- Coding-focused update that can serve as a starting point for agentic fine-tuning. Source
- Training procedure
- Post-training combines supervised fine-tuning on synthetic and public data with RLOO reinforcement learning using verifiable rewards. Source
- Tokenizer
- Uses cl100k_base without additional special tokens. Source
- Language scope
- English is the intended supported language; the publisher does not guarantee other-language capability. Source
- Conversation handling
- Stop generation at <sep> or the end-of-text token; the card recommends removing earlier assistant reasoning traces before the next conversation turn. Source
What is documented about the reka-flash-3.1 checkpoint?
This evidence refers to RekaAI/reka-flash-3.1 at recorded revision dcf8d6ee3219ca177b519cab47777d42864b54bd, checked October 23, 2026. Repository metadata
Safetensors metadata records 20,905,482,240 stored parameters. This is a stored-weight count, not necessarily the number activated per token, a download size or a GPU-memory requirement. Repository metadata
Recorded architecture class: LlamaForCausalLM. Repository metadata
Repository access gate: false. This records the repository's gate setting when checked; licensing and use terms still apply. Repository metadata
What the configuration file says
The pinned config.json contains these values. Pinned configuration
max_position_embeddings- 98,304
torch_dtype- bfloat16
num_attention_heads- 64
num_key_value_heads- 8
num_hidden_layers- 44
hidden_size- 6,144
Configuration values describe the checkpoint and its implementation. In particular, max_position_embeddings, sliding_window and rope_scaling do not independently establish an API context limit, tested usable length or hardware requirement. Runtime, quantization, cache, batch size and input length affect deployment behavior.
Read the retrieved model card for setup and qualifications. Model card
Keep the exact version in view
Other reka models from Reka.
These are separate records in the same publisher family. A shared family name does not establish equal capabilities or interchangeable licenses.
reka-edge-2603
API · Open weights · 16,384 context tokens
reka-flash-3
API · Open weights · 64,000 context tokens
The documented record
Specifications, with their sources.
A missing value remains unknown. Input limits, output limits and the total context window are separate measurements.
- Publisher
- RekaSource ↗
- Family
- rekaSource ↗
- Version
- reka-flash-3.1Source ↗
- Availability
- Listed by publisherSource ↗
- Access
- Open weightsSource ↗
- Inputs
- TextSource ↗
- Outputs
- TextSource ↗
- Context window
- Not documented
- Maximum input
- Not documented
- Maximum output
- Not documented
- Knowledge cutoff
- Not documented
- Training-data cutoff
- Not documented
- Training completed
- Not documented
- Release date
- Not documented
- License
- apache-2.0Source ↗
- Input price / 1M tokens
- Not documented
- Output price / 1M tokens
- Not documented
Read this with the numbers.
Official publisher inventory entry. Missing fields have not been verified. Repository timestamps are not release dates. Publisher repository evidence (2026-10-23): Published architecture metadata: LlamaForCausalLM. Published safetensors metadata counts 20,905,482,240 stored parameters; this is not an active-parameter count for mixture-of-experts models. Published configuration: max_position_embeddings=98304; dtype=bfloat16; 44 hidden layers. Checkpoint configuration is not a verified hosted serving limit; context and output limits remain separate documented fields.
Model identifiers and aliases 2
RekaAI/reka-flash-3.1RekaAI/reka-flash-3.1-rekaquant-q3_k_s
Follow the evidence