Prueba de incorporación de key proveedor

Replicate | verificar key onboarding readiness

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

Proveedor

Replicate

ruta global

Cobertura de modelos

0

Replicate

Dimensión de prueba

verificar key onboarding readiness

onboarding-readiness

Señal de onboarding

limited model coverage, confirm provider identity first

replicate

Read-only probes

4

current_key / usage_report

Sample metrics

12

key_valid / owner_id / organization_id / token_type

Ten capabilities

5

operational actions / key identity / capability matrix

Resumen de onboarding proveedor

Proveedor

Replicate

Dimensión de prueba

onboarding-readiness

Cobertura de modelos

0

Solo lectura. Datos eliminados tras 5 minutos.

Por qué importa esta prueba

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

Proveedor: Replicate
Cobertura de modelos: 0
Dimensión de prueba: verificar key onboarding readiness

Cómo probarlo

Solo lectura. Datos eliminados tras 5 minutos.

Identify the real provider first, then verify verificar 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

Siguiente acción

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

Solo lectura. Datos eliminados tras 5 minutos.
Señal de onboarding: limited model coverage, confirm provider identity first
Cobertura de modelos: Replicate

Diez capacidades de key

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

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

Abrir checker

Solo lectura. Datos eliminados tras 5 minutos.