Prueba de incorporación de key proveedor

Meta | verificar key onboarding readiness

Meta verificar key onboarding readiness decides whether a key can move from identification into inventory, pricing, routing, and launch. TestKey starts with 14 covered models, ruta global, sample models Llama 3.1 70B Instruct · Llama 3.1 8B Instruct · Llama 3.2 11B Vision Instruct, then verifies with read-only probes.

Proveedor

Por qué importa esta prueba

Meta verificar key onboarding readiness decides whether a key can move from identification into inventory, pricing, routing, and launch. TestKey starts with 14 covered models, ruta global, sample models Llama 3.1 70B Instruct · Llama 3.1 8B Instruct · Llama 3.2 11B Vision Instruct, then verifies with read-only probes.

Proveedor: Meta
Cobertura de modelos: 14
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 14 covered models as candidates, then read /models, balance, error bodies, and limit headers.
multi-model coverage, suitable for read-only identification first

Siguiente acción

Meta 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: multi-model coverage, suitable for read-only identification first
Cobertura de modelos: Llama 3.1 70B Instruct · Llama 3.1 8B Instruct · Llama 3.2 11B Vision Instruct

Abrir checker

Solo lectura. Datos eliminados tras 5 minutos.

Abrir proveedores