Print & Pattern Extraction

Extract visible print or pattern elements from product imagery. Use the Print & Pattern Extraction API via REST or MCP, or try it free in the online playground.

CostEst. 47–57 credits / call

Try online

POST · https://api.nexscope.ai/ai/printPatternExtractionMCP · nexscope_print_pattern_extraction

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.

What this API does

Extract visible print or pattern elements from product imagery. The request accepts imageUrl. Generation runs as a task: retain the task ID and retrieve the completed result before using the output.

Print & Pattern Extraction API use cases

Investigate Print & Pattern Extraction

To investigate print & pattern extraction, a content editor submits imageUrl to Print & Pattern Extraction. The returned completed generation results help investigate the requested operation.

Collect Print & Pattern Extraction evidence

A content editor uses Print & Pattern Extraction with imageUrl to collect print & pattern extraction evidence. The returned completed generation results help compare evidence for the requested scope.

Review Print & Pattern Extraction results

For this workflow, a content editor calls Print & Pattern Extraction with imageUrl to review print & pattern extraction results. The result helps review the returned facts with the team.

Print & Pattern Extraction API FAQ

What does the Print & Pattern Extraction API return?

Extract visible print or pattern elements from product imagery. It corresponds to the supplied imageUrl. 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 Print & Pattern Extraction 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 Print & Pattern Extraction API from my app or an MCP client?

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

MCP method

nexscope_print_pattern_extraction

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

Run an API

Extract visible print or pattern elements from product imagery.

Example request

Replace YOUR_API_KEY, then run this command in your terminal.

curl -X POST 'https://api.nexscope.ai/ai/printPatternExtraction' \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "imageUrl": "https://example.com/product.jpg"
}'

Code example

{
  "imageUrl": "https://example.com/product.jpg"
}

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	Default HTTP response for both success and many business errors. Only outer JSON code 0 indicates success or asynchronous acceptance; inspect data for the result.
429	Execution admission rate limit; honor Retry-After when present.
503	Execution admission is temporarily unavailable; honor Retry-After when present.
Opt-in	X-Nexscope-Http-Status: semantic maps controller-handled business errors to HTTP status on run and task routes. Pre-authentication failures, such as a missing or invalid API key (code 11209, including an incomplete or corrupted copy) or an expired website login session (code 12001), may still return HTTP 200 before this mapping. Always check the outer JSON code; malformed requests and infrastructure failures may also return non-200 HTTP responses.

View parameters & response Try online

All categories/ Multimodal AI

POSThttps://api.nexscope.ai/ai/printPatternExtraction

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

Request parameters

Name	Type	Required	Description
`imageUrl`	`string`	required	Public URL of the image containing the print. 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

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.

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	Default HTTP response for both success and many business errors. Only outer JSON code 0 indicates success or asynchronous acceptance; inspect data for the result.
429	Execution admission rate limit; honor Retry-After when present.
503	Execution admission is temporarily unavailable; honor Retry-After when present.
Opt-in	X-Nexscope-Http-Status: semantic maps controller-handled business errors to HTTP status on run and task routes. Pre-authentication failures, such as a missing or invalid API key (code 11209, including an incomplete or corrupted copy) or an expired website login session (code 12001), may still return HTTP 200 before this mapping. Always check the outer JSON code; malformed requests and infrastructure failures may also return non-200 HTTP responses.

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_print_pattern_extraction",
    "arguments": {
      "imageUrl": "https://example.com/product.jpg"
    }
  }
}

Legacy MCP v1

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

GET / POST /mcp/legacy

What can you do with this API?

Data explained and practical use cases

AI Guide

Question

What can Print & Pattern Extraction produce, and how might I use the result?

AI answer

Print & Pattern Extraction takes a product image URL and runs an extraction task for its visible print or pattern. The documented submission example is PENDING with data.result set to null. The task result must be checked before any extracted output can be used; the documentation does not specify a fixed set of pattern attributes or file fields inside the completed result. API documentation.

Data category	Documented fields	What the values mean
Extracted output	`data.result`	The completed task's business output, when available. Its capability-specific structure is not documented here.
Availability	`data.status`	Whether the task is pending, running, succeeded, failed, or timed out; it determines whether a result is ready.

Extract a visible textile print from a garment photo for a designer to inspect as a separate visual reference.
- Prompt example: “I am researching products for an online store. Could you extract a visible textile print from a garment photo for a designer to inspect as a separate visual reference? Show the relevant returned evidence and tell me what input you need from me.”
Pull a pattern from a product image to compare its appearance with another design after the task succeeds.
- Prompt example: “I am researching products for an online store. Could you pull a pattern from a product image to compare its appearance with another design after the task succeeds? Show the returned values behind the comparison, and mark missing data.”
Review the completed extraction before deciding whether it is suitable for a product-content workflow. The pending response alone supplies no extracted pattern.
- Prompt example: “I am researching products for an online store. Could you review the completed extraction before deciding whether it is suitable for a product-content workflow? Show the relevant returned evidence and tell me what input you need from me.”