Nexscope

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/api/skill-api/v1/skills/utility-patent-detector/runMCP · nexscope_utility_patent_detector
Patent & IP Risk

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 applicantAddresses, applicants, applicationDate, applicationNumber, claims, claimsCn, classNumList, cpcKindRaw.

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 applicantAddresses, applicants, applicationDate 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 applicantAddresses, applicants, applicationDate 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 applicantAddresses, applicants, applicationDate, applicationNumber, claims, claimsCn, classNumList, cpcKindRaw. 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/api/skill-api/v1/skills/utility-patent-detector/run 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. 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/api/skill-api/v1/skills/utility-patent-detector/run
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/api/skill-api/v1/skills/utility-patent-detector/run

Run an API

Request parameters documented by ecommerce.utility-patent-detector.

Example request

Replace YOUR_API_KEY, then run this command in your terminal.

curl -X POST 'https://api.nexscope.ai/api/skill-api/v1/skills/utility-patent-detector/run' \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "productDescription": "A protective smartphone case with a magnetic ring stand and shockproof corners.",
  "productTitle": "Magnetic phone case with ring stand",
  "region": "US",
  "topNumber": 10
}'

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/ Patent & IP Risk
POSThttps://api.nexscope.ai/api/skill-api/v1/skills/utility-patent-detector/run

Run this API

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

Endpoint

MethodPOST
Pathhttps://api.nexscope.ai/api/skill-api/v1/skills/utility-patent-detector/run
AuthBearer API key
Content-Typeapplication/json

Request parameters

NameTypeRequiredDescription
productTitlestringrequired
Product title, max 1000 characters
Example: Magnetic phone case with ring stand
productDescriptionstringrequired
Product description, max 1000 characters
Example: A protective smartphone case with a magnetic ring stand and shockproof corners.
regionstringrequired
Country/region code(s) where the product is intended for sale, multiple separated by commas. Currently supports US. Default US
Example: US
topNumberintegerrequired
Number of results to recall, range: 10--200, default 100
Example: 10

Code example

{
  "productDescription": "A protective smartphone case with a magnetic ring stand and shockproof corners.",
  "productTitle": "Magnetic phone case with ring stand",
  "region": "US",
  "topNumber": 10
}

Response example

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

{
  "code": 0,
  "cost": "-1",
  "data": {
    "columns": [],
    "costToken": 1,
    "data": [
      {
        "applicantAddresses": [],
        "applicants": [],
        "applicationDate": "2026-01-01",
        "classNumList": [],
        "cpcKindRaw": [],
        "estimatedDueDate": "2026-01-01",
        "globalUtilityId": "example-id",
        "images": [],
        "inventorAddresses": [],
        "inventors": [],
        "patentImageUrl": "https://example.com/image.jpg",
        "priorityNumber": [],
        "publicationDate": "2026-01-01",
        "region": "US",
        "relatedPublicationDate": [],
        "similarity": 1,
        "troCase": false,
        "troHolder": false
      }
    ],
    "detectId": "example-id",
    "total": 1
  },
  "msg": null,
  "time": "2026-01-01 00:00:00",
  "traceId": null,
  "ts": "0"
}

Response fields

NameTypeRequiredDescription
codeintegerrequired
0 means accepted or successful; nonzero is a platform error.
coststringrequired
Elapsed milliseconds, never credits; -1 outside web requests.
dataanyrequired
Data value used by this API operation.
msgstring | nullrequired
Msg value used by this API operation.
timestringrequired
Server local time: yyyy-MM-dd HH:mm:ss.
traceIdstring | nullrequired
Trace id value used by this API operation.
tsstringrequired
Epoch milliseconds.

Any of option 1

