Model limit probe

ByteDance: UI-TARS 7B | max output limit

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

max output limit

max-output

Visible signal

catalog visible

Context window: 128,000

Limit matrix summary

Model

bytedance/ui-tars-1.5-7b

Limit dimension

max-output

Visible signal

catalog visible

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

Why this limit matters

ByteDance: UI-TARS 7B max output limit 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: max output 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.
max output limit must bind model ID bytedance/ui-tars-1.5-7b; limits from another model at the same provider cannot be reused.
max output limit · catalog visible · 128,000

Operator action

ByteDance: UI-TARS 7B max output 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: 128,000

Open key checker

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

Open models

ByteDance: UI-TARS 7B

Open providers

ByteDance (Doubao)