IP Risk Detection RG: trademark Graphic Detection API

Use IP Risk Detection RG: trademark Graphic Detection API through Nexscope with documented parameters, structured results and API key authentication.

CostRecent 127 credits / call

Try online

POST · https://api.nexscope.ai/rg/trademarkGraphicDetectionMCP · nexscope_data_rg_trademark_graphic_detection

IP Risk Detection RG

What this API does

Use IP Risk Detection RG: trademark Graphic Detection API through Nexscope with documented parameters, structured results and API key authentication. The request accepts imageUrl, topNumber, productTitle, trademarkName, regions. Its documented result includes boundingBoxCount, radarResult, detectId, image, boundingBox, subRadarResult, applicationNumber, niceClassName.

IP Risk Detection RG: trademark Graphic Detection API API use cases

Investigate a product IP question

To investigate a product ip question, a compliance analyst submits imageUrl and topNumber to IP Risk Detection RG: trademark Graphic Detection API. The returned boundingBoxCount, radarResult, detectId help identify records relevant to the proposed product.

Collect records for an IP review

A compliance analyst uses IP Risk Detection RG: trademark Graphic Detection API with imageUrl and topNumber to collect records for an ip review. The returned boundingBoxCount, radarResult, detectId help collect bibliographic evidence for a specialist review.

Document evidence for specialist assessment

For this workflow, a compliance analyst calls IP Risk Detection RG: trademark Graphic Detection API with imageUrl and topNumber to document evidence for specialist assessment. The result helps document the records supporting an IP research question.

IP Risk Detection RG: trademark Graphic Detection API API FAQ

What does the IP Risk Detection RG: trademark Graphic Detection API API return?

Use IP Risk Detection RG: trademark Graphic Detection API through Nexscope with documented parameters, structured results and API key authentication. The documented output includes boundingBoxCount, radarResult, detectId, image, boundingBox, subRadarResult, applicationNumber, niceClassName. It corresponds to the supplied imageUrl, topNumber, productTitle, trademarkName, regions. 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 IP Risk Detection RG: trademark Graphic Detection API API cost?

The current documented cost is Recent 127 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 IP Risk Detection RG: trademark Graphic Detection API API from my app or an MCP client?

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

View plans and credits Connect this API with MCP

Try this API

Endpoint

https://api.nexscope.ai/rg/trademarkGraphicDetection

MCP method

nexscope_data_rg_trademark_graphic_detection

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/rg/trademarkGraphicDetection

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/rg/trademarkGraphicDetection' \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "imageUrl": "https://example.com/product-image.jpg",
  "productTitle": "Wireless Bluetooth headphones",
  "regions": "US,EM",
  "topNumber": 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/ IP Risk Detection RG

POSThttps://api.nexscope.ai/rg/trademarkGraphicDetection

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

Request parameters

Name	Type	Required	Description
`imageUrl`	`string`	required	Product image URL or base64-encoded image data, maximum 1000 characters
`topNumber`	`integer`	required	Returns the maximum number of YOLO coordinates, ranging from 1-100; the actual number returned may be less than the number of parameters passed Example: 5
`productTitle`	`string`	optional	Product title, used for context-aware detection, max 1000 characters
`trademarkName`	`string`	optional	Possible graphic logo names, used to narrow the search scope, maximum 1000 characters
`regions`	`string`	optional	Country/region codes to be detected, separate with commas if multiple. If not transmitted, all countries will be detected by default. Optional values: `US`, `WO`, `ES`, `GB`, `DE`, `IT`, `CA`, `MX`, `EM`, `AU`, `FR`, `JP`, `TR`, `BX`, `CN`
`enableLocalizing`	`boolean`	optional	Whether to enable image cutting Example: false
`enableRadar`	`boolean`	optional	Whether to enable radar monitoring Example: true

Code example

{
  "imageUrl": "https://example.com/product-image.jpg",
  "productTitle": "Wireless Bluetooth headphones",
  "regions": "US,EM",
  "topNumber": 5
}

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 (23 fields)

Name	Type	Required	Description
`boundingBoxCount`	`integer`	optional	Number of test results
`radarResult`	`string`	optional	Radar detection results
`total`	`integer`	optional	Number of records
`data`	`array`	optional	Test result list (see element fields below for details)
`detectId`	`string`	optional	Detection ID
`columns`	`array`	optional	Rendered column definitions
`costToken`	`integer`	optional	Consume token
`type`	`string`	optional	Rendering style
`image`	`string`	optional	Matching trademark image address
`boundingBox`	`string`	optional	YOLO coordinates, comma separated
`subRadarResult`	`string`	optional	Sub-radar detection results
`applicationNumber`	`string`	optional	Application number
`niceClassName`	`string`	optional	Nice classification names, comma separated
`applicantName`	`string`	optional	Rights holders, separated by commas
`tradeMarkStatus`	`string`	optional	Trademark status, enumeration value is `DEL`, `ended`, `registered`, `act`, `pend`, `filed` or empty string
`niceClass`	`array`	optional	Nice classification details
`similarity`	`number`	optional	Similarity (0 to 1, higher values are more similar)
`registrationNumber`	`string`	optional	Registration number
`registrationOfficeCode`	`string`	optional	Trademark Acceptance Office
`registrationDate`	`string`	optional	Registration date
`bid`	`string`	optional	logo
`trademarkName`	`string`	optional	Text brand name in image
`applicationDate`	`string`	optional	Application date

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_data_rg_trademark_graphic_detection",
    "arguments": {
      "imageUrl": "https://example.com/product-image.jpg",
      "productTitle": "Wireless Bluetooth headphones",
      "regions": "US,EM",
      "topNumber": 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.

120 credits / callAPI usage records

Try it

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

Endpoint

/rg/trademarkGraphicDetection

MCP method

nexscope_data_rg_trademark_graphic_detection

API key*

JSON payload*

cURL

curl -X POST \
  https://api.nexscope.ai/rg/trademarkGraphicDetection \
  -H "Authorization: Bearer nk-..." \
  -H "Content-Type: application/json" \
  -d '{ "imageUrl": "", "productTitle": "Wireless Bluetooth headphones", "regions": "US,EM", "topNumber": 5 }'

Response

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

Use IP Risk Detection RG: copyright Detection API through Nexscope with documented parameters, structured results and API key authentication.

IP Risk Detection RG: detection Patent Design API

Use IP Risk Detection RG: detection Patent Design API through Nexscope with documented parameters, structured results and API key authentication.

IP Risk Detection RG: gun Parts Search API

Use IP Risk Detection RG: gun Parts Search API through Nexscope with documented parameters, structured results and API key authentication.

IP Risk Detection RG: text Trademark Detection API

Use IP Risk Detection RG: text Trademark Detection API through Nexscope with documented parameters, structured results and API key authentication.

What this API does

IP Risk Detection RG: trademark Graphic Detection API API use cases

Investigate a product IP question

Collect records for an IP review

Document evidence for specialist assessment

IP Risk Detection RG: trademark Graphic Detection API API FAQ

What does the IP Risk Detection RG: trademark Graphic Detection API API return?

How many credits does the IP Risk Detection RG: trademark Graphic Detection API API cost?

How do I call the IP Risk Detection RG: trademark Graphic Detection API API from my app or an MCP client?

Authentication

Run an API

Example request

Check the response

HTTP status codes

Run this API

Endpoint

Request parameters

Code example

Response example

Response fields

Responses

Data source, freshness, and limitations

MCP

Call a tool

Legacy MCP v1

Online test

Try it

Related APIs