Image, audio, video, and other APIs

The Aikey365 codebase implements multiple non-text routes. Effective availability depends on the selected model, route, and current platform configuration.

Images

POST /v1/images/generations
POST /v1/images/edits
POST /v1/edits

Image billing can use different units from chat models.

Audio

POST /v1/audio/transcriptions
POST /v1/audio/translations
POST /v1/audio/speech

Consider upload size, media format, and client timeouts.

Embeddings

POST /v1/embeddings

Vector dimensions and input limits depend on the model.

Rerank

POST /v1/rerank

Realtime

GET /v1/realtime

Realtime uses WebSocket transport and requires connection lifecycle handling.

Video

POST /v1/video/generations
GET  /v1/video/generations/{task_id}
POST /v1/videos
GET  /v1/videos/{task_id}
GET  /v1/videos/{task_id}/content
POST /v1/videos/{video_id}/remix

Video is typically asynchronous. Preserve task IDs and query task state instead of blindly resubmitting generation requests.

Vendor-specific task routes

The codebase also contains specialized task routes. Treat them as available only when the console, model description, or account configuration explicitly exposes the corresponding capability.