The Rundown AI homepage

Independent tool overview

Mercury 2 at a glance

Mercury 2 is Inception's active text reasoning model built around diffusion decoding, which refines multiple token positions in parallel instead of generating strictly one token at a time. Inception positions it for low-latency voice agents, customer support, search pipelines, tool use and rapid coding workflows, and advertises more than 1,000 tokens per second on NVIDIA H100 hardware. The OpenAI-compatible API supports a 128K context window, up to 50,000 output tokens, structured outputs, streaming and four reasoning-effort levels. Current list pricing is $0.25 per million input tokens, $0.025 per million cached-input tokens and $0.75 per million output tokens. Performance claims are workload- and hardware-dependent vendor results; production teams must benchmark end-to-end latency, accuracy, safety, tool authorization and cost on their own traffic.

Visit the official Mercury 2 site ↗
Mercury 2 product preview
Developer
Inception AI, Inc.
Model type
Text diffusion reasoning language model
API model ID
mercury-2
API compatibility
OpenAI-compatible chat completions
Context window
128K tokens
Maximum output
50,000 tokens; 16,384 default in model docs
Reasoning levels
Instant, low, medium and high
Input price
$0.25 per 1M tokens
Cached-input price
$0.025 per 1M tokens
Output price
$0.75 per 1M tokens
New-account promotion
100M free tokens currently advertised in docs; verify in dashboard
Modalities
Text input and output
Tool calling
Supported; not recommended in instant mode
Prompt training control
Opt out in platform settings
Reviewed
August 31, 2026

Overview

What Mercury 2 is

Mercury 2 is Inception's current general-purpose reasoning diffusion language model. It is an API model, not a complete phone system: a voice deployment still needs speech recognition, text-to-speech, telephony, orchestration, monitoring and human escalation.

Diffusion generation works by refining a span of noisy text over repeated denoising passes, allowing many token positions to be processed together. That differs from conventional left-to-right autoregressive decoding and is the basis for Inception's low-latency claims.

Inception reports more than 1,000 decoded tokens per second on standard NVIDIA H100 GPUs and roughly 300 milliseconds for a 300-token reasoning trace. Those figures are vendor measurements, not guaranteed end-to-end response times.

The model exposes instant, low, medium and high reasoning-effort settings. Instant prioritizes responsiveness and is documented for turns that do not need tool calls; medium is the official default for most applications.

The OpenAI-compatible chat-completions endpoint supports text, a 128K context window, a 50,000-token maximum output, tool calling and structured outputs. Streaming returns blocks, while an optional diffusing mode exposes changing intermediate denoising text and should not be shown as a stable final answer.

Inception highlights realtime voice, customer support, enterprise search, workflow subagents and rapid coding iteration. Its voice cost example estimates only the model layer and explicitly excludes transcription, speech synthesis and telephony.

Current list prices are $0.25 per million input tokens, $0.025 per million cached-input tokens and $0.75 per million output tokens. Inception's docs currently advertise 100 million free tokens for a new account, although one marketing-page line still says 10 million; confirm the actual grant and expiration in the platform.

A low model-token price does not equal a low total voice-call price. Resent conversation history, reasoning tokens, retries, tool calls, retrieval, speech services, phone minutes, logging and human transfers can dominate the real bill.

Inception's terms prohibit misinformation, political campaign content and high-stakes decision-making involving individual rights. They also say the service is for internal personal use and not on behalf of a third party, language that production or customer-facing buyers should reconcile with Inception in writing.

Prompts and other user submissions may be used to train Inception's models unless the account setting called Improve the model for everyone is turned off. The privacy policy also covers personal data in prompts and uploads and provides only purpose-based, not fixed, retention language.

Fast reasoning does not remove hallucinations, prompt injection, tool mistakes or policy failures. Voice agents need deterministic authorization, least-privilege tools, confirmation before consequential actions, transcript review, disclosure that the caller is speaking with AI and an immediate human handoff path.

Use cases

Who Mercury 2 is best for

