Tencent VOD AIGC Code Helper

Problem it addresses

When integrating Tencent VOD AIGC APIs, the blocker is usually not just “can the call run.” Developers often need to reconcile scattered interface docs, lagging parameter updates, a missing or wrong SubAppId, outdated SDK request classes, async task polling, and unclear billing boundaries. This skill focuses on those engineering details and helps align docs, credentials, sub-app configuration, task state, and cost rules before code is written.

How it works

It organizes the integration workflow around common Tencent VOD AIGC tasks:
- Image/video generation: identify CreateAigcImageTask and CreateAigcVideoTask, note that they are asynchronous, and use the returned TaskId to poll DescribeTaskDetail.
- Custom elements and voices: surface the docs for CreateAigcCustomElement, CreateAigcCustomVoice, CreateAigcAdvancedCustomElement, and CreateAigcSubject.
- Auth and call setup: remind developers to prepare SecretId, SecretKey, and verify the required SubAppId.
- SDK usage: prefer official Python, Go, Java, Node.js, PHP, or .NET SDKs over manually constructing signed HTTP requests.
- Result retrieval: use polling for debugging, and consider HTTP callbacks or CMQ/TDMQ message queues in production.

It also keeps billing risk visible: AIGC image generation, video generation, custom elements, custom voices, and related capabilities may be charged by image count, video duration, training time, or other dimensions, with different pricing for domestic and international accounts.

Boundaries and cautions

This skill is useful for interface selection, workflow clarification, SDK example drafting, and debugging auth or task-status issues. It does not replace official docs as the final source of truth; when parameters differ from the website, check the supplemental docs for the latest fields. Before production calls, confirm cost alerts, spending limits, retry behavior, and concurrency control.