Nexscope

IP Risk Detection RG: utility Patent Detection API

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

Cost81 credits / call
Try online
POST · https://api.nexscope.ai/rg/utilityPatentDetectionMCP · nexscope_data_rg_utility_patent_detection
IP Risk Detection RG

What this API does

Use IP Risk Detection RG: utility Patent Detection API through Nexscope with documented parameters, structured results and API key authentication. The request accepts productTitle, productDescription, region, topNumber. Its documented result includes detectId, globalUtilityId, title, titleCn, similarity, patentValidity, applicationNumber, applicationDate.

IP Risk Detection RG: utility Patent Detection API API use cases

Investigate a product IP question

To investigate a product ip question, a compliance analyst submits productTitle and productDescription to IP Risk Detection RG: utility Patent Detection API. The returned detectId, globalUtilityId, title help identify records relevant to the proposed product.

Collect records for an IP review

A compliance analyst uses IP Risk Detection RG: utility Patent Detection API with productTitle and productDescription to collect records for an ip review. The returned detectId, globalUtilityId, title help collect bibliographic evidence for a specialist review.

Document evidence for specialist assessment

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

IP Risk Detection RG: utility Patent Detection API API FAQ

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

Use IP Risk Detection RG: utility Patent Detection API through Nexscope with documented parameters, structured results and API key authentication. The documented output includes detectId, globalUtilityId, title, titleCn, similarity, patentValidity, applicationNumber, applicationDate. It corresponds to the supplied productTitle, productDescription, region, topNumber. 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: utility Patent Detection API API cost?

The current documented cost is 81 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: utility Patent Detection API API from my app or an MCP client?

Send a POST request to https://api.nexscope.ai/rg/utilityPatentDetection 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_utility_patent_detection. 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/utilityPatentDetection
MCP method
nexscope_data_rg_utility_patent_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/utilityPatentDetection

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/utilityPatentDetection' \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "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
}'

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

Run this API

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

Endpoint

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

Request parameters

NameTypeRequiredDescription
productTitlestringrequired
Product title, maximum 1000 characters
productDescriptionstringrequired
Product description, max 1000 characters
regionstringrequired
The country/region code where the product is to be sold. Multiples are separated by commas. Currently, `US` is supported.
Example: US
topNumberintegerrequired
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)

NameTypeRequiredDescription
totalintegeroptional
Number of records
detectIdstringoptional
Detection ID
costTokenintegeroptional
Consume token
typestringoptional
Rendering style
columnsarrayoptional
Rendered column definitions
dataarrayoptional
Patent list (see patent object field below for details)
globalUtilityIdstringoptional
Patent ID
titlestringoptional
Invention patent title
titleCnstringoptional
Invention Patent Title (Chinese)
similaritynumberoptional
How similar the product is to the patent (0-1)
patentValiditystringoptional
Patent validity: `Active` (valid) or `Invalid` (invalid)
applicationNumberstringoptional
Application number
applicationDatestringoptional
Application date (yyyy-MM-dd)
publicationNumberstringoptional
Public account
publicationDatestringoptional
Open day (yyyy-MM-dd)
estimatedDueDatestringoptional
Estimated maturity date (yyyy-MM-dd)
regionstringoptional
receiving office
patentAbstractstringoptional
Summary
patentAbstractCnstringoptional
Abstract (Chinese)
claimsstringoptional
claims
claimsCnstringoptional
Claims (Chinese)
specificationstringoptional
Instructions
specificationCnstringoptional
Instructions (Chinese)
inventorsarrayoptional
Inventor and country splicing, array format
inventorAddressesarrayoptional
Inventor address, array format
applicantsarrayoptional
Applicant and country concatenation, array format
applicantAddressesarrayoptional
Right holder address, array format
priorityNumberarrayoptional
Priority number, array format
relatedPublicationDatearrayoptional
First public date (yyyy-MM-dd), array format
patentImageUrlstringoptional
Patent cover image
imagesarrayoptional
Patent drawings
classNumListarrayoptional
Category number path list, in the format of `classNum1 > classNum2 > classNum3`
cpcKindRawarrayoptional
CPC classification (raw JSONArray)
troCasebooleanoptional
Do you have a history of TRO rights protection?
troHolderbooleanoptional
Is it the patent of the TRO right holder?

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_utility_patent_detection",
    "arguments": {
      "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
    }
  }
}

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.

81 credits / callAPI usage records

Try it

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

Endpoint
/rg/utilityPatentDetection
MCP method
nexscope_data_rg_utility_patent_detection
cURL
curl -X POST \
  https://api.nexscope.ai/rg/utilityPatentDetection \
  -H "Authorization: Bearer nk-..." \
  -H "Content-Type: application/json" \
  -d '{ "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
No response yet. Run the request to see the response here.

Related APIs