Product Scene Variations

Generate multiple ecommerce scene variants from a product image, optional segmentation, and prompt guidance. Available via REST API or MCP.

CostEst. 47–57 credits / call

Try online

POST · https://api.nexscope.ai/ai/productSceneVariationsMCP · nexscope_product_scene_variations

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

Generate multiple ecommerce scene variants from a product image, optional segmentation, and prompt guidance. The request accepts imageUrl, segImageUrl, strength, prompt, imageOutputWidth. Generation runs as a task: retain the task ID and retrieve the completed result before using the output.

Product Scene Variations API use cases

Inspect a candidate product

To inspect a candidate product, a content editor submits imageUrl and segImageUrl to Product Scene Variations. The returned completed generation results help inspect the documented attributes of the candidate product.

Compare listing details

A content editor uses Product Scene Variations with imageUrl and segImageUrl to compare listing details. The returned completed generation results help compare product details with another shortlisted listing.

Prepare product evidence for a sourcing review

For this workflow, a content editor calls Product Scene Variations with imageUrl and segImageUrl to prepare product evidence for a sourcing review. The result helps record product facts before a sourcing discussion.

Product Scene Variations API FAQ

What does the Product Scene Variations API return?

Generate multiple ecommerce scene variants from a product image, optional segmentation, and prompt guidance. It corresponds to the supplied imageUrl, segImageUrl, strength, prompt, imageOutputWidth. 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 Product Scene Variations API cost?

The current documented cost is Est. 47–57 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 Product Scene Variations API from my app or an MCP client?

Send a POST request to https://api.nexscope.ai/ai/productSceneVariations 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_product_scene_variations. 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/productSceneVariations

MCP method

nexscope_product_scene_variations

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/productSceneVariations

Run an API

Generate multiple ecommerce scene variants from a product image, optional segmentation, and prompt guidance.

Example request

Replace YOUR_API_KEY, then run this command in your terminal.

curl -X POST 'https://api.nexscope.ai/ai/productSceneVariations' \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "imageOutputHeight": 1024,
  "imageOutputWidth": 1024,
  "imageUrl": "https://example.com/product.jpg",
  "outputNum": 1,
  "prompt": "modern kitchen countertop",
  "segImageUrl": "https://example.com/mask.png",
  "strength": 0.5
}'

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/productSceneVariations

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/productSceneVariations`
Auth	`Bearer API key`
Content-Type	`application/json`

Request parameters

Name	Type	Required	Description
`imageUrl`	`string`	required	Public URL of the product image. The image must be up to 20 MB and between 385 and 8192 pixels in both width and height. Example: https://example.com/product.jpg
`segImageUrl`	`string`	optional	Optional segmentation mask URL. Example: https://example.com/mask.png
`strength`	`number`	optional	Variation strength from 0.1 to 1. Defaults to 0.5. Example: 0.5
`prompt`	`string`	optional	Scene generation prompt, up to 600 characters. Example: modern kitchen countertop
`imageOutputWidth`	`integer`	optional	Desired output width in pixels, from 32 to 2048. Example: 1024
`imageOutputHeight`	`integer`	optional	Desired output height in pixels, from 32 to 2048. Example: 1024
`outputNum`	`integer`	optional	Number of images to generate, from 1 to 4. Example: 1

Code example

{
  "imageOutputHeight": 1024,
  "imageOutputWidth": 1024,
  "imageUrl": "https://example.com/product.jpg",
  "outputNum": 1,
  "prompt": "modern kitchen countertop",
  "segImageUrl": "https://example.com/mask.png",
  "strength": 0.5
}

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_product_scene_variations",
    "arguments": {
      "imageOutputHeight": 1024,
      "imageOutputWidth": 1024,
      "imageUrl": "https://example.com/product.jpg",
      "outputNum": 1,
      "prompt": "modern kitchen countertop",
      "segImageUrl": "https://example.com/mask.png",
      "strength": 0.5
    }
  }
}

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 an image

Prompt0 characters

Source image*Required

Public URL of the product image. The image must be up to 20 MB and between 385 and 8192 pixels in both width and height.

JPG, PNG, WEBP · 1 image · 20 MB · 385–8192 px per side

0/1

Segmentation MaskOptional

Optional segmentation mask URL.

JPG, PNG, WEBP · 1 image · 20 MB

0/1

Image settings

Edit Strength

Variation strength from 0.1 to 1. Defaults to 0.5.

Output Width

Desired output width in pixels, from 32 to 2048.

Output Height

Desired output height in pixels, from 32 to 2048.

Images

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 image 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/productSceneVariations

Task result endpoint

/ai/productSceneVariations/tasks/{taskId}

MCP method

nexscope_product_scene_variations

API key*

JSON payload*

cURL

curl -X POST \
  https://api.nexscope.ai/ai/productSceneVariations \
  -H "Authorization: Bearer nk-..." \
  -H "Content-Type: application/json" \
  -d '{ "imageOutputHeight": 1024, "imageOutputWidth": 1024, "imageUrl": "", "outputNum": 1, "prompt": "modern kitchen countertop", "segImageUrl": "", "strength": 0.5 }'

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.