Utility Patent Detector

Search for similar utility and invention patents from product information. Call the Utility Patent Detector API via REST or MCP from 81 credits per call.

Cost81 credits / call

Try online

POST · https://api.nexscope.ai/rg/utilityPatentDetectionMCP · nexscope_utility_patent_detector

What this API does

Search for similar utility and invention patents from product information. The request accepts productTitle, productDescription, region, topNumber. Its documented result includes detectId, globalUtilityId, title, titleCn, similarity, patentValidity, applicationNumber, applicationDate.

Utility Patent Detector API use cases

Investigate a product IP question

To investigate a product ip question, a compliance analyst submits productTitle and productDescription to Utility Patent Detector. The returned detectId, globalUtilityId, title help identify records relevant to the proposed product.

Collect records for an IP review

A compliance analyst uses Utility Patent Detector 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 Utility Patent Detector with productTitle and productDescription to document evidence for specialist assessment. The result helps document the records supporting an IP research question.

Utility Patent Detector API FAQ

What does the Utility Patent Detector API return?

Search for similar utility and invention patents from product information. 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 Utility Patent Detector 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 Utility Patent Detector 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_utility_patent_detector. Use the MCP arguments shown in the MCP guide, or switch Online test to MCP to review its 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/utilityPatentDetection

MCP method

nexscope_utility_patent_detector

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
}'

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
}

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	Default HTTP response for both success and many business errors. Only outer JSON code 0 indicates success or asynchronous acceptance; inspect data for the result.
429	Execution admission rate limit; honor Retry-After when present.
503	Execution admission is temporarily unavailable; honor Retry-After when present.
Opt-in	X-Nexscope-Http-Status: semantic maps controller-handled business errors to HTTP status on run and task routes. Pre-authentication failures, such as a missing API key (code 11209), may still return HTTP 200 before this mapping. Always check the outer JSON code; malformed requests and infrastructure failures may also return non-200 HTTP responses.

View parameters & response Try online

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.

Open tester

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

Response example

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

No response example is published for this API. Refer to the response fields below.

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	Default HTTP response for both success and many business errors. Only outer JSON code 0 indicates success or asynchronous acceptance; inspect data for the result.
429	Execution admission rate limit; honor Retry-After when present.
503	Execution admission is temporarily unavailable; honor Retry-After when present.
Opt-in	X-Nexscope-Http-Status: semantic maps controller-handled business errors to HTTP status on run and task routes. Pre-authentication failures, such as a missing API key (code 11209), may still return HTTP 200 before this mapping. Always check the outer JSON code; malformed requests and infrastructure failures may also return non-200 HTTP responses.

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_utility_patent_detector",
    "arguments": {
      "productDescription": "A protective smartphone case with a magnetic ring stand and shockproof corners.",
      "productTitle": "Magnetic phone case with ring stand",
      "region": "US",
      "topNumber": 10
    }
  }
}

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_utility_patent_detector

API key*

JSON payload*

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

Image Copyright Check

Compare images with registered works to screen for potential copyright risks.

Design Patent Risk Check

Detect design-patent risks by comparing a product image with patent records across more than 25 jurisdictions.

Prohibited Product Image Check

Compare product images with records of prohibited items to help review listing risks.

Graphic Trademark Check

Find visual matches between product images and registered graphic trademarks.