Nexscope

Patent Intelligence ZY: query Search Patent API

Use Patent Intelligence ZY: query Search Patent API through Nexscope with documented parameters, structured results and API key authentication.

CostRecent 10 credits / call
Try online
POST · https://api.nexscope.ai/zy/querySearchPatentMCP · nexscope_data_zy_query_search_patent
Patent Intelligence ZY

What this API does

Use Patent Intelligence ZY: query Search Patent API through Nexscope with documented parameters, structured results and API key authentication. The request accepts queryText, limit, offset, sort, stemming. Its documented result includes errcode, errmsg, allRecordsCount, patentId, pn, title, apdt, pbdt.

Patent Intelligence ZY: query Search Patent API API use cases

Investigate a product IP question

To investigate a product ip question, a compliance analyst submits queryText and limit to Patent Intelligence ZY: query Search Patent API. The returned errcode, errmsg, allRecordsCount help identify records relevant to the proposed product.

Collect records for an IP review

A compliance analyst uses Patent Intelligence ZY: query Search Patent API with queryText and limit to collect records for an ip review. The returned errcode, errmsg, allRecordsCount help collect bibliographic evidence for a specialist review.

Document evidence for specialist assessment

For this workflow, a compliance analyst calls Patent Intelligence ZY: query Search Patent API with queryText and limit to document evidence for specialist assessment. The result helps document the records supporting an IP research question.

Patent Intelligence ZY: query Search Patent API API FAQ

What does the Patent Intelligence ZY: query Search Patent API API return?

Use Patent Intelligence ZY: query Search Patent API through Nexscope with documented parameters, structured results and API key authentication. The documented output includes errcode, errmsg, allRecordsCount, patentId, pn, title, apdt, pbdt. It corresponds to the supplied queryText, limit, offset, sort, stemming. 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 Patent Intelligence ZY: query Search Patent API API cost?

The current documented cost is Recent 10 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 Patent Intelligence ZY: query Search Patent API API from my app or an MCP client?

Send a POST request to https://api.nexscope.ai/zy/querySearchPatent 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_zy_query_search_patent. 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/zy/querySearchPatent
MCP method
nexscope_data_zy_query_search_patent

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/zy/querySearchPatent

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/zy/querySearchPatent' \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "limit": 10,
  "queryText": "TACD: virtual reality"
}'

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 Intelligence ZY
POSThttps://api.nexscope.ai/zy/querySearchPatent

Run this API

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

Endpoint

MethodPOST
Pathhttps://api.nexscope.ai/zy/querySearchPatent
AuthBearer API key
Content-Typeapplication/json

Request parameters

NameTypeRequiredDescription
queryTextstringrequired
Analytics search query, up to 12,000 characters, supports field prefixes such as `TACD:`, `TAC:`, `TA:` and `AND`/`OR`/`NOT` Boolean operations.
limitintegeroptional
Returns the number of patents, range 1–1000.
Example: 10
offsetintegeroptional
Offset, range 0–19,999; `limit + offset` cannot exceed 20,000.
Example: 0
sortarrayoptional
Array of sorting conditions, each element is `{field, order}`; `field`: `PBDT_YEARMONTHDAY`, `APD_YEARMONTHDAY`, `ISD`, `SCORE`; `order`: `DESC` or `ASC`.
stemmingintegeroptional
Whether to enable truncation search: `1` is on, `0` is off.
Example: 0
collapseTypestringoptional
Deduplication methods: `ALL`, `APNO`, `DOCDB`, `INPADOC`, `EXTEND`.
Example: ALL
collapseBystringoptional
Deduplication sorting fields: `APD`, `PBD`, `AUTHORITY`, `SCORE`.
collapseOrderstringoptional
Deduplication sort order: `OLDEST` or `LATEST`.
collapseOrderAuthorityarrayoptional
Array of receiving office priority, only valid when `collapseBy=AUTHORITY`.

Code example

{
  "limit": 10,
  "queryText": "TACD: virtual reality"
}

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

NameTypeRequiredDescription
errcodeintegeroptional
Business status, `200` indicates success.
errmsgstringoptional
Success is `ok`, failure is error description.
totalintegeroptional
The number of results returned this time.
dataarrayoptional
Patent List.
columnsarrayoptional
Renders column meta information, not data records.
typestringoptional
Rendering style.
costTokenintegeroptional
Consume token.
allRecordsCountintegeroptional
Retrieve the total number of hits.
patentIdstringoptional
ZY patent ID.
pnstringoptional
Public (announcement) number.
titlestringoptional
Patent title.
apdtintegeroptional
Application date (YYYYMMDD).
pbdtintegeroptional
Open day (YYYYMMDD).
apnostringoptional
Application number.
authoritystringoptional
Receiving Office, such as `US`.
inventorstringoptional
Inventor, multiple people separated by `\|`.
originalAssigneestringoptional
Original applicant, multiple separated by `\|`.
currentAssigneestringoptional
Current applicant, multiple separated by `\|`.

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_zy_query_search_patent",
    "arguments": {
      "limit": 10,
      "queryText": "TACD: virtual reality"
    }
  }
}

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.

12 credits / callAPI usage records

Try it

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

Endpoint
/zy/querySearchPatent
MCP method
nexscope_data_zy_query_search_patent
cURL
curl -X POST \
  https://api.nexscope.ai/zy/querySearchPatent \
  -H "Authorization: Bearer nk-..." \
  -H "Content-Type: application/json" \
  -d '{ "limit": 10, "queryText": "TACD: virtual reality" }'
Response
No response yet. Run the request to see the response here.

Related APIs