You need to enable JavaScript to run this app.
Lake AI Service

Lake AI Service

Copy page
Download PDF
Content Creation
Video Script Planner
Copy page
Download PDF
Video Script Planner

By entering the video topic and creative requirements, you can generate a video production plan for use in subsequent production, including image asset planning, video content structure, shot arrangement, recommendations for video reference materials, duration pacing, and voice-over scripts (does not directly generate audio, video, or text/image assets). The plan breaks down creative ideas into a clear content structure, shot arrangement, asset recommendations, and duration pacing, making it suitable for pre-production planning of educational and marketing videos.

Operator introduction

Operator ID: las_hypervideo_script_planner

Use cases

  • Course instruction: Pre-planning for educational videos such as Chinese poetry reading, English vocabulary explanation, math example explanation, and scientific phenomenon interpretation.
  • Advertising and marketing: ad output, marketing video production, and more.
  • Batch planning: Generate unified production plans for serialized content to reduce repetitive planning work.
  • It is necessary to control the ratio of pure video frames to precise text frames generated, and to restrict scenarios where accurate text is mixed into courseware frames.

Core capabilities

  • From creative concept to production plan: Organize the topic, audience, and expression objectives into an actionable video production plan.
  • Shot and rhythm planning: Break down video content and plan the shot direction, duration, and connection for each part.
  • Suggestions for material usage: Arrange the use of video, images, and other materials as needed for the content to facilitate subsequent production.
  • Audio script: Plan audio elements such as narration, dialogue, and character voices for scenes or storyboard scripts.
  • Support for different content types: Supports planning for course instruction and advertising/marketing videos.
  • Multiple generation modes.
    • Each scene can have three script planning generation modes: video, frame, and hybrid, as follows:
      • video is used for pure video storytelling, character actions, story scenes, environment, emotion, cinematic transitions, and visual demonstrations that do not require precise text rendering.
      • frame is used for accurate rendering of pure text/layout, courseware pages, and charts in visual demonstrations.
      • hybrid is used for scenarios where both video frames and precise text/layout need to be generated within the same scene.
    • video/frame/hybrid routing: Provides an appropriate generation mode for each scene, assigning story context, character actions, and visual demonstrations to video; assigning precise text, formulas, and courseware pages to frame; and assigning scenarios requiring both video and text to hybrid.

Demonstration of results

  • Input: Example of an educational scenario
    "prompt": "为小学三年级数学《长方形面积》课程生成 1 分钟讲解视频规划,要求结构清晰、示例贴近生活。",
    "prompt_strategy": "education_v1",
    "total_duration_sec": 300,
    "planning": {
    "domain": "education",
    "context": {         "target_grade": "小学三年级",
        "subject": "数学",
        "course_topic": "长方形面积"
                }
            }
    
  • Operator output result:
    • Script intent result
      Image
      intent_profile.json
      Unknown size
    • Video production planning result
      Image
      production_plan.json
      Unknown size
  • Video generation can be performed based on the operator output result. The following is an example.
Caution: This operator does not directly output video.

Supported regions

  • Beijing: cn-beijing
  • Shanghai: cn-shanghai
  • Guangzhou: cn-guangzhou

Operator performance

Sub-items
Performance impact description

Maximum RPM

600

Input and output requirements

Input requirements

Breakdown

Detailed requirements

Input data modality

  • Text (Prompt)

Input path requirements

Provide input data to the operator via the request parameter prompt. Input recommendations:

  • Clearly describe the video topic, target audience, expected duration, and information that must be presented. The generated plan will better align with the creative objectives.
  • For course videos, it is recommended to include the grade, subject, and course topic; for marketing videos, specify the product, core selling points, and target audience in the creative requirements.

Output requirements

Breakdown

Detailed requirements

Output data modality

  • Text
  • Other: Each planning task supports a script content duration range from 30 seconds to 30 minutes.

Output path: TOS

You can specify the storage path for the operator's output results via the request parameter output_tos_path. Currently, setting a TOS path is supported.

  • TOS path: Under the same primary account and region as the LAS service, with write permissions on the TOS Bucket directory. Format: tos://bucket/output/.

