Zeligate VoiceDeveloper docs
v1.3.0Sign in

API reference / Models

Models

There is one engine — Zeli Turbo. The models endpoint exists so that a hard-coded model_id from a previous integration resolves, and model_id in a request body is accepted and ignored.

List models

GET/v1/models

Returns the ZeliSpeech-shaped model list. Any model_id you send on a synthesis request is recorded and echoed but never changes the engine.

curl "https://voice.your-domain.com/v1/models" -H "Authorization: Bearer sk-zeli-..."
Why it exists

Migrating clients often hard-code a model_id from a previous integration. Keeping a models list means those calls succeed without edits — the list returns a single zeli-turbo entry, and any value simply maps to Zeli Turbo.

Account & quota

GET/v1/user
GET/v1/user/subscription

Return standard account / subscription objects as a stub, so client code that reads the user or checks quota on startup doesn't break. There is no real metering or credit accounting yet — a self-hosted box has no quota.

curl "https://voice.your-domain.com/v1/user/subscription" -H "Authorization: Bearer sk-zeli-..."
On the roadmap

Real metering (usage → credits) that populates /v1/user* is a standalone-platform item, alongside per-key concurrency and API-key management.

Zeligate Voice API · self-hosted · secure data sovereignty · source