TestKey.ai logo
TestKey.ai
KEY CHECKER & MODEL MARKET
You are hereHome
Core routes

Keep clicks and crawl depth focused on the few pages that resolve intent fastest.

Already holding a key? Check it first, then keep reading.
Confirm ownership, visible models, and resale signals before deciding whether models, pricing, protocols, or providers matter next.
Provider key onboarding probe

NVIDIA | key onboarding readiness

NVIDIA key onboarding readiness decides whether a key can move from identification into inventory, pricing, routing, and launch. TestKey starts with 11 covered models, global route, sample models Llama 3.1 Nemotron 70B Instruct · Llama 3.1 Nemotron Ultra 253B v1 · Llama 3.3 Nemotron Super 49B V1.5, then verifies with read-only probes.

Provider
NVIDIA
global route
Model coverage
11
Llama 3.1 Nemotron 70B Instruct · Llama 3.1 Nemotron Ultra 253B v1 · Llama 3.3 Nemotron Super 49B V1.5
Probe dimension
key onboarding readiness
onboarding-readiness
Onboarding signal
multi-model coverage, suitable for read-only identification first
nvidia
Read-only probes
1
current_key
Sample metrics
8
key_valid / requests_total / runtime_model / runtime_model_allowed
Ten capabilities
6
operational actions / model permission matrix / limit matrix
Provider onboarding summary
Provider
NVIDIA
Probe dimension
onboarding-readiness
Model coverage
11
Read-only check. Detection data burns after 5 minutes.
Read-only check. Detection data burns after 5 minutes.

Why this probe matters

NVIDIA key onboarding readiness decides whether a key can move from identification into inventory, pricing, routing, and launch. TestKey starts with 11 covered models, global route, sample models Llama 3.1 Nemotron 70B Instruct · Llama 3.1 Nemotron Ultra 253B v1 · Llama 3.3 Nemotron Super 49B V1.5, then verifies with read-only probes.

  • Provider: NVIDIA
  • Model coverage: 11
  • 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 11 covered models as candidates, then read /models, balance, error bodies, and limit headers.
  • multi-model coverage, suitable for read-only identification first

Next action

NVIDIA 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: multi-model coverage, suitable for read-only identification first
  • Model coverage: Llama 3.1 Nemotron 70B Instruct · Llama 3.1 Nemotron Ultra 253B v1 · Llama 3.3 Nemotron Super 49B V1.5

Ten key capability anchors

NVIDIA has 1 read-only account probes configured, currently supporting operational actions / model permission matrix / limit matrix / continuous monitoring / key identity / capability matrix. These anchors feed the real TestKey detection path, not just admin display.

  • Read-only probes: current_key, used to prove provider identity, models, balance, or subscription state.
  • Sampleable metrics: key_valid / requests_total / runtime_model / runtime_model_allowed / tokens_limit / bucket_start / token_role / token_scopes.
  • Ten-capability anchors: operational actions / model permission matrix / limit matrix / continuous monitoring / key identity.