p-video-avatar API
p-video-avatar from PrunaAI is listed for video tasks. Duration, resolution, frame rate and any image conditioning must be checked together with the native price.
PreparingService type
Sale prices will appear after provider configuration is complete.
- API model ID
- di-prunaaip-video-avatar-07904fc804
- Model developer
- PrunaAI
- Service type
- Video
- Current availability
- Preparing
- Catalogue task
- Video generation
- Native billing basis
- Output duration
Model features
No additional gateway capabilities have been confirmed for this model.
What is p-video-avatar?
Use the public identifier di-prunaaip-video-avatar-07904fc804 for p-video-avatar in ServerNet. The gateway uses this identifier to select the configured route; the developer is PrunaAI.
Where to use p-video-avatar
- Check the exact video task supported by p-video-avatar.
- 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.
Image, audio, video and other native services can use different billing units. A token tariff is not a valid substitute. Sale opens only after the execution path and bounded billing contract are verified.
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 |
|---|---|---|---|
image | string | Yes | |
audio | string | No | |
voice | string | No | Values: Zephyr (Female), Puck (Male), Charon (Male), Kore (Female), Fenrir (Male), Leda (Female), Orus (Male), Aoede (Female), Callirrhoe (Female), Autonoe (Female), Enceladus (Male), Iapetus (Male), Umbriel (Male), Algenib (Male), Despina (Female), Erinome (Female), Laomedeia (Female), Achernar (Female), Algieba (Male), Schedar (Male), Gacrux (Female), Pulcherrima (Female), Achird (Male), Zubenelgenubi (Male)
|
resolution | string | No | Values: 720p, 1080p
|
seed | integer | No |
Frequently asked questions
Is p-video-avatar available through ServerNet?
p-video-avatar is currently unavailable for API use. A catalogue listing does not activate billing or access. Choose an available related model or check this page again after the route is verified.
Which model ID and API endpoint should I use for p-video-avatar?
This model needs a native execution route. A chat, embedding or reranking example would not execute the advertised task. Its public page remains a catalogue reference until the route and metering are ready.
How is p-video-avatar usage charged?
Image, audio, video and other native services can use different billing units. A token tariff is not a valid substitute. Sale opens only after the execution path and bounded billing contract are verified.
What should I check before using p-video-avatar 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.