Pixverse-T2V-HD API
Pixverse-T2V-HD from Pixverse is listed for video tasks. Duration, resolution, frame rate and any image conditioning must be checked together with the native price.
AvailableService type
1 Model-defined image units · Final price depends on dimensions, quantity and request options.
The usage rate is fixed at request admission. Reported consumption determines the final usage amount.
- API model ID
- di-pixversepixverse-t2v-hd-ab2fe655cd
- Model developer
- Pixverse
- Service type
- Video
- Current availability
- Available
- Catalogue task
- Video generation
- Native billing basis
- Model-defined image units
Model features
No additional gateway capabilities have been confirmed for this model.
What is Pixverse-T2V-HD?
Use the public identifier di-pixversepixverse-t2v-hd-ab2fe655cd for Pixverse-T2V-HD in ServerNet. The gateway uses this identifier to select the configured route; the developer is Pixverse.
Where to use Pixverse-T2V-HD
- Check the exact video task supported by Pixverse-T2V-HD.
- Evaluate a short clip before a longer generation.
- Compare cost and visual consistency at the resolution you plan to use.
Build your integration
Video tasks require a bounded native request and a delivery contract for the output. Asynchronous status and billing must be verified before the model is opened for sale.
Inputs and service limits
Do not infer a video tariff from a chat token price. Longer clips, extra frames and higher resolutions can increase cost. The catalogue listing alone does not enable generation.
A bounded request cost is reserved before sending. The verified tariff or reported provider cost is settled using the exchange rate and sale markup. Media is not billed as chat tokens. Use Data URLs for valid images, PCM WAV audio, or H.264 MP4 video on routes that accept video input.
Model-specific native inputs
Input schema snapshot: 2026-10-10. The current gateway execution status is shown above. These catalogue fields help you evaluate the native model; accepted gateway requests are documented in the integration section.
| Parameter | Type | Required | Declared constraints |
|---|---|---|---|
aspect_ratio | string | No | Default: 16:9
Values: 16:9, 4:3, 1:1, 3:4, 9:16
|
duration | integer | No | Default: 5
Values: 5, 8
|
prompt | string | Yes | Maximum length: 2048
|
negative_prompt | string | No | Maximum length: 2048
|
seed | integer | No | Minimum: 0
Maximum: 2147483647
|
Connect to Pixverse-T2V-HD API
Enable ai:native on your key and ai:models:read to check availability. Set SERVERNET_API_KEY in your server environment. Change the idempotency key for each new request; keep it unchanged only for an identical retry.
curl https://servernet.cloud/v1/inference \
-H "Authorization: Bearer $SERVERNET_API_KEY" \
-H 'Content-Type: application/json' \
-H 'Idempotency-Key: CHANGE_FOR_EACH_NEW_REQUEST' \
-d '{
"model": "di-pixversepixverse-t2v-hd-ab2fe655cd",
"duration": 5,
"prompt": "A hand with delicate fingers picks up a bright yellow lemon from a wooden bowl filled with lemons and sprigs of mint against a peach-colored background. The hand gently tosses the lemon up and catches it, showcasing its smooth texture. A beige string bag sits beside the bowl, adding a rustic touch to the scene. Additional lemons, one halved, are scattered around the base of the bowl. The even lighting enhances the vibrant colors and creates a fresh, inviting atmosphere."
}'
Use the same Idempotency-Key when retrying an identical request. Successful responses are replayed without a second charge for 24 hours. Do not automatically retry when x-should-retry:false is present. The key is shown once. Store it in a server environment variable. Keep it out of browser code, GitHub and logs.
Keys, budgets and usage reportsFrequently asked questions
Is Pixverse-T2V-HD available through ServerNet?
Pixverse-T2V-HD is currently available on the configured route. Check GET /v1/models before sending a request: availability can change with provider capacity, catalogue freshness or account configuration.
Which model ID and API endpoint should I use for Pixverse-T2V-HD?
Create a key with ai:native and send this page’s example to /v1/inference. Video and music return a 202 receipt and a result polling URL.
How is Pixverse-T2V-HD usage charged?
A bounded request cost is reserved before sending. The verified tariff or reported provider cost is settled using the exchange rate and sale markup. Media is not billed as chat tokens. Use Data URLs for valid images, PCM WAV audio, or H.264 MP4 video on routes that accept video input.
What should I check before using Pixverse-T2V-HD in production?
Do not infer a video tariff from a chat token price. Longer clips, extra frames and higher resolutions can increase cost. The catalogue listing alone does not enable generation.