Are you an LLM? Read llms.txt for a summary of the docs, or llms-full.txt for the full context.
Skip to content

API Explorer

Pick an operation, paste your Lazu API key, and send a real request against the live API. Requests go straight from your browser to api.lazu.ai — your key stays in this tab (and is only persisted if you tick Remember).

The embedded explorer below covers the most common JSON operations. For the complete contract, including binary upload/download APIs and provider-native paths, use the generated openapi.json or openapi.yaml assets shipped with the docs build.

Compatibility matrix

"OpenAI-compatible" describes the supported request and response shapes; it does not mean every OpenAI product endpoint exists. Unsupported routes return HTTP 501 with an OpenAI-style error envelope.

CapabilityStatusRoutes
Chat and legacy completionsSupportedPOST /v1/chat/completions, POST /v1/completions
ResponsesSupportedPOST /v1/responses
Embeddings and rerankSupportedPOST /v1/embeddings, POST /v1/rerank
ImagesPartialGenerations and edits are supported; variations are not
AudioSupportedSpeech, transcription, and translation
Files and modelsSupportedFile lifecycle and model list/retrieve
Realtime, Anthropic, GeminiProvider-dependentWebSocket and native provider routes require a capable configured channel
Fine-tuning and model deletionNot implementedFine-tune routes and DELETE /v1/models/:model return 501

Long-running interactive inference should use streaming. Work that can remain silent for many minutes should use an asynchronous job endpoint and polling instead of relying on an indefinitely idle HTTP connection.

Audio

OpenAI-compatible audio endpoints:

EndpointUse for
POST /v1/audio/speechText-to-speech audio bytes
POST /v1/audio/transcriptionsWhisper-compatible speech-to-text
POST /v1/audio/translationsTranslate audio to English

Images

Image generation and edit endpoints:

EndpointUse for
POST /v1/images/generationsGenerate images from text
POST /v1/images/editsEdit an input image

Videos

Async video generation job endpoints:

EndpointUse for
POST /v1/videosCreate a video generation job
GET /v1/videosList video jobs
GET /v1/videos/:idRetrieve a video job

Anthropic

Anthropic-native requests use POST /v1/messages with x-api-key and anthropic-version headers. Model availability is still scoped by the active Lazu API key; check Model catalog before calling native provider paths.

Gemini

Gemini-native requests use POST /v1beta/models/{model}:generateContent. API keys can be supplied through the OpenAI-compatible bearer header, ?key=..., or x-goog-api-key.

Operations
POST/v1/chat/completions
Response
// Press Send to run a live request