The strongest fit depends on the job you need the product to complete, not the size of its feature list.

Latency-sensitive voice orchestration

Serving as the text-reasoning layer in an ASR-to-LLM-to-TTS pipeline where pauses are tightly budgeted.

Multi-step customer support

Handling tool-assisted support flows with explicit confirmation, limited permissions and human escalation.

Agentic search pipelines

Running repeated query rewriting, reranking and summarization calls where per-hop latency compounds.

High-volume classification

Producing structured routing, extraction and policy checks after schema and error-rate validation.

OpenAI-compatible migrations

Testing a faster endpoint with familiar request shapes while auditing every behavioral difference.

Rapid coding loops

Generating or reviewing text and code quickly when the general Mercury 2 model is preferable to the specialized Mercury Edit 2.

Capabilities

Core Mercury 2 features

1

Parallel diffusion decoding

Refines multiple positions across bounded denoising passes rather than decoding only left to right.

2

Reasoning-effort control

Offers instant, low, medium and high modes to trade response depth for latency.

3

OpenAI-compatible endpoint

Uses the familiar v1/chat/completions shape and works through several common client libraries.

4

128K context

Accepts long text conversations and instructions, with token cost and retrieval quality still requiring management.

5

Long outputs

Allows as many as 50,000 output tokens, with a documented default of 16,384.

6

Tool use

Can return tool calls for application-side execution; the application remains responsible for validation and authorization.

7

Structured outputs

Supports constrained JSON schemas for extraction and workflow integration.

8

Standard streaming

Returns completed response blocks progressively for chat and realtime interfaces.

9

Diffusing display mode

Can expose the full changing text at each denoising step for demonstration or specialized interfaces.

10

Prompt caching price

Charges cached input at one-tenth of the standard input-token rate under the published table.

11

Integration ecosystem

Official docs show use with OpenAI clients, LangChain, LiteLLM, AISuite and Vercel AI SDK.

Process

How the Mercury 2 workflow works

  1. Step 1

    Confirm the use is permitted

    Map the application against the current restrictions on high-stakes individual-rights decisions, misinformation, political campaigns and third-party use; obtain written terms for production ambiguity.

  2. Step 2

    Classify data before sending it

    Exclude secrets, regulated records and unnecessary personal data; turn off Improve the model for everyone before any sensitive authorized test.

  3. Step 3

    Build an end-to-end baseline

    Measure speech recognition, network, model, tools, speech synthesis and telephony separately instead of treating token throughput as caller-perceived latency.

  4. Step 4

    Create a representative test set

    Include common requests, accents, interruptions, ambiguous instructions, angry callers, prompt injection, rare edge cases and unsupported requests.

  5. Step 5

    Start at medium reasoning

    Use Inception's default, then test low or instant only on simple turns; do not use instant for tool calls under the current documentation.

  6. Step 6

    Constrain outputs

    Use structured schemas, explicit allowed actions, refusal rules and deterministic validation before downstream processing.

  7. Step 7

    Give tools least privilege

    Use narrowly scoped credentials, server-side authorization and allowlists; never let model text directly choose arbitrary endpoints or arguments.

  8. Step 8

    Require confirmation

    Read back names, dates, amounts, appointments and account changes and obtain clear user confirmation before committing an action.

  9. Step 9

    Keep high-stakes decisions human

    Do not let the model decide eligibility, employment, credit, healthcare, legal rights or other consequential outcomes; route those to authorized people.

  10. Step 10

    Design transparent escalation

    Disclose the AI agent, make a human transfer available and preserve context so callers do not have to repeat sensitive information.

  11. Step 11

    Load-test real concurrency

    Measure p50, p95 and p99 latency, rate limiting, timeouts, retries and cost during realistic bursts; published rate limits can still vary with GPU availability.

  12. Step 12

    Monitor production continuously

    Review sampled transcripts with access controls, track failed actions and hallucinations, cap spend and maintain a rollback model.

Cost

