Wan 2.7 is Alibaba's Tongyi Wanxiang video-and-image family. On HiAPI it runs through one unified /v1/tasks API across three endpoints — text-to-video, image-to-video, and text-to-image — and every one is billed pay-as-you-go: per second for video, per image for stills. No subscription, no seat license, no per-token math. This guide breaks down the real 2026 numbers (re-checked against HiAPI's live pricing on 2026-10-17), shows what a clip actually costs, and gives you a way to estimate and cap Wan 2.7 spend before you scale it.
Wan 2.7 API pricing at a glance (2026)
All figures are in USD. Video is billed by the second; images are billed per successful render. See live pricing for the current numbers.
| Endpoint | How it bills | Price |
|---|---|---|
| Text-to-video | per second | $0.10/s at 720P · $0.167/s at 1080P |
| Image-to-video | per second | $0.10/s at 720P · $0.167/s at 1080P |
| Text-to-image | per image | $0.08 flat (up to 4K) |
That is the whole list. Video has exactly two price points — set by resolution, not by prompt, audio, or reference inputs — and text-to-image is a single flat rate regardless of output size. Failed tasks are not charged, so retries on a timeout or a rejected prompt cost nothing.
How video is billed: per second, by resolution
Both video endpoints price the same way, and only resolution moves the number:
- 720P — $0.10 per second. The default working tier for drafts, social cuts, and any clip you will iterate on.
- 1080P — $0.167 per second. Reach for it on final delivery, hero clips, and anything a viewer watches full-screen.
Clip length is the other half of the bill. Wan 2.7 clips run 2 to 15 seconds, and you pay for the length you request. So the formula is simply seconds × rate:
| Clip length | 720P ($0.10/s) | 1080P ($0.167/s) |
|---|---|---|
| 5 seconds | $0.50 | $0.84 |
| 10 seconds | $1.00 | $1.67 |
| 15 seconds | $1.50 | $2.51 |
The jump from 720P to 1080P adds about two-thirds to every clip. That is the single biggest cost lever you control, which is why the practical workflow is to lock your prompt and motion at 720P, then re-render only the keeper at 1080P.
What a second of Wan 2.7 actually buys
Per-second pricing is abstract until you watch what a second contains. Here is a Wan 2.7 text-to-video preview at 1080P with native audio — the tier billed at $0.167 per second:
A 1080P second like this costs about 17 cents; the same shot at 720P costs a dime. For a 6-second product loop that is roughly $0.60 at 720P or $1.00 at 1080P — cheap enough to generate a dozen variations and keep the best, which is exactly how you should budget it.
Image generation: a flat $0.08 per image
Wan 2.7's text-to-image endpoint (marketed as Wan 2.7 Image Pro) is priced completely differently from the video side: one flat $0.08 per image, with no resolution tier and no surcharge up to 4K. Strong prompt adherence and clean in-image text are its selling points, and because a 1K draft and a 4K final cost the same eight cents, there is no reason to iterate at low resolution — render at the size you actually need from the start.
At $0.08 flat, every dollar buys 12 images and ten dollars buys 125 — predictable enough that a batch job's cost is just image count × $0.08.
What $1 and $10 buy
Putting video and image buying power side by side:
| Spend | 720P video | 1080P video | Text-to-image |
|---|---|---|---|
| $1 | 10 seconds | ~6 seconds | 12 images |
| $10 | 100 seconds | ~59 seconds | 125 images |
New accounts start with free credits, so your first test clips and images cost nothing out of pocket.
Per-call billing vs direct access
The structural point matters more than any single number: Wan 2.7 on HiAPI is pure pay-as-you-go. You pay for successful calls and nothing else — no monthly minimum, no subscription tier to grow into, and one API key covers all three endpoints plus the rest of HiAPI's models.
The alternatives carry different shapes of cost. Standing up the open weights yourself means renting GPUs and paying for idle time, cold starts, and ops — which only pencils out at very high, steady volume. First-party or direct access means a separate account and separate billing per provider, with terms that vary by region and change often. We do not publish a line-by-line comparison against those, because the honest answer is "it depends on your volume and where you run it." What is fixed and verifiable here is the structure: metered per second or per image, failed tasks free, no commitment.
How to estimate and control cost at scale
A few levers do most of the work:
- Draft at 720P, finalize at 1080P. You pay a dime a second to explore and 17 cents only on the take you keep — a ~40% saving on everything you discard.
- Request the duration you need, not the max. Every second is billed. Trimming a 15-second plan to the 8 seconds you will actually use cuts that clip's cost by nearly half.
- Batch images at final resolution. Since text-to-image is $0.08 whether it is 1K or 4K, render once at delivery size instead of a cheap pass plus a re-run.
- Let retries be free. Failed tasks are not billed, so a timeout or a policy rejection does not cost you — build retry logic without worrying about double charges.
- Model the bill before you run it. Video cost is seconds × rate × clips; image cost is count × $0.08. Plug in your volume and you have a hard number. For a cross-model view of the same tactics, see Controlling AI Image and Video API Costs.
How to access Wan 2.7 on HiAPI
One API key covers all three endpoints. Image and video models run on the async task endpoint: POST /v1/tasks returns a taskId, you poll GET /v1/tasks/{taskId} until status is success (or pass a callback.url to be notified), then download the result. Pay-as-you-go, no minimum, and failed tasks are not charged.
This piece is about cost, so it stops at the billing shape. For the full request bodies — the media array for first/last frames, uppercase 720P/1080P resolution, and the ratio field — follow the copy-paste curl and Python in the Wan 2.7 API guide, with the complete parameter reference in the HiAPI docs.
FAQ
How much does the Wan 2.7 API cost? On HiAPI, video (both text-to-video and image-to-video) is $0.10 per second at 720P and $0.167 per second at 1080P, for clips of 2–15 seconds. Text-to-image is a flat $0.08 per image up to 4K. There is no subscription and no per-token billing.
Is Wan 2.7 video billed per clip or per second? Per second. You are charged seconds × the resolution rate, so a 10-second 720P clip is $1.00 and the same clip at 1080P is $1.67. Clip length can be anywhere from 2 to 15 seconds.
Does 1080P cost more than 720P? Yes — $0.167 per second versus $0.10, about two-thirds more. Iterate at 720P and switch to 1080P only for the final render to keep spend down.
Is there a cheaper way to use Wan 2.7? Stay at 720P while you iterate, request only the seconds you need, and lean on the free retries (failed tasks are not billed). If you only need stills, the flat $0.08 text-to-image rate is often cheaper per deliverable than a short video.
Do I pay for failed generations? No. Only successful tasks are billed, so timeouts, rejected prompts, and retries cost nothing.
Takeaways
Wan 2.7 is simple to budget once you separate the two billing models. Video is seconds × rate: $0.10/s at 720P, $0.167/s at 1080P, for 2–15-second clips — so the resolution tier and the duration you request are your two cost dials. Images are a flat $0.08 each up to 4K, which makes batch jobs trivial to price. Draft cheap at 720P, finalize at 1080P, trim every second you do not need, and let the free retries absorb your failures.
Ready to put a real number on your workload? New keys come with free credits — open the Wan 2.7 model page and run your first clip today.
