AIHubMix API Documentation and Developer Resources
AIHubMix OpenAPI specification, authentication, model discovery and agent onboarding resources.
Start an integration
Create an API key in the AIHubMix console and store it in an environment variable. Choose a real model ID from the public catalog, read its capabilities and integration guide, then use the wire protocol supported by your SDK. Chat Completions and Responses use Authorization: Bearer; Messages uses x-api-key; Gemini uses x-goog-api-key. Check the response body as well as the status code when verifying your first call. Never embed API keys in frontend code or public repositories.
Free models and testing
The free model catalog publishes current availability and model limits. Access can depend on your account and key settings. The Playground provides an interactive way to try models; review the selected model pricing before sending requests. The console offers self-service key management. These resources do not imply an isolated public sandbox or guaranteed trial credits.
Errors and retries
For API error formats and trace IDs, use the HTTP status documentation linked below. On 429, honor Retry-After when supplied; it can be a delay in seconds or an HTTP date. Otherwise use bounded exponential backoff with jitter. Rate-limit headers, when present, come from the API gateway. Do not assume that missing quota headers mean unlimited capacity. Avoid blindly replaying generation requests after ambiguous failures, because a request may already have incurred usage.
API versions and model retirement
Use the exact versioned paths declared by the OpenAPI specification, including /v1 and the Gemini /gemini/v1beta endpoints. API versioning and model lifecycle are separate: a versioned endpoint can remain available while a particular model is retired. Read the model retirement index and model guide for announced retirement dates and successors. An id removed from the website catalog may return 410 Gone. No fixed API deprecation notice period is promised here; confirm migration requirements with support before relying on one.