Provider key onboarding probe

ByteDance (Doubao) | key onboarding readiness

ByteDance (Doubao) key onboarding readiness decides whether a key can move from identification into inventory, pricing, routing, and launch. TestKey starts with 1 covered models, China route, sample models UI-TARS 7B, then verifies with read-only probes.

Provider

ByteDance (Doubao)

China route

Model coverage

1

UI-TARS 7B

Probe dimension

key onboarding readiness

onboarding-readiness

Onboarding signal

limited model coverage, confirm provider identity first

bytedance

Provider onboarding summary

Provider

ByteDance (Doubao)

Probe dimension

onboarding-readiness

Model coverage

1

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

Why this probe matters

ByteDance (Doubao) key onboarding readiness decides whether a key can move from identification into inventory, pricing, routing, and launch. TestKey starts with 1 covered models, China route, sample models UI-TARS 7B, then verifies with read-only probes.

Provider: ByteDance (Doubao)
Model coverage: 1
Probe dimension: key onboarding readiness

How to prove it

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

Identify the real provider first, then verify key onboarding readiness; do not treat OpenAI-compatible as real OpenAI by default.
Use 1 covered models as candidates, then read /models, balance, error bodies, and limit headers.
limited model coverage, confirm provider identity first

Next action

ByteDance (Doubao) key onboarding readiness should become an action: add provider config, fill pricing, import inventory, set route, add monitoring, or send to human review.

Read-only check. Detection data burns after 5 minutes.
Onboarding signal: limited model coverage, confirm provider identity first
Model coverage: UI-TARS 7B

Open key checker

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