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.
Audio
OpenAI-compatible audio endpoints:
| Endpoint | Use for |
|---|---|
POST /v1/audio/speech | Text-to-speech audio bytes |
POST /v1/audio/transcriptions | Whisper-compatible speech-to-text |
POST /v1/audio/translations | Translate audio to English |
Images
Image generation and edit endpoints:
| Endpoint | Use for |
|---|---|
POST /v1/images/generations | Generate images from text |
POST /v1/images/edits | Edit an input image |
Videos
Async video generation job endpoints:
| Endpoint | Use for |
|---|---|
POST /v1/videos | Create a video generation job |
GET /v1/videos | List video jobs |
GET /v1/videos/:id | Retrieve 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.
/v1/chat/completions// Press Send to run a live request