Protocol and SDK support
Treat each model's protocols field from /v1/models as authoritative. The model page and customer workspace derive protocol and SDK badges only from that field, never from a model name or family. Do not call a model through a protocol it does not list.
An AICredits API Key is only for the AI Credits data API; it is not an official key issued by any Provider. Current executable examples consistently use Authorization: Bearer $AICREDITS_API_KEY.
protocols value | API shape | SDK badge | Current authentication status |
|---|---|---|---|
openai_chat_completions | OpenAI Chat Completions | OpenAI SDK | Available with Bearer |
openai_responses | OpenAI Responses | OpenAI SDK | Available with Bearer |
openai_images | OpenAI Images | OpenAI SDK | Available with Bearer |
anthropic_messages | Anthropic Messages | Anthropic SDK · Coming soon | Use Bearer now; the SDK-default x-api-key is not enabled yet |
gemini | Gemini v1beta | Gemini SDK · Coming soon | Use Bearer now; the SDK-default x-goog-api-key is not enabled yet |
videos | Video generation HTTP API | No native SDK badge | Use the HTTP sample for the catalog-listed protocol |
“Coming soon” describes a planned integration path, not current availability. Until P0-9 launches, executable requests must not use x-api-key or x-goog-api-key.
Planned operations
count_tokens and embeddings depend on later delivery stages. This page intentionally provides no executable samples for them. Their OpenAPI operations, model-catalog support, and changelog entries must ship together before use.