Free credits
$5
on signup
Enough session time to connect a real prototype before adding a payment method.
- 50,000 credits
- All public models
- 4 concurrent session
A session is a held GPU, not a request. Credits move only while the runtime is ready and returning live frames.
Choose a model, ready time, and concurrency. The estimate moves on the same unit as the API: session seconds.
Select runtime
Estimated burn
Helios
$0.102
1 × 1 min ready time · 60 session seconds.
Every access mode uses the same ready-time billing model. Capacity changes; the unit does not.
$5
on signup
Enough session time to connect a real prototype before adding a payment method.
$0.0017
per session-second, from
Buy credits and draw them down only while a session is ready. No subscription or seats.
Custom
reserved capacity
For teams shipping interactive video with dedicated capacity and private deployments.
03 · Billing FAQ
These answers mirror the current ready_session_second contract. Rates remain discoverable at the API instead of being hidden in plan fine print.
Billing starts when a session enters ready and stops when it is released or ends. Queued capacity, worker startup, and the documented reconnect grace are excluded. A ready session is billable even when nobody is watching its track.
No. pauseTrack only stops delivery to that connection, and a generation pause can still leave the GPU reserved. Release the owner session when the experience is finished or idle.
Session creation reserves the model rate multiplied by its maximum session ceiling. Concurrent reservations reduce the spendable balance. When a session ends, actual ready seconds settle and the unused reservation returns.
No. One session is metered once regardless of how many authorized guests receive it. Separate concurrent sessions each carry their own meter and credit reservation.
Rates follow the GPU and runtime profile needed to keep each model interactive, not an output-count abstraction. 10,000 credits equal $1; current public rates are also exposed by GET /v1/pricing.
Queue and startup never enter the ready meter. If a ready session fails, it ends and settles against the ready seconds already recorded; the unused reservation returns to the account balance.
During private beta, the published public rate is the ready-session meter. Temporary recordings expire after 24 hours; high-volume exports, dedicated storage, or private delivery are scoped with Reserved scale.
Yes. Approved accounts receive 50,000 credits ($5) on signup, usable across public models. The estimator above shows how many runs fit inside that grant.