TestKey.ai logo
TestKey.ai
KEY CHECKER & MODEL MARKET
You are hereHome
Model limit probe

Inception: Mercury 2 | max output limit

Inception: Mercury 2 max output limit decides whether a key can enter a production route. TestKey reads model ID inception/mercury-2, provider Inception, catalog context, real-key headers, 429 errors, and region signals together.

Model
inception/mercury-2
Inception: Mercury 2
Provider
Inception
3 models in catalog
Limit dimension
max output limit
max-output
Visible signal
catalog visible
Context window: 128,000
Limit matrix summary
Model
inception/mercury-2
Limit dimension
max-output
Visible signal
catalog visible
Read-only check. Detection data burns after 5 minutes.
Read-only check. Detection data burns after 5 minutes.

Why this limit matters

Inception: Mercury 2 max output limit decides whether a key can enter a production route. TestKey reads model ID inception/mercury-2, provider Inception, catalog context, real-key headers, 429 errors, and region signals together.

  • Model: inception/mercury-2
  • Provider: Inception
  • Limit dimension: max output limit

How to prove it

Read-only check. Detection data burns after 5 minutes.

  • Start with the visible signal: catalog visible, then read headers and error bodies with read-only requests.
  • max output limit must bind model ID inception/mercury-2; limits from another model at the same provider cannot be reused.
  • max output limit · catalog visible · 128,000

Operator action

Inception: Mercury 2 max output limit is not just a number. It should become route throttling, sale tags, headroom alerts, fallback model suggestions, and price protection.

  • Read-only check. Detection data burns after 5 minutes.
  • Visible signal: catalog visible
  • Context window: 128,000