Nexscope

TRO Risk Detection MD: check Api Flash API

Use TRO Risk Detection MD: check Api Flash API through Nexscope with documented parameters, structured results and API key authentication.

Cost234 credits / call
Try online
POST · https://api.nexscope.ai/md/checkApiFlashMCP · nexscope_data_md_check_api_flash
TRO Risk Detection MD

What this API does

Use TRO Risk Detection MD: check Api Flash API through Nexscope with documented parameters, structured results and API key authentication. The request accepts mainProductImage, referenceImages, otherProductImages, ipImages, referenceText. Its documented result includes errcode, errmsg, checkId, riskLevel, results, nonResults, ipType, text.

TRO Risk Detection MD: check Api Flash API API use cases

Investigate TRO Risk Detection MD: check Api Flash API

To investigate tro risk detection md: check api flash api, a marketplace analyst submits mainProductImage and referenceImages to TRO Risk Detection MD: check Api Flash API. The returned errcode, errmsg, checkId help investigate the requested operation.

Collect TRO Risk Detection MD: check Api Flash API evidence

A marketplace analyst uses TRO Risk Detection MD: check Api Flash API with mainProductImage and referenceImages to collect tro risk detection md: check api flash api evidence. The returned errcode, errmsg, checkId help compare evidence for the requested scope.

Review TRO Risk Detection MD: check Api Flash API results

For this workflow, a marketplace analyst calls TRO Risk Detection MD: check Api Flash API with mainProductImage and referenceImages to review tro risk detection md: check api flash api results. The result helps review the returned facts with the team.

TRO Risk Detection MD: check Api Flash API API FAQ

What does the TRO Risk Detection MD: check Api Flash API API return?

Use TRO Risk Detection MD: check Api Flash API through Nexscope with documented parameters, structured results and API key authentication. The documented output includes errcode, errmsg, checkId, riskLevel, results, nonResults, ipType, text. It corresponds to the supplied mainProductImage, referenceImages, otherProductImages, ipImages, referenceText. Optional fields can be absent; a missing value should not be interpreted as a measured zero. Example values illustrate the response shape, rather than live account results.

How many credits does the TRO Risk Detection MD: check Api Flash API API cost?

The current documented cost is 234 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 TRO Risk Detection MD: check Api Flash API API from my app or an MCP client?

Send a POST request to https://api.nexscope.ai/md/checkApiFlash 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_data_md_check_api_flash. The same documented request parameters apply; use Online test to review a request before adding it to your app.

View plans and creditsConnect this API with MCP

Try this API
Endpoint
https://api.nexscope.ai/md/checkApiFlash
MCP method
nexscope_data_md_check_api_flash

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/md/checkApiFlash

Run an API

Send a JSON request body using the parameters described below.

Example request

Replace YOUR_API_KEY, then run this command in your terminal.

curl -X POST 'https://api.nexscope.ai/md/checkApiFlash' \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "language": "zh",
  "mainProductImage": "https://m.media-amazon.com/images/I/71jKJgFpg8L._AC_SL1500_.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

CodeDescription
200HTTP request completed. Check JSON code; only 0 indicates business success or acceptance.
400Request JSON or required API parameters are invalid.
401API key is missing, invalid, or cannot be matched to a user.
5xxAPI execution or upstream service failed.
All categories/ TRO Risk Detection MD
POSThttps://api.nexscope.ai/md/checkApiFlash

Run this API

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

Endpoint

MethodPOST
Pathhttps://api.nexscope.ai/md/checkApiFlash
AuthBearer API key
Content-Typeapplication/json

Request parameters

NameTypeRequiredDescription
mainProductImagestringrequired
Main product image, which can be a public image URL or a Base64 data URI prefixed with `data:image/...;base64,`; the maximum length is 1000
referenceImagesstring[]optional
Array of similar product reference pictures, the elements are URL or data URI, up to 3 pictures
otherProductImagesstring[]optional
Array of additional product images, the elements are URL or data URI, up to 5 images
ipImagesstring[]optional
Array of pictures related to intellectual property, the elements are URL or data URI, up to 3 pictures
referenceTextstringoptional
Similar product text, such as product title; maximum length 1000 characters
descriptionstringoptional
Product description, it is recommended to fill in only the product title; the maximum length is 1000 characters
ipKeywordsstring[]optional
Array of keywords related to intellectual property, up to 20
languagestringoptional
Legal assessment report language, affects `report` field only; optional `zh` or `en`
Example: zh

