![]()
HeyGen Avatar 6 API pricing on PoYo is per second of output video, with four rates: two models (heygen-avatar-6 and heygen-avatar-6-turbo) times two resolutions (1080p and 2K). This page lists the rates, explains what is and is not billed, and works through real request shapes. Rates can also be checked on the HeyGen Avatar 6 model page.
HeyGen Avatar 6 API price on PoYo
1 credit = $0.005. All rates are per second of output.
| Model ID | Resolution | Credits per second | USD per second | USD per minute |
|---|---|---|---|---|
heygen-avatar-6-turbo | 1080p | 10 | $0.05 | $3.00 |
heygen-avatar-6-turbo | 2K | 18 | $0.09 | $5.40 |
heygen-avatar-6 | 1080p | 20 | $0.10 | $6.00 |
heygen-avatar-6 | 2K | 29 | $0.145 | $8.70 |
Three ratios fall out of the table:
- Turbo vs Avatar 6 at 1080p: Turbo is exactly half (10 vs 20 credits).
- Turbo vs Avatar 6 at 2K: Turbo is 18 / 29 = 62% of the price, a 38% saving.
- 2K premium: +45% on Avatar 6 (29 vs 20), +80% on Turbo (18 vs 10). Turbo at 2K (18) still costs less than Avatar 6 at 1080p (20).
The input mode does not change the rate. A photo, a reference video, or a public avatar costs the same per output second at the same model and resolution.
What is billed and what is not
The billable unit is whole seconds of output, rounded up. When the seconds are counted depends on how the speech arrives:
| Request | Billed seconds | When it is charged |
|---|---|---|
Photo mode (image_urls + audio_url) | Audio length, rounded up | At submission |
Reference video mode (video_url + audio_url) | Audio length, rounded up | At submission |
Public avatar + audio_url | Audio length, rounded up | At submission |
Public avatar + text | Finished video length, rounded up | Credits reserved at submission, settled when the task ends |
Not billed as separate line items: the prompt, the choice of avatar or voice, the aspect_ratio, and the optional reference photo in reference video mode. PoYo validates audio length, reference video length, and the avatar name at submission, so a request rejected with a 400 never starts a task. A finished video can be about a tenth of a second shorter than its audio; billing follows the rounded-up audio length, not that small difference.
Worked cost examples
1. A 30-second explainer from a recorded voice-over
Photo mode, a 29.4-second MP3. Billed as 30 seconds.
| Model / resolution | Credits | USD |
|---|---|---|
| Turbo 1080p | 300 | $1.50 |
| Turbo 2K | 540 | $2.70 |
| Avatar 6 1080p | 600 | $3.00 |
| Avatar 6 2K | 870 | $4.35 |
2. Our launch-day text tests
Public avatar mode with text, 16:9, 1080p, run by the PoYo team on the production API on November 19, 2026:
| Model | Script | Output | Billed seconds | Cost at current prices |
|---|---|---|---|---|
heygen-avatar-6-turbo | 27 words, Abigail Office Front, voice Jessica Anne Bogart | 10.16 s | 11 | 110 credits ($0.55) |
heygen-avatar-6 | 21 words, Bryan Tech Expert, voice Andrew | 6.88 s | 7 | 140 credits ($0.70) |
Rounding is visible here: 10.16 s became 11 billed seconds. For short clips, the rounded-up fraction is a larger share of the bill, so keep scripts tight rather than padding them.
3. A batch of 200 sales videos, 20 seconds each
4,000 output seconds in total, if each clip uses a 20-second recording:
| Model / resolution | Credits | USD |
|---|---|---|
| Turbo 1080p | 40,000 | $200 |
| Avatar 6 1080p | 80,000 | $400 |
| Avatar 6 2K | 116,000 | $580 |
A common pattern is to render drafts on Turbo, get approval, and re-render only the approved cut on Avatar 6. The routing logic is in HeyGen Avatar 6 API vs Turbo.
Credit reservations for text tasks
Text requests reserve credits up front, before the reading time is known, and settle to the actual seconds when the task finishes. In our launch-day test, a third request (Turbo, 2K, 22 words) was rejected after two earlier text tasks had been submitted. The response was HTTP 200 with body code 402 and type insufficient_credits_error, and the message read: "this request needs at least 252 credits, and 344 credits are already reserved by your unfinished HeyGen Avatar 6 text tasks."
Two practical rules follow:
- Size your balance for the reservations of every text task in flight, not just the expected final bill.
- Treat
code402 as "wait or top up", not as a permanent failure. Credits held by a finished task are settled, so the same request can succeed later.
Audio requests do not need a reservation: the length is known from the file, and the charge is taken once at submission.
How HeyGen Avatar 6 API pricing compares with other talking-avatar models on PoYo
| Model on PoYo | Rate per second | Notes |
|---|---|---|
kling-avatar-2.0/standard | 7 credits ($0.035) | Photo + audio only |
heygen-avatar-6-turbo 1080p | 10 credits ($0.05) | All three HeyGen modes |
kling-avatar-2.0/pro | 14 credits ($0.07) | Photo + audio only |
heygen-avatar-6-turbo 2K | 18 credits ($0.09) | |
heygen-avatar-6 1080p | 20 credits ($0.10) | |
omnihuman-2.0 720p | 21 credits ($0.105) | 4–300 s audio |
heygen-avatar-6 2K | 29 credits ($0.145) |
Field-by-field differences are in HeyGen Avatar 6 API vs Kling Avatar 2.0.
Frequently asked questions
How much does the HeyGen Avatar 6 API cost per second?
On PoYo: Turbo $0.05 (1080p) or $0.09 (2K); Avatar 6 $0.10 (1080p) or $0.145 (2K). That is 10, 18, 20, and 29 credits per second.
Is a HeyGen Avatar 6 API video billed by audio length or video length?
With audio_url, by the audio length, rounded up, at submission. With text, by the finished video length, rounded up, after credits are reserved at submission.
Does 2K cost more on the HeyGen Avatar 6 API?
Yes: 45% more on Avatar 6 (29 vs 20 credits per second) and 80% more on Turbo (18 vs 10).
Why did I get a 402 with enough credits for the final video?
Running text tasks hold reserved credits until they settle. The error message states how many credits the new request needs and how many are reserved.
Is there a subscription for the HeyGen Avatar 6 API on PoYo?
No. You pay per generated second from a credit balance, using the same PoYo key as the HeyGen Avatar 6 API guide.