https://api.nexscope.ai/rg/utilityPatentDetectionRun this API
Send a JSON request to execute this API and receive the documented response payload.
Endpoint
| Method | POST |
| Path | https://api.nexscope.ai/rg/utilityPatentDetection |
| Auth | Bearer API key |
| Content-Type | application/json |
Request parameters
| Name | Type | Required | Description |
|---|---|---|---|
productTitle | string | required | Product title, maximum 1000 characters |
productDescription | string | required | Product description, max 1000 characters |
region | string | required | The country/region code where the product is to be sold. Multiples are separated by commas. Currently, `US` is supported. Example: US |
topNumber | integer | required | Recall quantity, range 10-200 Example: 100 |
Code example
{
"productDescription": "A compact 65W GaN USB-C fast charger with a foldable plug, PD3.0 and QC4.0 support, two USB-C ports and one USB-A port for laptops, phones and tablets.",
"productTitle": "Portable USB-C 65W GaN fast charger",
"region": "US",
"topNumber": 100
}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)
| Name | Type | Required | Description |
|---|---|---|---|
total | integer | optional | Number of records |
detectId | string | optional | Detection ID |
costToken | integer | optional | Consume token |
type | string | optional | Rendering style |
columns | array | optional | Rendered column definitions |
data | array | optional | Patent list (see patent object field below for details) |
globalUtilityId | string | optional | Patent ID |
title | string | optional | Invention patent title |
titleCn | string | optional | Invention Patent Title (Chinese) |
similarity | number | optional | How similar the product is to the patent (0-1) |
patentValidity | string | optional | Patent validity: `Active` (valid) or `Invalid` (invalid) |
applicationNumber | string | optional | Application number |
applicationDate | string | optional | Application date (yyyy-MM-dd) |
publicationNumber | string | optional | Public account |
publicationDate | string | optional | Open day (yyyy-MM-dd) |
estimatedDueDate | string | optional | Estimated maturity date (yyyy-MM-dd) |
region | string | optional | receiving office |
patentAbstract | string | optional | Summary |
patentAbstractCn | string | optional | Abstract (Chinese) |
claims | string | optional | claims |
claimsCn | string | optional | Claims (Chinese) |
specification | string | optional | Instructions |
specificationCn | string | optional | Instructions (Chinese) |
inventors | array | optional | Inventor and country splicing, array format |
inventorAddresses | array | optional | Inventor address, array format |
applicants | array | optional | Applicant and country concatenation, array format |
applicantAddresses | array | optional | Right holder address, array format |
priorityNumber | array | optional | Priority number, array format |
relatedPublicationDate | array | optional | First public date (yyyy-MM-dd), array format |
patentImageUrl | string | optional | Patent cover image |
images | array | optional | Patent drawings |
classNumList | array | optional | Category number path list, in the format of `classNum1 > classNum2 > classNum3` |
cpcKindRaw | array | optional | CPC classification (raw JSONArray) |
troCase | boolean | optional | Do you have a history of TRO rights protection? |
troHolder | boolean | optional | Is it the patent of the TRO right holder? |
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.