Skip to content
Model infoModelsSnapshot: 15 Oct 2026

Inception / Mercury

Mercury Voice

Text-based diffusion LLM tuned for the language stage of low-latency voice agents.

restrictedClosed weightsText generationCoding
Official documentation (opens in a new tab)Reviewed 15 Oct 2026
11 of 17 specification fields collected
Context window128K128,000 tokens
Maximum output50K50,000 tokens
Input / 1M tokens$0.20Inception API
Output / 1M tokens$0.75USD · observed 15 Oct 2026

Specifications

Provider-documented facts. “Not collected” means we have not verified that field yet, not that the feature is unsupported.

Maximum input tokens
Not collected

No exact model-specific contract established in the reviewed evidence.

Parameters
Not collected

No exact model-specific contract established in the reviewed evidence.

Knowledge cutoff
Not collected

No exact model-specific contract established in the reviewed evidence.

Streaming
Not collected

No exact model-specific contract established in the reviewed evidence.

Batch processing
Not collected

No exact model-specific contract established in the reviewed evidence.

Fine-tuning
Not collected

No exact model-specific contract established in the reviewed evidence.

Context caching
SupportedSource for Context caching (opens in a new tab)

Automatic prefix caching; no documented TTL guarantee.

Architecture
Diffusion language model using parallel iterative refinement.Source for Architecture (opens in a new tab)

Exact parameter count and layer architecture are not published here.

Generation controls
Low, medium and high reasoning effort.Source for Generation controls (opens in a new tab)

Do not inherit the instant setting from Mercury 2/2.5.

Access & pricing

Prices belong to an endpoint and billing tier. A provider listing does not guarantee access for every account or region.

API model ID
Not collected

No exact callable model selector established for this offering.

Access
Enterprise API access by arrangement; provider documentation does not expose a confirmed exact model selector.
Regions
Deployment-dependent; complete serving region inventory unverified.
API endpoint
POST /v1/chat/completionsSource for API endpoint (opens in a new tab)
INPUT / 1M TOKENS$0.20
OUTPUT / 1M TOKENS$0.75

Advertised promotional snapshot on October 15, 2026. End date not published; verify current account pricing. Billed output includes reasoning. Cached input price: $0.02 / 1M tokens (base tier).

USD · observed 15 Oct 2026 · Pricing evidence (opens in a new tab)
Published billing units · original currency · observed 15 Oct 2026
CategoryUsageRateUnit
Undiscounted reference pricesInput1$0.401M tokens
Undiscounted reference pricesOutput1$1.501M tokens
Undiscounted reference pricesCached input1$0.041M tokens

Rate conditions

  1. Crossed-out regular rate in the provider pricing table, not the advertised promotional rate. No promotion end date is published.
Pricing source (opens in a new tab)

Data & enterprise terms

Terms permit using submissions for model training unless the user disables “Improve the model for everyone” in API Platform settings. The privacy policy uses purpose-dependent retention, not a fixed universal period. The FAQ says custom zero-retention arrangements are handled case by case; enterprise agreements may differ.

Read the service policy (opens in a new tab)

Caching

Caching can reuse earlier input processing. Availability, lifetime and billing depend on the endpoint. A cache hit still generates a new response.

01 / INITIAL INPUTProcess & retain

The system processes eligible input and retains reusable state.

02 / LATER REQUESTCheck available state

Reuse depends on matching input, session state and the cache policy.

03 / CACHE HITReuse & generate

Reusing state can reduce repeated work. Any charges follow the billing rules below.

Inception API

Documented
Support evidence (opens in a new tab)
How it works
Automatic prefix caching.Source for How it works (opens in a new tab)
Minimum reusable input
Not collected

Minimum prefix length not documented.

Lifetime & refresh
No documented TTL; pinning, invalidation and cache inspection are not exposed.Source for Lifetime & refresh (opens in a new tab)
How to enable it
Enabled automatically; no request parameter required.Source for How to enable it (opens in a new tab)
Usage fields
prompt_tokens includes cached_tokens; completion_tokens includes reasoning_tokens. Do not add nested counts again. Streaming usage requires stream_options.include_usage.Source for Usage fields (opens in a new tab)
Billing rules
Cache reads use the model-specific cached-input rate. Reasoning tokens are billed as output.Source for Billing rules (opens in a new tab)
Limits & data boundaries
Cache lifetime is not a customer-data-retention promise.Source for Limits & data boundaries (opens in a new tab)
Cache reads, writes & storage
ChargeApplies toRate / unit
Cache read1Text tokens · 50% launch promotion · end date unpublished$0.02 / 1M tokensPricing evidence (opens in a new tab)
Cached input2Undiscounted reference prices$0.04 / 1M tokensPricing evidence (opens in a new tab)

Rate conditions

  1. Advertised promotional snapshot on October 15, 2026. End date not published; verify current account pricing. Billed output includes reasoning.
  2. Crossed-out regular rate in the provider pricing table, not the advertised promotional rate. No promotion end date is published.

Observed 15 Oct 2026. Write rates and storage fees are different charges; use the billing rules above.

Caching reviewed 15 Oct 2026

What the measurements say

Time to first answer token · provider voice prompts

Inception · provider-reported
320ms (p50)

Real customer-service prompt set with low reasoning. Reported p95 is 750ms. Not a universal SLA or time-to-first-audio guarantee.

Evaluation source (opens in a new tab)

Latency and throughput depend on the host, request size, reasoning settings and load. There is no measured speed or global usage figure in this record.

The record behind the model

Why it is included

Inception’s own Trust Center describes the Mercury family as proprietary. Public API and enterprise deployment access do not establish public weights.

Classification evidence (opens in a new tab)

Sources reviewed