NameTypeRequiredDescription
dataobjectrequired
Data value used by this API operation.
data.columnsarrayoptional
Render column definitions
Example: []
data.costTimeintegeroptional
Execution time reported by the upstream provider.
Example: null
data.costTokenintegeroptional
Token cost
Example: 1
data.dataarrayoptional
Patent list (see below)
Example: []
data.data[]objectrequired
Item in data data.
data.data[].applicantAddressesarrayoptional
Rights holder addresses, array format
Example: []
data.data[].applicantsarrayoptional
Applicants and countries concatenated, array format
Example: []
data.data[].applicationDatestringoptional
Application date (yyyy-MM-dd)
Example: 2026-01-01
data.data[].applicationNumberstringoptional
Application number
Example: null
data.data[].claimsstringoptional
Claims
Example: null
data.data[].claimsCnstringoptional
Claims (Chinese)
Example: null
data.data[].classNumListarrayoptional
Classification number path list, format: classNum1 > classNum2 > classNum3
Example: []
data.data[].cpcKindRawarrayoptional
CPC classification (raw JSONArray)
Example: []
data.data[].estimatedDueDatestringoptional
Estimated expiration date (yyyy-MM-dd)
Example: 2026-01-01
data.data[].globalUtilityIdstringoptional
Patent ID
Example: example-id
data.data[].imagesarrayoptional
Patent drawings
Example: []
data.data[].inventorAddressesarrayoptional
Inventor addresses, array format
Example: []
data.data[].inventorsarrayoptional
Inventors and countries concatenated, array format
Example: []
data.data[].patentAbstractstringoptional
Abstract
Example: null
data.data[].patentAbstractCnstringoptional
Abstract (Chinese)
Example: null
data.data[].patentImageUrlstringoptional
Patent cover image
Example: https://example.com/image.jpg
data.data[].patentValiditystringoptional
Patent validity: Active or Invalid
Example: null
data.data[].priorityNumberarrayoptional
Priority numbers, array format
Example: []
data.data[].publicationDatestringoptional
Publication date (yyyy-MM-dd)
Example: 2026-01-01
data.data[].publicationNumberstringoptional
Publication number
Example: null
data.data[].regionstringoptional
Receiving office
Example: US
data.data[].relatedPublicationDatearrayoptional
First publication dates (yyyy-MM-dd), array format
Example: []
data.data[].similaritynumberoptional
Similarity between the product and this patent (0--1)
Example: 1
data.data[].specificationstringoptional
Specification
Example: null
data.data[].specificationCnstringoptional
Specification (Chinese)
Example: null
data.data[].titlestringoptional
Utility patent title
Example: null
data.data[].titleCnstringoptional
Utility patent title (Chinese)
Example: null
data.data[].troCasebooleanoptional
Whether there is a TRO enforcement history
Example: false
data.data[].troHolderbooleanoptional
Whether it is a patent of a TRO rights holder
Example: false
data.dataSnapshotMonthstringoptional
Data snapshot month returned by the upstream provider.
Example: null
data.detectIdstringoptional
Detection ID
Example: example-id
data.pageintegeroptional
Current page returned by the upstream provider.
Example: null
data.pageItemCountintegeroptional
Item count on the current page returned by the upstream provider.
Example: null
data.pageSizeintegeroptional
Page size returned by the upstream provider.
Example: null
data.sourceToolstringoptional
Provider-specific source tool name.
Example: null
data.sourceTypestringoptional
Provider-specific source platform type.
Example: null
data.titlestringoptional
Provider-specific response title.
Example: null
data.totalintegeroptional
Record count
Example: 1
data.totalPageintegeroptional
Total page count returned by the upstream provider.
Example: null
data.typestringoptional
Render style
Example: null

Any of option 2

NameTypeRequiredDescription
datanullrequired
Data value used by this API operation.

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/api/skill-api/v2/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 /api/skill-api/v1/mcp

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
https://api.nexscope.ai/api/skill-api/v1/skills/utility-patent-detector/run
MCP method
nexscope_utility_patent_detector
cURL
curl -X POST \
  https://api.nexscope.ai/api/skill-api/v1/skills/utility-patent-detector/run \
  -H "Authorization: Bearer nk-..." \
  -H "Content-Type: application/json" \
  -d '{ "productDescription": "A protective smartphone case with a magnetic ring stand and shockproof corners.", "productTitle": "Magnetic phone case with ring stand", "region": "US", "topNumber": 10 }'
Response
No response yet. Run the request to see the response here.

Related APIs