Mercury 2 pricing and free plan

List pricing checked August 31, 2026 is $0.25 per million input tokens, $0.025 per million cached-input tokens and $0.75 per million output tokens. Current documentation advertises 100 million free tokens for new accounts without payment details, while an older line on the model page still says 10 million; confirm the actual promotional balance and any expiration after signup. Enterprise pricing, custom rate limits and SLA guarantees require sales contact. Voice-system cost also includes ASR, TTS, telephony, tools, storage and support.

Free

100M promotional tokens advertised

Trial access to Inception's models without payment details under the current documentation.

  • Documentation currently says 100 million tokens
  • One model-page line still says 10 million; verify the dashboard
  • Free limits: 1,000 requests, 1M input tokens and 100K output tokens per minute
  • Subject to GPU availability and account terms

Pay As You Go

$0.25 input / $0.025 cached / $0.75 output per 1M tokens

Usage-based API access after the promotional balance.

  • 3,000 requests per minute
  • 3 million input tokens per minute
  • 300,000 output tokens per minute
  • Published limits may be affected by demand and GPU availability

Enterprise

Custom

Negotiated production capacity, security terms and support.

  • Custom rate limits
  • SLA guarantees
  • Security and privacy review
  • Volume-based pricing

Pricing checked . Check current pricing at the source ↗

Assessment

Mercury 2 strengths and limitations

Where it stands out

  • Very low published token prices for a reasoning-capable API.
  • Vendor-reported throughput is unusually high on supported NVIDIA hardware.
  • Four reasoning levels let applications reserve deeper reasoning for harder turns.
  • OpenAI-compatible request shapes reduce initial integration work.
  • Tool calling and structured outputs support production workflow patterns.
  • A 128K context window and long output ceiling cover many text workloads.
  • Current free-token promotion is large enough for substantial benchmarking.
  • The cascaded voice architecture preserves transcripts and lets teams choose separate speech vendors.
  • Published docs expose rate limits, endpoint behavior, pricing and a training opt-out control.

What to consider

  • The 1,000-plus token-per-second and 300-millisecond figures are vendor claims tied to particular prompts, settings and hardware, not an application latency guarantee.
  • Mercury 2 is text-only; realtime voice needs separate transcription, synthesis, telephony and orchestration.
  • Instant mode trades intelligence for speed and is documented for turns that do not require tool calling.
  • The optional diffusing stream exposes unstable intermediate text that can change before the final answer.
  • Tool calls can be wrong, manipulated by prompt injection or unsafe without server-side authorization.
  • The model can hallucinate, omit constraints and generate confident but incorrect answers like other language models.
  • The current terms prohibit high-stakes decision-making involving individual rights, political campaign content and misinformation.
  • Terms describing only internal personal use and no use on behalf of a third party appear difficult to reconcile with marketed customer-support and enterprise use cases; production buyers need clarification.
  • User submissions may be used for model training unless the account-level improvement setting is turned off.
  • The privacy policy includes personal data in prompts and uploads and does not publish one simple fixed retention period for all API content.
  • Output use rights remain subject to compliance, third-party rights and the provider's broad disclaimers.
  • Free-token copy is inconsistent between current documentation and a stale model-page line.
  • Rate limits and latency can vary with demand and GPU availability.
  • The provider is newer and has a shorter public operational history than major cloud-model vendors.
  • Total voice cost can materially exceed model-token cost after ASR, TTS, telephony, tools, logging and human escalation.

Compare

Mercury 2 alternatives

The right alternative depends on the specific output, workflow, controls and budget your project requires.

Consumer

Gemini 3 Flash

A broad fast-reasoning model alternative for teams comparing quality, multimodality, ecosystem and latency.

Explore Gemini 3 Flash

Agents

Grok Voice Agent

A more integrated voice-agent API when native speech interaction matters more than choosing each cascade component.

Explore Grok Voice Agent

Sales

Vapi

An orchestration platform for combining telephony, speech providers and language models, including Mercury-compatible architectures.

