Remova Logo
Operational Fit Analysis

Mercury

Mercury is a cost-efficient model with standard context support, optimized for code generation and agent workflows in enterprise environments.

Use Mercury in your company

Data checked: 2026-03-19

Context Window
128,000
Input / 1M
$0.25
Output / 1M
$0.75

Model Positioning

Inception lists Mercury as a standard context option with $0.25 per 1M tokens input pricing, $0.75 per 1M tokens output pricing, and text->text modality support for enterprise AI operations.

  • Latest profile indicates standard context capacity for enterprise prompts and documents.
  • Current pricing band is cost-efficient: $0.25 per 1M tokens input and $0.75 per 1M tokens output.
  • Best-fit workloads include: Code generation, Agent workflows, Low-latency assistants.
  • Apply department budgets and alert thresholds from day one.

Key Specs

Model ID
inception/mercury
Context Window
128,000 tokens
Modality
text->text
Input Modalities
text
Output Modalities
text
Input Price
$0.25 per 1M tokens
Output Price
$0.75 per 1M tokens
Provider
Inception
Listing Date
2025-06-26

Strengths

  • Mercury is suited for code generation.
  • Supports standard context for multi-step prompts and larger working sets.
  • Pricing profile is cost-efficient, enabling predictable workload routing decisions.
  • Can be paired with policy guardrails for safer deployment at scale.

Tradeoffs

  • Governance controls are still required for regulated or sensitive workflows.
  • Standard context limits may require chunking or retrieval strategies for large documents.
  • Low-cost tiers can still underperform on high-consequence decisions without escalation paths.
  • Text-only modality can limit workflows that rely on image, audio, or document interpretation.

High-Fit Use Cases

  • Mercury for software delivery workflows with policy-enforced prompts.
  • Mercury for tool-driven automation with governance checkpoints.
  • Mercury for high-volume assistant traffic with low-response targets.
  • Mercury for governed enterprise assistant workflows across teams.

Deployment Checklist

  • Define where Mercury is default vs. fallback in your routing policy.
  • Enable role-based access and policy checks before opening access broadly.
  • Set spend guardrails by team and monitor weekly token consumption.
  • measure business impact against cost before scaling usage.
  • Re-run quality and cost benchmarks monthly as newer releases appear.

Start Smaller

Safe AI Use Case Selector

Choose your team and goals, then start with the AI use cases that fit best and carry the least risk.

You get

Recommended first use cases for your company.

Send to my email

Parameter Guidance

max_tokens

Set completion limits to avoid unpredictable long-output spend.

response_format

Prefer structured output where responses feed internal systems.

stop

Use stop sequences to keep output boundaries consistent across automations.

structured_outputs

Use this parameter only with tested defaults in production workflows.

Start Smaller

AI Risk Test

Test what can go wrong before teams start using AI loosely across the company.

You get

A short risk summary with the main gaps to close.

Send to my emailBook demo
Knowledge Hub

Mercury FAQs

Choose Mercury when the workload aligns with code generation, agent workflows, low-latency assistants and quality targets justify its pricing profile.
It depends on workload mix. Most organizations use routing policies so routine traffic stays on lower-cost tiers.
Validate quality on real internal prompts, token efficiency, latency, and policy compliance behavior.

Deploy This Model With Governance

Use policy controls, role-based access, and budget guardrails before enabling advanced model tiers at scale.

Use Mercury in your company