| Setting | Value |
|---|---|
| API base URL | https://ai-api.lightspeedfuture.com unless LSF supplies an account-specific address |
| Authentication | Authorization: Bearer <LSF_API_KEY> |
| Request type | Content-Type: application/json |
| Video create / retrieve | POST /v1/videos GET /v1/videos/{task_id} |
| Balance | GET /v1/billing/balance |
| Speech | POST /v1/audio/speech |
| Assets | Documented /v1/seedance/virtual/... and /v1/seedance/real-human/... paths |
| Model identifiers | Model aliases supplied by LSF. Asset Library requests do not include model. |
Use the LSF request fields in this guide even if your HTTP client supports an OpenAI-compatible style. Use the parameters documented here; other vendors’ fields and SDK defaults may not be supported.
Keep API keys on your application server. Use the creating key while it remains valid. For Production and Flash, a valid replacement key issued for the same LSF organization and account can retrieve an existing task, subject to its current permissions. Retain the original task ID and recover with GET; do not resubmit the old POST under a new key. Request IDs remain scoped to each key, so switching keys can create a separate billable task. Native Draft-to-Final key rotation is described in section 5.8; do not assume these rules apply to every endpoint.
Balance response
GET /v1/billing/balance
Authorization: Bearer <LSF_API_KEY>
{
"object": "billing.balance",
"currency": "USD",
"balance": {
"available": 100.0,
"used": 0.0,
"unlimited": false
},
"updated_at": 1782493727
}
This endpoint reports the available and used allowance associated with the current API key, not a sum of all account keys or an account wallet. Pending reservations affect the displayed allowance; they are not necessarily final charges. For an unlimited key, available is null and unlimited is true. This does not mean the account has unlimited funds. updated_at is the response-generation time in Unix seconds. Pricing and top-ups follow your agreement with LSF.
For accepted Production and Flash tasks, an exhausted key allowance does not by itself prevent retrieval. Disabled, revoked, expired or deleted keys cannot be used; use a valid, authorized replacement key. Existing tasks retain their original billing terms, and reading with a replacement key does not transfer or repeat their charges. New submissions still require sufficient allowance and current product permissions.