Explore Vapi

Business Operations

Retell AI

A managed conversational-voice platform for teams that prefer a fuller agent stack over a standalone model API.

Explore Retell AI

Business Operations

Voiceflow

A visual platform for designing, testing and managing chat and voice agents with broader workflow tooling.

Explore Voiceflow

Questions

Mercury 2 FAQs

What is Mercury 2?

It is Inception's text reasoning diffusion language model, exposed through an OpenAI-compatible API and positioned for low-latency voice, support, search and agent workflows.

Is Mercury 2 a voice model?

No. It is the text-reasoning layer. A phone agent still needs automatic speech recognition, text-to-speech, telephony and orchestration.

How fast is Mercury 2?

Inception reports more than 1,000 decoded tokens per second on NVIDIA H100 GPUs and about 300 milliseconds for a 300-token reasoning trace. Benchmark the complete application because network, queue, prompt, tool and speech latency differ.

How much does Mercury 2 cost?

The list price is $0.25 per million input tokens, $0.025 per million cached-input tokens and $0.75 per million output tokens.

Does Mercury 2 have a free tier?

Current documentation advertises 100 million free tokens for new accounts without payment details. One public page retains an older 10-million figure, so verify the awarded balance and expiration in the platform.

What context window does Mercury 2 support?

The production-model table lists a 128K-token chat context window and a maximum output of 50,000 tokens, with 16,384 as the documented default output limit.

What does reasoning_effort do?

It selects instant, low, medium or high reasoning. Medium is the official general default; instant is for near-realtime simple turns and is not recommended for tool calling.

Does Mercury 2 support tool calling?

Yes, except that the docs advise against tool use in instant mode. The application must validate arguments, authorize actions and require confirmation for consequential changes.

Does it support structured outputs?

Yes. Mercury 2 can target a supplied JSON schema, but applications should still validate every response and handle refusals or malformed data.

Are prompts used for training?

The terms say user submissions may be used to train models unless Improve the model for everyone is turned off in API Platform settings. Enterprise buyers should obtain contract-specific data terms.

Can Mercury 2 make healthcare, credit or employment decisions?

Do not use it to make high-stakes decisions about individual rights. The current terms prohibit that category, and consequential decisions require authorized human review regardless.

Is Mercury 2 a drop-in replacement for another OpenAI-compatible model?

The endpoint shape is compatible, but behavior is not identical. Retest prompts, streaming, tool schemas, structured outputs, token accounting, safety, retries and latency before migration.

Why is total voice cost higher than the token estimate?

The advertised estimate covers only Mercury 2. Production also pays for transcription, synthesis, phone minutes, conversation history, reasoning output, tools, storage, monitoring and human handoffs.

Bottom line

Our Mercury 2 verdict

Mercury 2 is a compelling model to benchmark when every sequential model call adds visible delay, especially in voice and multi-hop search. Its combination of diffusion decoding, OpenAI-compatible integration and $0.25/$0.75 token pricing is differentiated. The responsible buying decision depends on production evidence: measure full-pipeline p95 latency and accuracy, clarify the provider's customer-facing-use terms, disable prompt training where required, constrain every tool and preserve human control over consequential actions. Speed is valuable only when the system remains correct, permitted and recoverable.

Visit Mercury 2 website ↗
The Rundown University

AI training for the future of work.

Get access to all our AI courses, hundreds of real-world AI use cases, live expert-led workshops, an exclusive network of AI early adopters, and more.

AI Courses

Get unlimited access to all of our current & upcoming industry-specific AI courses for the duration of your subscription.

Daily Guides

To keep up with the rapid pace of AI, our team publishes AI implementation guides daily. Our library contains 300+ practical use cases to automate real-world work.

Workshops

Join weekly, live, interactive sessions with industry leaders who are at the forefront of AI for hands-on implementation guidance and exclusive insights.

Community

Network with an exclusive community of AI-first professionals who are working smarter with AI. Learn how early adopters are using AI in their work and businesses.