Nexscope

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.

CostRecent Avg. 144 · Range 10–220 credits / call
Try online
POST · https://api.nexscope.ai/rg/detectionPatentDesignMCP · nexscope_data_rg_detection_patent_design
IP Risk Detection RG

What this API does

Use IP Risk Detection RG: detection Patent Design API through Nexscope with documented parameters, structured results and API key authentication. The request accepts imageUrl, queryMode, topNumber, regions, productTitle. Its documented result includes applicationNumber, publicationNumber, patentProd, patentProdCn, similarity, patentImageUrl, images, abstracts.

IP Risk Detection RG: detection Patent Design API API use cases

Investigate a product IP question

To investigate a product ip question, a compliance analyst submits imageUrl and queryMode to IP Risk Detection RG: detection Patent Design API. The returned applicationNumber, publicationNumber, patentProd help identify records relevant to the proposed product.

Collect records for an IP review

A compliance analyst uses IP Risk Detection RG: detection Patent Design API with imageUrl and queryMode to collect records for an ip review. The returned applicationNumber, publicationNumber, patentProd help collect bibliographic evidence for a specialist review.

Document evidence for specialist assessment

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

IP Risk Detection RG: detection Patent Design API API FAQ

What does the IP Risk Detection RG: detection Patent Design API API return?

Use IP Risk Detection RG: detection Patent Design API through Nexscope with documented parameters, structured results and API key authentication. The documented output includes applicationNumber, publicationNumber, patentProd, patentProdCn, similarity, patentImageUrl, images, abstracts. It corresponds to the supplied imageUrl, queryMode, topNumber, regions, productTitle. 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: detection Patent Design API API cost?

The current documented cost is Recent Avg. 144 · Range 10–220 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: detection Patent Design API API from my app or an MCP client?

Send a POST request to https://api.nexscope.ai/rg/detectionPatentDesign 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_detection_patent_design. 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/rg/detectionPatentDesign
MCP method
nexscope_data_rg_detection_patent_design

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

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/detectionPatentDesign' \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "enableRadar": true,
  "imageUrl": "https://example.com/product.jpg",
  "queryMode": "hybrid",
  "regions": "US",
  "topNumber": 50
}'

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/ IP Risk Detection RG
POSThttps://api.nexscope.ai/rg/detectionPatentDesign

Run this API

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

Endpoint

MethodPOST
Pathhttps://api.nexscope.ai/rg/detectionPatentDesign
AuthBearer API key
Content-Typeapplication/json

Request parameters

NameTypeRequiredDescription
imageUrlstringrequired
Product image file URL, used for comparison with patent database, maximum 1000 characters
queryModestringrequired
Search mode: `physical` (physical drawing search), `line` (line drawing search), `hybrid` (mixed search), maximum 1000 characters
Example: hybrid
topNumberintegerrequired
Number of recalled patents, maximum 100
Example: 100
regionsstringoptional
The country/region codes where the product is sold, separated by commas when selecting multiple items. support `US`, `EU`, `CN`, `JP`, `KR`, `DE`, `GB`, `FR`, `IT`, `AU`, `CA`, `BR`, `MX`, `IN`, `TH`, `SE`, `CH`, `IE`, `IL`, `DK`, `NZ`, `AT`, `BX`, `FI`, `WO`, max. 1000 characters
Example: US
productTitlestringoptional
Product title, used to supplement search context, maximum 1000 characters
productDescriptionstringoptional
Product description, used to supplement search context, maximum 1000 characters
patentStatusstringoptional
Patent validity filter: `1` (valid patent), `0` (invalidated patent), `1,0` (all), maximum 1000 characters
Example: 1
enableRadarbooleanoptional
Whether to enable radar chart (AI infringement determination analysis)
Example: true
topLocstringoptional
Specify the first-level LOC range to retrieve, such as `06,07`. The format is `^(0[1-9]\|1[0-9]\|2[0-9]\|3[0-2]\|ALL)(,(0[1-9]\|1[0-9]\|2[0-9]\|3[0-2]\|ALL))*$`; if not specified, use model LOC prediction results
sourceLanguagestringoptional
The original language code needs to be marked for uniform translation into English, such as `zh-CN`; when the text is in English, just pass it empty, the maximum length is 1000 characters

Code example

{
  "enableRadar": true,
  "imageUrl": "https://example.com/product.jpg",
  "queryMode": "hybrid",
  "regions": "US",
  "topNumber": 50
}

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

NameTypeRequiredDescription
totalintegeroptional
Total number of patent records returned
dataarrayoptional
Patent list (see patent objects below for details)
columnsarrayoptional
Rendered column definitions
costTokenintegeroptional
Consume token
typestringoptional
Rendering style
applicationNumberstringoptional
Patent application number
publicationNumberstringoptional
Patent publication number
patentProdstringoptional
Patent title (English)
patentProdCnstringoptional
Patent title (Chinese)
similaritystringoptional
Similarity between patent and product pictures (0-1)
patentImageUrlstringoptional
The URL of the patent drawing that is most similar to the product image
imagesarrayoptional
Patent picture list
abstractsstringoptional
Patent abstract
specificationstringoptional
patent specification
inventorsarrayoptional
List of inventors
applicantsarrayoptional
Applicant list
applicantAddressesarrayoptional
Applicant address
troCasebooleanoptional
Do you have a history of TRO rights protection?
troHolderbooleanoptional
Is it the patent of the TRO right holder?
radarResultobjectoptional
AI radar analysis results
radarResult.samebooleanoptional
Is it suspected of infringement?
radarResult.expstringoptional
Expected Description (Radar Determination Instructions)
patentLocstringoptional
LOC classification of the patent, multiple separated by commas
locOneInfostringoptional
LOC Level 1 Details
locTwoInfostringoptional
LOC Level 2 Details
patentValiditystringoptional
patent validity
applicationDatestringoptional
Patent application date
publicationDatestringoptional
Patent disclosure date
grantDatestringoptional
Patent grant date
estimatedDueDatestringoptional
Estimated maturity date
registrationOfficeCodestringoptional
Patent Registration and Reception Office
patentFamilyarrayoptional
List of patent families
globalPatentIdstringoptional
Global Patent ID
globalImageIdstringoptional
ID of the patent image
isSketchTextstringoptional
Is it a line drawing?

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_rg_detection_patent_design",
    "arguments": {
      "enableRadar": true,
      "imageUrl": "https://example.com/product.jpg",
      "queryMode": "hybrid",
      "regions": "US",
      "topNumber": 50
    }
  }
}

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/detectionPatentDesign
MCP method
nexscope_data_rg_detection_patent_design
cURL
curl -X POST \
  https://api.nexscope.ai/rg/detectionPatentDesign \
  -H "Authorization: Bearer nk-..." \
  -H "Content-Type: application/json" \
  -d '{ "enableRadar": true, "imageUrl": "", "queryMode": "hybrid", "regions": "US", "topNumber": 50 }'
Response
No response yet. Run the request to see the response here.

Related APIs