Model limit probe

ByteDance Seed: Seed-2.0-Mini | context window limit

ByteDance Seed: Seed-2.0-Mini context window limit decides whether a key can enter a production route. TestKey reads model ID bytedance-seed/seed-2.0-mini, provider ByteDance Seed, catalog context, real-key headers, 429 errors, and region signals together.

Model

bytedance-seed/seed-2.0-mini

ByteDance Seed: Seed-2.0-Mini

Provider

ByteDance Seed

4 models in catalog

Limit dimension

context window limit

context-window

Visible signal

catalog visible

Context window: 262,144

Limit matrix summary

Model

bytedance-seed/seed-2.0-mini

Limit dimension

context-window

Visible signal

catalog visible

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

Why this limit matters

ByteDance Seed: Seed-2.0-Mini context window limit decides whether a key can enter a production route. TestKey reads model ID bytedance-seed/seed-2.0-mini, provider ByteDance Seed, catalog context, real-key headers, 429 errors, and region signals together.

Model: bytedance-seed/seed-2.0-mini
Provider: ByteDance Seed
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 bytedance-seed/seed-2.0-mini; limits from another model at the same provider cannot be reused.
context window limit · catalog visible · 262,144

Operator action

ByteDance Seed: Seed-2.0-Mini 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

ByteDance Seed: Seed-2.0-Mini

Open providers

ByteDance Seed