How much of the plan is used right now: the number of videos,
automations and clips in the library, generations and renders started
in the last 30 days against their monthly ceiling, storage, credits,
and the per-video duration and render-time caps. since is the start
of the rolling window the counters cover.
Authorization
bearerAuth An API key created under Settings > API & Webhooks. Keys start with sf_live_.
In: header
Response Body
application/json
application/json
curl -X GET "https://example.com/stats"{ "data": { "plan": "pro", "videos": 37, "automations": { "used": 2, "limit": 5 }, "clips": 118, "generations": { "used": 24, "limit": 100, "since": "2026-07-09T11:42:03.000Z" }, "renders": { "used": 19, "limit": 100, "since": "2026-07-09T11:42:03.000Z" }, "storage": { "used": 3187441664, "limit": 21474836480 }, "credits": { "tokens": 42500000, "credits": 42500 }, "maxRenderSeconds": 900, "maxDurationSeconds": 900 }}API info GET
Returns API metadata and the workspace the key resolved to, including its plan, credit balance, plan limits and current usage. This is the cheapest way to verify a key: it reads nothing beyond the workspace the transport already loaded.
Plan, credits and limits GET
The plan snapshot for the connected workspace: the credit balance in both units (1 credit is 1000 tokens), every plan ceiling, and current storage and profile usage. A limit the plan does not cap is `null`, which means unlimited.