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

Inception: Mercury | reset window

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

Model
inception/mercury
Inception: Mercury
Provider
Inception
3 models in catalog
Limit dimension
reset window
reset-window
Visible signal
real key probe required
Context window: 128,000
Limit matrix summary
Model
inception/mercury
Limit dimension
reset-window
Visible signal
real key probe required
Read-only check. Detection data burns after 5 minutes.
Read-only check. Detection data burns after 5 minutes.

Why this limit matters

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

  • Model: inception/mercury
  • Provider: Inception
  • Limit dimension: reset window

How to prove it

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

  • Start with the visible signal: real key probe required, then read headers and error bodies with read-only requests.
  • reset window must bind model ID inception/mercury; limits from another model at the same provider cannot be reused.
  • reset window · real key probe required · 128,000

Operator action

Inception: Mercury reset window 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: real key probe required
  • Context window: 128,000