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

Free Models Router | context window limit

Free Models Router context window limit decides whether a key can enter a production route. TestKey reads model ID openrouter/free, provider Openrouter, catalog context, real-key headers, 429 errors, and region signals together.

Model
openrouter/free
Free Models Router
Provider
Openrouter
3 models in catalog
Limit dimension
context window limit
context-window
Visible signal
catalog visible
Context window: 200,000
Limit matrix summary
Model
openrouter/free
Limit dimension
context-window
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

Free Models Router context window limit decides whether a key can enter a production route. TestKey reads model ID openrouter/free, provider Openrouter, catalog context, real-key headers, 429 errors, and region signals together.

  • Model: openrouter/free
  • Provider: Openrouter
  • Limit dimension: context window 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.
  • context window limit must bind model ID openrouter/free; limits from another model at the same provider cannot be reused.
  • context window limit · catalog visible · 200,000

Operator action

Free Models Router context window 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: 200,000