Model limit probe

ByteDance: UI-TARS 7B | reset window

ByteDance: UI-TARS 7B reset window decides whether a key can enter a production route. TestKey reads model ID bytedance/ui-tars-1.5-7b, provider ByteDance (Doubao), catalog context, real-key headers, 429 errors, and region signals together.

Model

bytedance/ui-tars-1.5-7b

ByteDance: UI-TARS 7B

Provider

ByteDance (Doubao)

1 models in catalog

Limit dimension

reset window

reset-window

Visible signal

real key probe required

Context window: 128,000

Limit matrix summary

Model

bytedance/ui-tars-1.5-7b

Limit dimension

reset-window

Visible signal

real key probe required

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

Why this limit matters

ByteDance: UI-TARS 7B reset window decides whether a key can enter a production route. TestKey reads model ID bytedance/ui-tars-1.5-7b, provider ByteDance (Doubao), catalog context, real-key headers, 429 errors, and region signals together.

Model: bytedance/ui-tars-1.5-7b
Provider: ByteDance (Doubao)
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 bytedance/ui-tars-1.5-7b; limits from another model at the same provider cannot be reused.
reset window · real key probe required · 128,000

Operator action

ByteDance: UI-TARS 7B 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

Open key checker

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

Open models

ByteDance: UI-TARS 7B

Open providers

ByteDance (Doubao)