Sales Talking Video

Create a product-selling video from prompt and product image references. Call it via REST API or MCP, or try it in the online playground.

CostEst. 1040–1248 credits / call

Try online

POST · https://api.nexscope.ai/ai/salesTalkingVideoMCP · nexscope_sales_talking_video

Subscription required. Creative AI APIs are available only to users with an active subscription. Trial credits do not enable API key access. View subscription plans.

Multimodal AI

What this API does

Create a product-selling video from prompt and product image references. The request accepts prompt, imageList, videoType, videoTime, aspectRatio. Generation runs as a task: retain the task ID and retrieve the completed result before using the output.

Sales Talking Video API use cases

Draft a product video

To draft a product video, a content editor submits prompt and imageList to Sales Talking Video. The returned completed generation results help review a video concept before campaign production.

Prepare campaign video variants

A content editor uses Sales Talking Video with prompt and imageList to prepare campaign video variants. The returned completed generation results help compare clips created for different campaign briefs.

Review generated footage for a listing

For this workflow, a content editor calls Sales Talking Video with prompt and imageList to review generated footage for a listing. The result helps choose footage suitable for the product listing.

Sales Talking Video API FAQ

What does the Sales Talking Video API return?

Create a product-selling video from prompt and product image references. It corresponds to the supplied prompt, imageList, videoType, videoTime, aspectRatio. The initial response can contain a task ID and status; the completed task result contains the generated output. Example values illustrate the response shape, rather than live account results.

How many credits does the Sales Talking Video API cost?

The current documented cost is Est. 1040–1248 credits / call. This is the same cost shown at the top of this page. If a range or estimate is displayed, the final charge depends on the request. Review your available credits and the pricing page before calling the API, and check API usage records for the actual charge.

How do I call the Sales Talking Video API from my app or an MCP client?

Send a POST request to https://api.nexscope.ai/ai/salesTalkingVideo with your API key as a Bearer token and the JSON inputs shown in API integration. In a compatible MCP client such as Claude or Cursor, connect Nexscope and call nexscope_sales_talking_video. Use the MCP arguments shown in the MCP guide, or switch Online test to MCP to review its request before adding it to your app.

View plans and credits Connect this API with MCP

Try this API

Endpoint

https://api.nexscope.ai/ai/salesTalkingVideo

MCP method

nexscope_sales_talking_video

Step 1 of 3 · Authenticate

Authentication

All run endpoints require a user API key. Send it as a bearer token in the Authorization header.

Authorization: Bearer nk-xxxxxxxxxxxxxxxxx

Missing or invalid API keys return an authentication error. Manage keys from .

Step 2 of 3 · Send a request

POSThttps://api.nexscope.ai/ai/salesTalkingVideo

Run an API

Create a product-selling video from prompt and product image references.

Example request

Replace YOUR_API_KEY, then run this command in your terminal.

curl -X POST 'https://api.nexscope.ai/ai/salesTalkingVideo' \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "aspectRatio": "9:16",
  "imageList": [
    "https://example.com/product.jpg"
  ],
  "isPro": false,
  "prompt": "Introduce this shockproof phone case in an upbeat tone.",
  "resolution": "720p",
  "videoTime": 10,
  "videoType": "seedance-2-0-fast"
}'

Step 3 of 3 · Inspect the result

Check the response

Read code for the request status and data for the result. Open the parameter and response reference for the full field definitions.

HTTP status codes

Code	Description
200	HTTP request completed. Check JSON code; only 0 indicates business success or acceptance.
400	Request JSON or required API parameters are invalid.
401	API key is missing, invalid, or cannot be matched to a user.
5xx	API execution or upstream service failed.

View parameters & response Try online

All categories/ Multimodal AI

POSThttps://api.nexscope.ai/ai/salesTalkingVideo

Run this API

Send a JSON request to execute this API and receive the documented response payload.

Open tester

Endpoint

Method	`POST`
Path	`https://api.nexscope.ai/ai/salesTalkingVideo`
Auth	`Bearer API key`
Content-Type	`application/json`

Request parameters

Name	Type	Required	Description
`prompt`	`string`	required	Sales script or creative prompt. Example: Introduce this shockproof phone case in an upbeat tone.
`imageList`	`array`	required	Public product image URLs. Provide up to 30 images for Seedance 2.5 or up to 9 images for the other supported models. Example: [ "https://example.com/product.jpg" ]
`videoType`	`string`	required	Video model. Available options `seedance-2-0` `seedance-2-0-fast` `seedance-2-0-mini` `seedance-2-5` `happyhorse-v2` Example: seedance-2-0-fast
`videoTime`	`integer`	optional	Target duration in seconds. Seedance 2.0, Fast, Mini, and HappyHorse V2 support 5, 10, or 15; Seedance 2.5 also supports 30. Example: 10
`aspectRatio`	`string`	optional	Target aspect ratio: 16:9, 9:16, 1:1, 4:3, 3:4, or 21:9. Example: 9:16
`isPro`	`boolean`	optional	Enable Pro mode for any Seedance model. HappyHorse V2 does not support Pro mode. When enabled without resolution, the default is 720p. Example: false
`resolution`	`string`	optional	Target resolution. Seedance 2.0 and 2.5 support 480p, 720p, or 1080p; Seedance Fast and Mini support 480p or 720p; HappyHorse V2 supports 720p or 1080p. Example: 720p

Code example

{
  "aspectRatio": "9:16",
  "imageList": [
    "https://example.com/product.jpg"
  ],
  "isPro": false,
  "prompt": "Introduce this shockproof phone case in an upbeat tone.",
  "resolution": "720p",
  "videoTime": 10,
  "videoType": "seedance-2-0-fast"
}

Response example

Platform response envelope. code 0 indicates success or acceptance; data contains the business result.