Billing information
  • Billing standards

    Breakdown
    Description of billing standards

    Billing item

    • Operator processing fees: Usage is calculated based on the target video duration of the output video script, with different unit prices applied for different durations. That is, the longer the target video duration planned in the script, the higher the fee.
    • Multimodal reference input fees (as needed): If multimodal reference input content is provided (such as reference images, reference PDF documents, and so on), a multimodal input fee of 1 CNY will be charged.

    Billing type

    Billed by usage, unit: CNY, invoiced hourly based on actual usage.

    Unit price

    Tiered pricing is applied based on the target video duration required for script planning.

  • Billing details

    Billing item

    Target video duration
    Unit price

    Operator processing fees

    (0 seconds, 30 seconds]

    1.2 CNY

    (30 seconds, 1 minute]

    1.5 CNY

    (1 minute, 2 minutes]

    2.0 CNY

    (2 minutes, 5 minutes]

    3.0 CNY

    (5 minutes, 10 minutes]

    4.5 CNY

    (10 minutes, 20 minutes]

    7.0 CNY

    (20 minutes, 30 minutes]

    9.5 CNY

    Multimodal reference input fees

    Not applicable

    1.00 CNY, charged when multimodal reference input is provided; not charged when multimodal reference input is not provided

Caution and prerequisites

Details

Caution and prerequisites

Costs

Before calling an operator, you need to understand the model invocation costs associated with using the operator. For details, see Large model invocation billing.

Authentication (API Key)

Before calling an operator, you need to generate an API Key for operator invocation. It is recommended to configure the API Key as an environment variable to ensure safer operator calls. For details, see Obtain and configure API Key.

BaseURL

Before calling an operator, you need to determine the BaseURL for operator invocation based on the region where your current LAS service is deployed. This is used to configure the path parameter values for operator calls.
For details, see Obtain the Base URL. The Examples below are for reference only; when making actual calls, replace the path values with those corresponding to your region.

Rest API call

API usage instructions

  • This operator's API is an asynchronous task interface. You need to submit a task through the Submit interface to obtain the task's task_id, and then use the Poll interface to check the status of the corresponding task (task_id) and obtain the operator's result.
  • Caution: After a task is submitted, the task's task_id is valid for three days. After three days, the task_id can no longer be used to obtain the operator's result.

Submit

Interface description

Submit a video script planning task. After successful submission, a task ID is returned. You can obtain the processing result through the query interface.

Request parameters

Parameter
Type
Required
Example value
Description
operator_id
string
Yes
las_hypervideo_script_planner
Operator ID
operator_version
string
Yes
v1
Operator version
data
HyperVideoScriptPlannerReqParams
Yes
Video script planning request parameters

Response parameters

Parameter
Type
Example value
Description
metadata
metadata
Request metadata

Request example

curl --location "${LAS_ENDPOINT}/api/v1/submit" \
--header "Content-Type: application/json" \
--header "Authorization: Bearer $LAS_API_KEY" \
--data '{
    "operator_id": "las_hypervideo_script_planner",
    "operator_version": "v1",
    "data": {
        "prompt": "Generate a 5-minute explainer video plan for the Grade 3 math topic Area of Rectangles. The structure should be clear and examples should be close to daily life.",
        "prompt_strategy": "education_v1",
        "total_duration_sec": 300,
        "planning": {
            "domain": "education",
            "context": {
                "target_grade": "Grade 3",
                "subject": "Math",
                "course_topic": "Area of Rectangles"
            }
        },
        "ref_images": [
            "https://example.com/classroom-reference.png"
        ],
        "ref_files": [
            "https://example.com/course-material.pdf"
        ],
        "output_tos_path": "tos://bucket/output/script_planner/",
        "output_language": "en",
        "aspect_ratio": "16:9",
        "resolution": "1920x1080",
        "fps": 25,
        "video_target_ratio": 0.6,
        "frame_target_ratio": 0.3,
        "hybrid_target_ratio": 0.1,
        "video_max_scene_duration_sec": 8,
        "min_total_duration_sec": 240,
        "max_total_duration_sec": 300
    }
}'

Response example

{
  "metadata": {
    "task_id": "20250108_150000_abc123",
    "task_status": "PENDING",
    "business_code": "0",
    "error_msg": ""
  }
}

Error code

HttpStatusCode

Error code

Error message

Description

400

Parameter.Invalid

The parameter is invalid.

The parameter is invalid (for example, the request parameter format is illegal, planning.domain is not supported, the value range does not meet requirements, and so on)

401

Authorization.Missing

The authorization header is missing.

Authorization is missing

401

ApiKey.Invalid

The api key is invalid.

API Key is invalid

500

Server.InternalError

General Internal Error

Internal server error

Poll

Interface description

Query the execution status and result of the video script planning task.

Request parameters

Name

Type

Required

Example value

Description

operator_id

string

Yes

las_hypervideo_script_planner

Operator ID

operator_version

string

Yes

v1

Operator version

task_id

string

Yes

task-xxx

Task ID

Response parameters

Parameter
Type
Example value
Description
metadata
metadata
Request metadata
data
HyperVideoScriptPlannerResponse
Returned data

Request example

