Model limit probe

StepFun: Step 3.5 Flash | context window limit

StepFun: Step 3.5 Flash context window limit decides whether a key can enter a production route. TestKey reads model ID stepfun/step-3.5-flash, provider StepFun AI, catalog context, real-key headers, 429 errors, and region signals together.

Model

stepfun/step-3.5-flash

StepFun: Step 3.5 Flash

Provider

StepFun AI

1 models in catalog

Limit dimension

context window limit

context-window

Visible signal

catalog visible

Context window: 262,144

Limit matrix summary

Model

stepfun/step-3.5-flash

Limit dimension

context-window

Visible signal

catalog visible

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

Why this limit matters

StepFun: Step 3.5 Flash context window limit decides whether a key can enter a production route. TestKey reads model ID stepfun/step-3.5-flash, provider StepFun AI, catalog context, real-key headers, 429 errors, and region signals together.

Model: stepfun/step-3.5-flash
Provider: StepFun AI
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 stepfun/step-3.5-flash; limits from another model at the same provider cannot be reused.
context window limit · catalog visible · 262,144

Operator action

StepFun: Step 3.5 Flash 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: 262,144

Open key checker

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

Open models

StepFun: Step 3.5 Flash

Open providers

StepFun AI