Lightning v2 and Lightning Large endpoints retired - 410 Gone with v3.1 migration pointer

The underlying inference pools for Lightning v2 and Lightning Large have been retired. Calls to these endpoints now return a fast 410 Gone with a migration pointer to Lightning v3.1.

Endpoint	Before	After
`POST /waves/v1/lightning-v2/*`	5xx after timeout	410 `MODEL_DEPRECATED` → use `lightning-v3.1`
`POST /waves/v1/lightning-large/*`	5xx after timeout	410 `MODEL_DEPRECATED` → use `lightning-v3.1`
`POST /waves/v1/prof-voice-cloning/*`	5xx after timeout	410 `MODEL_DEPRECATED` → use `/waves/v1/voice-cloning` (v3.1)
`POST /waves/v1/voice-cloning` (`model=v2`)	served via lightning-large	400 - Voice cloning for lightning-v2 is deprecated; use lightning-v3.1
`POST /waves/v1/voice-cloning` (no `model`)	defaulted to v2 → dead queue	defaults to v3.1, served
`POST /waves/v1/voice-cloning` (`model=v3.1`)	served	served (no change)

Response shape on the deprecated endpoints:

{
  "status": "error",
  "error_code": "MODEL_DEPRECATED",
  "message": "This model is retired. Please migrate to lightning-v3.1 via /waves/v1/lightning-v3.1/get_speech.",
  "recommended_endpoint": "/waves/v1/lightning-v3.1/get_speech"
}

Migration: replace any lightning-v2 or lightning-large calls with the equivalent lightning-v3.1 endpoint. Voice cloning with no model parameter now routes to v3.1 automatically - no client change needed for that case.

Not affected (so v3.1 voice cloning keeps working): lightning-v3.1/get_speech, voice-cloning clone-creation with v3.1, and the unified /tts and /tts/live routes.

Lightning v3.1 Pro - 35 new voices added to the catalog

35 new voices have been added to the Lightning v3.1 Pro voice catalog. They’re available immediately to any org with Lightning v3.1 Pro access.

curl -X POST "https://api.smallest.ai/waves/v1/tts" \
  -H "Authorization: Bearer $SMALLEST_API_KEY" \
  -H "Accept: audio/wav" \
  -d '{"text": "Hello.", "voice_id": "<new-voice-id>", "model": "lightning_v3.1_pro", "sample_rate": 24000}'

What’s in this batch:

All 35 voices are routed through the standard Lightning v3.1 pipeline.
They’re also auto-promoted to the multimodel registry, so they remain available if you switch your model parameter later.
The full updated voice list is available via the Get Voices endpoint - filter to model=lightning_v3.1_pro to see only the Pro catalog.

Migration: no action - additive change, existing voices unchanged.