Provider key onboarding probe

Stability AI | key onboarding readiness

Stability AI key onboarding readiness decides whether a key can move from identification into inventory, pricing, routing, and launch. TestKey starts with 0 covered models, global route, sample models Stability AI, then verifies with read-only probes.

Provider

Stability AI

global route

Model coverage

0

Stability AI

Probe dimension

key onboarding readiness

onboarding-readiness

Onboarding signal

limited model coverage, confirm provider identity first

stability

Read-only probes

3

current_key / balance_snapshot

Sample metrics

12

key_valid / owner_id / organization_id / token_type

Ten capabilities

5

operational actions / key identity / capability matrix

Provider onboarding summary

Provider

Stability AI

Probe dimension

onboarding-readiness

Model coverage

0

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

Why this probe matters

Stability AI key onboarding readiness decides whether a key can move from identification into inventory, pricing, routing, and launch. TestKey starts with 0 covered models, global route, sample models Stability AI, then verifies with read-only probes.

Provider: Stability AI
Model coverage: 0
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 0 covered models as candidates, then read /models, balance, error bodies, and limit headers.
limited model coverage, confirm provider identity first

Next action

Stability AI 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: Stability AI

Ten key capability anchors

Stability AI has 3 read-only account probes configured, currently supporting operational actions / key identity / capability matrix / balance and quota / model permission matrix. These anchors feed the real TestKey detection path, not just admin display.

Read-only probes: current_key / balance_snapshot, used to prove provider identity, models, balance, or subscription state.
Sampleable metrics: key_valid / owner_id / organization_id / token_type / token_role / token_scopes / balance_available / balance_total / ....
Ten-capability anchors: operational actions / key identity / capability matrix / balance and quota / model permission matrix.

Open key checker

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