Code example

{
  "language": "zh",
  "mainProductImage": "https://m.media-amazon.com/images/I/71jKJgFpg8L._AC_SL1500_.jpg"
}

Response example

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

{
  "code": 0,
  "cost": "-1",
  "data": {},
  "msg": null,
  "time": "2026-01-01 00:00:00",
  "traceId": null,
  "ts": "0"
}

Response fields

Response field reference (25 fields)

NameTypeRequiredDescription
errcodeintegeroptional
Business status code, `200` indicates success
errmsgstringoptional
Status description, `ok` when successful
statusstringoptional
Analyze the overall status, `success` when successful
checkIdstringoptional
The unique identifier for this test
typestringoptional
Rendering style, such as `tableListWorkbenches`
costTokenintegeroptional
The token consumed by this call
totalintegeroptional
The number of high-risk infringement items, that is, the length of the `results` array
riskLevelstringoptional
Overall risk assessment: `High Risk`, `Medium Risk` or `Low Risk`
resultsarrayoptional
List of high-risk potential infringement items, please see the "Infringement Item Fields" below for the fields.
nonResultsarrayoptional
A list of IP items that are not high risk or low similarity, including information about possible TRO plaintiffs. See the "Infringement Item Fields" below for the fields.
columnsarrayoptional
Rendered column definitions for display only; length may differ from data array
ipTypestringoptional
IP type: `Trademark`, `Copyright` or `Patent`
textstringoptional
IP text content such as trademark text, patent title, or copyright title
ipOwnerstringoptional
Intellectual property right holder
regNostringoptional
Registration number, possibly an array of JSON strings, such as `["1221667"]`
riskLevelstringoptional
Risk level: `High Risk`, `Medium Risk`, or `Low Risk`; does not appear if there is no rating
riskScorenumberoptional
0-10 Numeric risk score; does not appear if there is no score
riskDescriptionstringoptional
Risk level text description; does not appear if there is no score
ipAssetUrlsstring[]optional
IP Evidence Image URL List
plaintiffIdintegeroptional
TRO Plaintiff ID, only appears if the IP appears in a TRO case
plaintiffNamestringoptional
TRO plaintiff name, appears only if the IP appears in a TRO case
numberOfCasesintegeroptional
Number of cases filed by this plaintiff; may be `null` if case details are not available
lastCaseDocketstringoptional
Court docket number of the most recent case; may be `null` if case details are not available
lastCaseDateFiledstringoptional
Date the most recent case was filed; may be `null` if case details are not available
reportstringoptional
AI-generated legal assessment report, the language is determined by the `language` parameter

Responses

CodeDescription
200HTTP request completed. Check JSON code; only 0 indicates business success or acceptance.
400Request JSON or required API parameters are invalid.
401API key is missing, invalid, or cannot be matched to a user.
5xxAPI 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_data_md_check_api_flash",
    "arguments": {
      "language": "zh",
      "mainProductImage": "https://m.media-amazon.com/images/I/71jKJgFpg8L._AC_SL1500_.jpg"
    }
  }
}

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.

234 credits / callAPI usage records

Try it

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

Endpoint
/md/checkApiFlash
MCP method
nexscope_data_md_check_api_flash
cURL
curl -X POST \
  https://api.nexscope.ai/md/checkApiFlash \
  -H "Authorization: Bearer nk-..." \
  -H "Content-Type: application/json" \
  -d '{ "language": "zh", "mainProductImage": "https://m.media-amazon.com/images/I/71jKJgFpg8L._AC_SL1500_.jpg" }'
Response
No response yet. Run the request to see the response here.