How much does Mercury 2 cost per million tokens?
Mercury 2 costs $0.250/1M input tokens and $0.750/1M output tokens in the gateway catalog snapshot (2026-06-27). Endpoint pricing may differ by fulfillment host.
Sourced from gateway catalog snapshot.
Mercury 2 costs $0.250/1M input tokens and $0.750/1M output tokens as of 2026-06-27. Openrouter publishes this model with a 128K tokens context window. o10 lists Mercury 2 on Together AI at routing band C2.
Last updated: 2026-06-27. Full catalog
Mercury 2 costs $0.250/1M input tokens and $0.750/1M output tokens in the gateway catalog snapshot (2026-06-27). Endpoint pricing may differ by fulfillment host.
Sourced from gateway catalog snapshot.
Mercury 2 is configured on Together AI. Each host maps to an upstream model ID listed in the fulfillment routes table. This model is routable through o10 eval-gated routing.
Mercury 2 supports a 128K tokens context window in the gateway catalog snapshot. Context limits may vary by fulfillment host endpoint.
Gateway snapshot pricing for Mercury 2.
| Unit | Price |
|---|---|
| Input | $0.25/1M tokens |
| Output | $0.75/1M tokens |
Upstream venues configured for Mercury 2.
| Host | Upstream model ID |
|---|---|
| inception | together_ai/mercury-2 |
Eval-gated model selection for this slug.
o10 slug: mercury-2. Band: C2. Routable: yes.
See [/models/routing](/models/routing) for smart aliases (o10/auto, o10/frontier, o10/squad) and [/kyi](/kyi) for governance.
Gateway catalog snapshot 2026-06-27. Fulfillment catalog synced from o10 control plane. Verify list prices against openrouter and host providers.
Mercury 2 costs $0.250/1M input tokens and $0.750/1M output tokens in the gateway snapshot (2026-06-27). Verify against your provider's published pricing.
Mercury 2 supports 128K tokens in the gateway catalog snapshot. Host-specific endpoints may differ.
Mercury 2 (mercury-2) is configured on: Together AI. Upstream model IDs are listed in the fulfillment routes section.
Yes. Mercury 2 is routable at band C2. Send model: "mercury-2" or use an o10 smart routing alias.
Use o10 slug "mercury-2" or gateway ID "inception/mercury-2" depending on your integration. Gateway-compatible endpoints accept OpenAI-style /v1 requests.
o10 routes Mercury 2 only when per-use-case evals clear at your quality floor. Band C2 indicates cost tier. See /kyi for governance and /models/routing for smart aliases.