Illustrative scenario
Model procurement for a customer-led AI short drama
This illustrative scenario shows a typical procurement process. It does not describe an actual client engagement.
A Singapore studio selects text and video resources for an international short-form drama project, checking access, sample outputs, billing and responsibility for the final edit.
A Singapore studio producing for international audiences
Assume a Singapore creative studio, operating outside mainland China and producing for international audiences, already owns its script drafts, approved reference assets and editing workflow. All production team members using model services are assumed to be outside mainland China. Check their actual countries or territories against each provider's supported locations; being outside mainland China does not by itself establish eligibility. It wants to trial AI-generated material for selected shots, with a project budget owner and an approved data-processing scope. Existing source rights and production approvals must be checked before material is uploaded. Only approved-list services may process the material, with no fallback to an unapproved region. Each shot batch has a budget owner and agreed stop or continuation conditions.
The procurement scope is model resources and agreed integration support. The customer directs the story, reviews material and edits the final work. A resource order is not an order for a completed film, guaranteed character consistency or a fixed number of successful shots.
Separate the text path from the video path
| Path | Candidate families to investigate | Procurement questions |
|---|---|---|
| Text | Qwen, GPT and Kimi | Current official model/version, script, storyboard or subtitle-text sample, access method, processing scope and token billing |
| Video | Seedance and Wan | Current official model/version, accepted input, task handling, supported output and billing unit |
These are candidates, not a confirmed Corebyte supply list. Check the providers' current official catalogues before selecting a model, endpoint or region. A text model understanding video does not establish video generation. Keep script-development usage and video-generation attempts separate so finance can understand what each part bought.
Investigate Qwen and Wan through Alibaba Cloud International Model Studio's Singapore entry point, and Seedance through BytePlus International ModelArk, only where the selected model is available to the actual account. Match model, workspace/region, API endpoint and credential; do not assume a mainland-China account or endpoint can be reused for these international products. GPT and Kimi require their own supported-territory, account and API-product checks.
BytePlus identifies its AP entry region as Johor, Malaysia, and documents possible cross-region inference scheduling. For Model Studio, check the inference deployment scope separately from its Singapore entry point. A Singapore buyer or nearby endpoint does not prove Singapore-only processing. Review the selected service's inference, asset storage, logs and support paths against the approved boundary before uploading; defer the candidate if the boundary cannot be established. See BytePlus region availability.
Decide delivery and ordering conditions independently
For provider-native accounts/APIs, confirm that the Singapore buying entity and actual users are eligible for the selected international service, then confirm account ownership and model/API entitlement. Check Corebyte delivery or resale rights separately. A proposed unified API needs its own actual available-model list and a check of upstream services, version mapping, supported parameters, metering and routing. Its text coverage does not establish video coverage.
For each selected resource, record the agreed version and permitted use, how usage evidence is obtained, and which party handles provider cases. Verify actual account alerts/limits, enforcement delay and in-flight charges before relying on a budget control. Model substitutions and changes of processing route require approval rather than being hidden behind an unchanged interface.
Assign project access and asset approval
Identify the creative owner, resource administrator, operator and reviewer. Store credentials on the authorised server side. Limit access to the project and the approved asset set; a shared production folder should not expose every client's references.
Keep the approval and version of the script, shot brief and reference assets. Confirm which material may be sent to each selected service and what response/log retention applies. Unconfirmed likeness, music or source-material rights remain a customer approval question, not something a model endpoint settles.
Also verify that the asset permissions and the selected model terms allow the intended commercial distribution in the target markets. Hold back assets or outputs while those conditions remain unresolved.
Implement a small, inspectable production path
- Use the selected text route for scripts, shot lists or storyboard descriptions, or to edit, translate and segment subtitle text from existing dialogue or an authorised transcript. The customer approves the text version.
- Prepare only the authorised reference material and requirements for the chosen shot. Verify the selected international video service account's supported inputs, parameters and regional task path.
- Generate a limited sample in the authorised environment and retain task status, usage and the review decision. For asynchronous services, check the documented submission, status and result lifecycle.
- The customer selects material and edits it in the existing workflow. Subtitle timecodes are aligned to the source audio/video using a verified transcription or editing tool and checked by a person. Additional attempts or integration work are reviewed against scope and budget.
The stages have separate acceptance points. Approval of a script does not mean that a generated clip is usable or that the finished edit is complete.
Review samples against the intended shot
Check whether the script and storyboard preserve the intended story and constraints. Review subtitle wording, translation and segmentation against the approved dialogue/transcript; verify timecodes against the source media. A text model is not assumed to produce a reliable timeline or finished edit. For video, review the actual output against the requested shot, reference handling, motion, duration and available audio features, where supported. Treat these as sample criteria, not universal model capabilities or guarantees.
Record accepted, rejected and incomplete attempts with reasons. If a service times out after submission, use the original provider task record before resubmitting. An unknown result needs investigation; it is not automatically free or safe to repeat. Keep creative_project_id, shot_id, attempt_id and provider_task_id associated with the selected model and reference version.
Read the budget as a sequence of attempts
For planning, assume the studio records each shot-batch budget in USD; this is not a quotation. Confirm the supplier's actual billing currency, tax and service-fee treatment, and the exchange-rate basis for internal comparisons. Retain original-currency charges for invoice reconciliation.
Confirm the billing units for text input/output and video separately against the provider’s current terms. A video service may price supported options differently, so record the actual unit and selected output conditions instead of treating every returned clip as equivalent. Include rejected attempts, retries, storage and agreed service charges where applicable.
More attempts may improve the chance of finding suitable material, but also increase review effort and cost. Specify who can approve another batch, a changed reference or a different model. Track the actual budget control behaviour and pending charges. There is no assumed savings rate, production deadline or final-film output in this scenario.
Hand over the resource record and the remaining decisions
A reviewable package includes the selected official catalogue references, agreed model/version and account route, asset approvals, configuration, sample/task records, usage and billing definitions, rejected-output reasons and support ownership. The customer retains creative selection and final editing decisions; Corebyte's agreed work concerns resource procurement, access, integration and handover.
Before authorising the next batch, resolve open supply, region, rights, feature and fee questions. Retain each unresolved item, its owner and the decision to pause or proceed.
Official checks for candidate services: BytePlus video generation, Alibaba Cloud Wan API reference, Model Studio regional API keys and BytePlus international availability. Check the current model catalogue, account eligibility and permitted use before selecting a version; these references do not establish Corebyte supply or customer access.