For APIXO’s wan-3-0-video route, estimate a fixed-duration request from the output seconds and any reference-video seconds. At the published 1080p schema rate of $0.20 per billable second, a ten-second text-to-video or image-to-video output is $2.00. A reference-to-video request with ten output seconds and a five-second video reference is $3.00. Smart duration uses a larger pre-charge and settles successful tasks using actual output length.
These are API calculations, not Studio-credit quotes or measured invoices. The current published schema was checked on October 22, 2026; recheck APIXO API Pricing before submitting.
Wan 3.0 Video example at 1080p: Text-to-video or image-to-video: 10 output seconds
Amount: $2.00
What it means: Fixed-duration estimate
Wan 3.0 Video example at 1080p: 10 output seconds + 5 reference-video seconds
Amount: $3.00
What it means: Fixed-duration estimate
Wan 3.0 Video example at 1080p: Smart duration + 5 reference-video seconds
Amount: $7.00
What it means: Pre-charge, not the final bill
Wan 3.0 Video example at 1080p: That smart task succeeds with 10 output seconds
Amount: $3.00 final; $4.00 difference
What it means: Hypothetical settlement
Reservation is not final cost: Editorial workflow diagram, not a tested model output
Choose the exact model and resolution
The worked examples in this guide use Wan 3.0 Video. Its published schema gives these API rates for text-to-video, image-to-video and reference-to-video:
Output resolution: 480p
USD per billable second: $0.05
Output resolution: 720p
USD per billable second: $0.10
Output resolution: 1080p
USD per billable second: $0.20
Video LoRA and Pro LoRA have their own rate tables and output tiers. Before changing routes, check the three-route comparison and the selected route’s current billing rules. The dollar examples here apply to standard Wan 3.0 Video.
The figures are in US dollars for API usage. Studio monthly credits are a separate allowance. If the pricing page and another source disagree, resolve the selected route’s rate before quoting or submitting a task rather than mixing values.
Add video inputs to billable seconds
For a positive fixed duration:
Text-to-video or image-to-video:
estimated cost = requested output seconds × unit rate
Reference-to-video:
estimated cost = (total reference-video seconds + requested output seconds) × unit rate
Add the actual durations of all video inputs, not the number of files or just the longest clip. A filename containing “five seconds” is not a duration measurement.
Images, reference audio, files and links are not billed separately on standard Wan 3.0 Video. A reference-to-video request with no video input still needs at least one other supported reference; no reference video does not mean no references. With zero video-input seconds, the formula reduces to output seconds × rate. Use the reference-input workflow to choose a valid set of materials.
Check the fixed-duration allowance before calculating a quote
The route accepts whole-second fixed output durations from 2 through 30. With reference video, fixed output seconds plus total reference-video seconds cannot exceed 30. Video input also has its own limit: up to five clips, each 1–15 seconds, totaling at most fifteen seconds.
Planned request: Text-to-video or image-to-video: 10-second output
Fixed-duration check: Within the duration limit
Standard Video 1080p estimate: 10 × $0.20 = $2.00
Planned request: 10-second output, 5-second video input
Fixed-duration check: 10 + 5 ≤ 30
Standard Video 1080p estimate: 15 × $0.20 = $3.00
Planned request: 20-second output, 10-second video input
Fixed-duration check: 20 + 10 = 30
Standard Video 1080p estimate: 30 × $0.20 = $6.00
Planned request: 20-second output, 15-second video input
Fixed-duration check: 35 seconds: exceeds the combined limit
Standard Video 1080p estimate: Shorten the output or references before submitting
Audio has a separate fifteen-second total input limit. Do not add audio seconds to the video-duration formula.
Trim a reference to the movement you need, keeping the original and trimmed files. Shortening it can reduce input cost, but also removes information that may matter to the result.
Separate smart-duration pre-charge from final cost
With duration=-1, the output length is unknown when the request starts. The published rule pre-charges thirty output seconds plus any reference-video seconds:
Pre-charge = (reference-video seconds + 30) × unit rate
After success:
final charge = (reference-video seconds + actual output seconds) × unit rate
For five seconds of reference video at $0.20 per second, the pre-charge is (5 + 30) × $0.20 = $7.00. If the successful output lasts ten seconds, the final charge is (5 + 10) × $0.20 = $3.00, and the difference is $4.00.
The $4.00 difference is refunded on this hypothetical successful settlement. Ten seconds is an assumption, not a promised smart-duration result. The $7.00 pre-charge reserves 35 billable seconds; it does not authorize a fixed request with 35 combined input/output seconds or promise a 30-second smart output.
Budget for the amount needed to start the task. A lower expected final charge does not mean that the balance required for submission is equally low. Failure, cancellation and exceptional-task handling need their applicable platform rules; this successful-settlement formula does not establish those policies.
Verify settlement and record every attempt
On a successful smart-duration task, confirm data.billing.settlementState is final, then inspect inputVideoSeconds, outputVideoSeconds and totalBillableSeconds alongside the actual charge. Do not record a processing task’s pre-charge as its final consumption. See the Wan 3.0 Video API documentation for response details.
Keep one record for each attempt:
Record: Model, mode and resolution
Why it matters: Identifies the applicable rate and input rules
Record: Reference-video seconds and requested duration
Why it matters: Explains the initial estimate or pre-charge
Record: Final billable seconds and actual charge
Why it matters: Separates settlement from reservation
Record: Accepted footage and reason for retry
Why it matters: Connects API spend to usable output
For a finished piece, divide the total cost of all relevant attempts by the seconds you actually accept. If no footage is usable, record the spend and zero accepted seconds; cost per usable second is undefined, not zero. A successful task is not automatically usable footage, and retries belong in the production budget.
Choose fixed or smart duration for the job
Use fixed duration when you need an advance quote or a specific edit length, after checking the reference-video allowance. Use smart duration when exploring pacing and when the budget can accommodate the pre-charge. Neither choice guarantees an acceptable clip on the first attempt.
Open Wan 3.0 Video with the model, resolution and duration already chosen. Keep the selected rate, request settings and actual bill together so the next estimate starts from evidence.
Build with APIXO
Explore image, video, and audio models in one place.