{
  "code": 0,
  "cost": "-1",
  "data": {
    "result": null,
    "status": "PENDING",
    "taskId": "example-task"
  },
  "msg": null,
  "time": "2026-01-01 00:00:00",
  "traceId": null,
  "ts": "0"
}

Response fields

Name	Type	Required	Description
`code`	`integer`	required	0 means accepted or successful; nonzero is a platform error.
`cost`	`string`	required	Elapsed milliseconds, never credits; -1 outside web requests.
`data`	`any`	required	Data value used by this API operation.
`msg`	`string \| null`	required	Msg value used by this API operation.
`time`	`string`	required	Server local time: yyyy-MM-dd HH:mm:ss.
`traceId`	`string \| null`	required	Trace id value used by this API operation.
`ts`	`string`	required	Epoch milliseconds.

Any of option 1 — requires taskId, status, result

Name	Type	Required	Description
`data`	`object`	required	Data value used by this API operation.
`data.result`	`any`	required	Result value used by this API operation.
`data.status`	`string`	required	Status value used by this API operation. Allowed: PENDING, RUNNING, SUCCEEDED, FAILED, TIMEOUT
`data.taskId`	`string`	required	Task id value used by this API operation.
`data.usage`	`object`	optional	Actual credits charged for a completed successful task; omitted when unavailable.
`data.usage.chargedCredits`	`integer`	required	Charged credits value used by this API operation. Minimum: 0

Any of option 1

Name	Type	Required	Description
`data.result`	`object`	required	Completed generation output retained from the task result. Fields vary by capability; generated resources use Nexscope-hosted URLs and any count represents charged Nexscope credits. This is the business output, not a task creation receipt.

Any of option 2

Name	Type	Required	Description
`data.result`	`null`	required	Result value used by this API operation.

Any of option 2

Name	Type	Required	Description
`data`	`null`	required	Data value used by this API operation.

Responses

Code	Description
200	HTTP request completed. Check JSON code; only 0 indicates business success or acceptance.
400	Request JSON or required API parameters are invalid.
401	API key is missing, invalid, or cannot be matched to a user.
5xx	API execution or upstream service failed.

Data source, freshness, and limitations

Source, freshness, coverage, rate limits, and estimation notes are not specified in this API definition unless they appear in the request or response field documentation above. Do not assume official marketplace data or real-time freshness when it is not explicitly documented.

Step 1 of 2 · Connect your MCP client

MCP

V2 recommended

Connect remote agents through the standard MCP 2025-11-25 Streamable HTTP endpoint. Use OAuth 2.1 Authorization Code with PKCE, or an API key for compatibility.

POST https://api.nexscope.ai/mcp
MCP-Protocol-Version: 2025-11-25
Content-Type: application/json

Authentication

OAuth clients request the mcp:tools scope. The endpoint's 401 response advertises protected-resource metadata for authorization discovery.

Step 2 of 2 · Call the tool

Call a tool

{
  "jsonrpc": "2.0",
  "id": "tool-call-1",
  "method": "tools/call",
  "params": {
    "name": "nexscope_sales_talking_video",
    "arguments": {
      "aspectRatio": "9:16",
      "imageList": [
        "https://example.com/product.jpg"
      ],
      "isPro": false,
      "prompt": "Introduce this shockproof phone case in an upbeat tone.",
      "resolution": "720p",
      "videoTime": 10,
      "videoType": "seedance-2-0-fast"
    }
  }
}

Legacy MCP v1

Existing API-key clients can continue using the compatibility endpoint. New integrations should use MCP v2.

GET / POST /mcp/legacy

Online test

Execute the current API with your API key and JSON payload. Online tests use this site's configured API environment; the Endpoint and copyable examples use the public integration address.

Create a video

Prompt*0 characters

Reference images*Required

JPG, PNG, WEBP · Up to 9 images · 20 MB each

0/9

Video settings

Video Model*

Video model. Supported values: seedance-2-0, seedance-2-0-fast, seedance-2-0-mini, seedance-2-5, or happyhorse-v2.

Duration

10s

Aspect ratio

Pro mode

May use more credits.

Resolution

API keys require an active subscription. Trial credits don't include API access. View plans.

Usage estimate unavailable

Final credits are shown with your result.

Preview

Your video will appear here

Recent generations

Saved in this browser for 24 hours

Your generations will appear here.

Test with an API key or MCP

Try it

Send a real request with the same contract shown in the reference.

Endpoint

/ai/salesTalkingVideo

Task result endpoint

/ai/salesTalkingVideo/tasks/{taskId}

MCP method

nexscope_sales_talking_video

API key*

JSON payload*

cURL

curl -X POST \
  https://api.nexscope.ai/ai/salesTalkingVideo \
  -H "Authorization: Bearer nk-..." \
  -H "Content-Type: application/json" \
  -d '{ "aspectRatio": "9:16", "imageList": [], "isPro": false, "prompt": "Introduce this shockproof phone case in an upbeat tone.", "resolution": "720p", "videoTime": 10, "videoType": "seedance-2-0-fast" }'

Response

No response yet. Run the request to see the response here.

Task result

Results are checked automatically after Run request. You can also enter a task ID and check it manually; completed resources use Nexscope URLs and show actual charged credits.

Task ID

Result response

No task result yet. Query the task to see the generated output here.

Related APIs

AI Apparel Image Set & Photography v3

Create apparel ecommerce image sets from clothing images with optional model and scene references.

AI Background Generator

Create product or lifestyle scene images from text prompts and optional reference images.

AI Clothes Changer for Tops & Bottoms

Dress a model image with upper and/or lower garment assets, supporting optional masks and original garment references.

AI Hand Repair

Improve hand appearance in generated model or lifestyle images.