curl --location "https://operator.las.cn-beijing.volces.com/api/v1/poll" \
--header "Content-Type: application/json" \
--header "Authorization: Bearer $LAS_API_KEY" \
--data '{
    "operator_id": "las_hypervideo_script_planner",
    "operator_version": "v1",
    "task_id": "20250108_150000_abc123"
}'

Response example

{
  "metadata": {
    "task_id": "20250108_150000_abc123",
    "task_status": "COMPLETED",
    "submit_time": "2026-07-21T16:04:06+08:00",
    "end_time": "2026-07-21T16:04:06+08:00",
    "business_code": "0",
    "error_msg": ""
  },
  "data": {
    "intent_profile_path": "tos://bucket/out/run/intent_profile.json",
    "intent_profile_uri": "https://example.com/intent_profile.json",
    "production_plan_path": "tos://bucket/out/run/production_plan.json",
    "production_plan_uri": "https://example.com/production_plan.json",
    "total_duration_sec": 300.0,
    "contains_multimodal_input": true
  }
}

Error code

HttpStatusCode

Error code

Error message

Description

400

Parameter.Invalid

The parameter is invalid.

Invalid parameter

400

TaskId.Invalid

The task id is invalid.

Task ID is invalid or the task does not exist

401

Authorization.Missing

The authorization header is missing.

Authorization is missing

401

ApiKey.Invalid

The api key is invalid.

API Key is invalid

500

Server.InternalError

General Internal Error

Internal server error

Reference: Description of output JSON file fields

intent_profile.json

intent_profile.json: Describes the content the user wants, mainly including video title, planning domain, topic, key knowledge points, audience, content objectives, content units, total duration, aspect ratio, resolution, output language, global visual style, text strategy, audio strategy, constraints, and assumptions. Main fields are as follows.

Name

Type

Description

video_title

string

Suggested video title.

planning_domain

string

Identified planning domain; currently supports "education" (教育) and "marketing" (营销).

scenario_type

string

Specific scenario type within the domain, such as classical poetry.

topic

object

Topic information, including main topic, key knowledge points, and classification.

target_audience

object

Target audience information, including age range, cognitive level, attention characteristics, and more.

content_goal

string

Overall content goal for the video.

key_messages

array

Key messages or objectives to be conveyed.

content_units

array

Structured content units, such as formula explanations, operation steps, product selling points, and more.

total_duration_sec

integer

Total planned video duration, in seconds.

aspect_ratio

string

Target video aspect ratio.

resolution

string

Target video resolution.

language

string

Video output language.

global_style

object

Global style, including visual style, text strategy, audio style, and music strategy.

production_plan.json

production_plan.json: Describes how the video is produced downstream, mainly including the following fields.

Name

Type

Description

content_structure

array

Content structure; each item includes chapter ID, name, goal, duration, and recommended generation mode.

generation_mix_strategy

object

Duration ratio strategy for video, frame, or hybrid.

asset_plan

array

List of assets to be generated or reused, such as cover, character reference, background reference, props, style images, frame illustrations, audio reference, and more.

scene_plan

array

Executable scene list; each scene is distinguished by generation_type as video, frame, or hybrid.

assembly_plan

object

Final stitching order, default transitions, transition duration, audio normalization, and background music strategy.

metadata

object

Additional information generated during the planning process.

asset_plan key fields

Name

Type

Description

asset_id

string

Unique asset ID, referenced by scenes via asset_refs.

asset_type

string

Asset type, such as cover, character reference, background reference, prop, style image, frame illustration, or audio reference.

generation_model

string

Recommended asset generation model.

purpose

string

Purpose of the asset in the video.

prompt

string

Prompt used to generate the asset.

negative_prompt

string

Negative prompt used to generate the asset.

uri

string

URI of the provided or generated asset.

metadata

object

Additional information related to the asset.

scene_plan key fields

Name

Type

Description

scene_id

string

Unique scene ID.

section_id

string

Section ID to which it belongs; section planning is in content_structure.

scene_title

string

Scene title.

generation_type

string

Scene generation mode; supports video, frame, or hybrid.

duration_sec

double

Planned scene duration, in seconds.

scene_goal

string

Content objectives to be achieved in the scene.

scene_function

string

Scene function, such as attracting attention, establishing context, explaining, demonstrating, or summarizing.

content_summary

string

Scene content summary.

asset_refs

array

List of asset IDs referenced by the current scene.

storyboards

array

Storyboard list for the video, including storyboard duration, visual prompts, shot design, and storyboard audio.

frame_prompt

object

Visual, text, layout, and animation planning for frame or hybrid scenes.

audio

object

Scene-level audio planning, including audio type, speaking role, timbre, script, and synchronization requirements.

transition

object

Transition requirements for entering and exiting the scene.

Last updated: 2026.09.03 16:28:54