inference/research
draftlow · 0.40updated 2026-10-05

Mercury

diffusion
This record is a draft. Not yet verified. Provisional. Treat every number on this page as provisional.

Fields

id
models/mercury
Family
mercury
Vendor
Mercury (Essential AI)
Release year
2025
Architecture
diffusion
Context scaling method
native
Attention variant
diffusion (non-autoregressive)
KV cache (bytes/token)
0
notes
Mercury is a diffusion language model listed in SGLang's supported diffusion language models. Specific architecture details (parameter count, layer count, denoising steps) could not be verified from the available sources. The SGLang docs page confirms it is served as a diffusion LM with --dllm-algorithm flags. More research needed to fill in the geometry. CONTEXT_SCALING_METHOD (native): diffusion (non-autoregressive) architecture record; no autoregressive position ladder. KV CACHE FIELD CLARIFIED (2026-10-05): kv_cache_bytes_per_token = 0 is correct here and means 'this architecture has no growing per-token KV cache', but it rests on the architecture CLASS rather than on a config read, because no config.json for Mercury is published - the record's own notes say the parameter and layer counts could not be verified. The reasoning: a diffusion language model denoises a fixed-length sequence through a fixed number of iterative steps rather than extending a cache one token at a time, so there is no cache whose size grows with generated length. It does still hold per-step activations for the current sequence, which is a memory cost, but that cost is bounded by sequence length and step count rather than accumulating across tokens as a KV cache does. So the 0 is honest, and a reader should not read it as 'unknown' - but it also should not read it as 'verified from config', since no config exists. This is the same distinction the three voyage records needed: a claim about cache behaviour, not a measurement of it.

Notes

Mercury is a diffusion language model listed in SGLang's supported diffusion language models. Specific architecture details (parameter count, layer count, denoising steps) could not be verified from the available sources. The SGLang docs page confirms it is served as a diffusion LM with --dllm-algorithm flags. More research needed to fill in the geometry.

CONTEXT_SCALING_METHOD (native): diffusion (non-autoregressive) architecture record; no autoregressive position ladder. KV CACHE FIELD CLARIFIED (2026-10-05): kv_cache_bytes_per_token = 0 is correct here and means 'this architecture has no growing per-token KV cache', but it rests on the architecture CLASS rather than on a config read, because no config.json for Mercury is published - the record's own notes say the parameter and layer counts could not be verified. The reasoning: a diffusion language model denoises a fixed-length sequence through a fixed number of iterative steps rather than extending a cache one token at a time, so there is no cache whose size grows with generated length. It does still hold per-step activations for the current sequence, which is a memory cost, but that cost is bounded by sequence length and step count rather than accumulating across tokens as a KV cache does. So the 0 is honest, and a reader should not read it as 'unknown' - but it also should not read it as 'verified from config', since no config exists. This is the same distinction the three voyage records needed: a claim about cache behaviour, not a measurement of it.

Cross-references

This record references no other records — it is a leaf. It is cited by 0.