Nexscope

Patent Description Data API

REST API and MCP service documentation generated from server-side API definitions. Responses use the shared code, msg, and data envelope.

API selector
Patent & IP Risk

API overview

Retrieve patent specification text from the Zhihuiya database by patent ID or publication number. View request parameters, response fields, and MCP usage.

Try this API
Endpoint
https://api.nexscope.ai/api/skill-api/v1/skills/patent-description-data/run
MCP method
nexscope_patent_description_data

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 .
POSThttps://api.nexscope.ai/api/skill-api/v1/skills/patent-description-data/run

Run an API

Request parameters documented by ecommerce.patent-description-data.

Slugpatent-description-data
HeadersAuthorization: Bearer nk-...
Content-Type: application/json
Request bodyAPI-specific JSON object.
Response bodyPlatform envelope: code, msg, data, ts, time, cost, traceId. Inspect data.status for asynchronous completion.

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.

Example request

curl -X POST https://api.nexscope.ai/api/skill-api/v1/skills/patent-description-data/run \
  -H "Authorization: Bearer nk-xxxxxxxxxxxxxxxxx" \
  -H "Content-Type: application/json" \
  -d '{   "patentNumber": "US11299876B2" }'
All categories/ Patent & IP Risk
POSThttps://api.nexscope.ai/api/skill-api/v1/skills/patent-description-data/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/patent-description-data/run
AuthBearer API key
Content-Typeapplication/json

Request body

NameTypeRequiredDescription
patentIdstringoptional
Patent ID (at least one of patentId and patentNumber must be provided; if both are present, patentId takes priority). Only a single value is supported; multiple values separated by commas are not allowed. Max length: 60000 characters.
patentNumberstringoptional
Publication/grant number (at least one of patentId and patentNumber must be provided; if both are present, patentId takes priority). Only a single value is supported; multiple values separated by commas are not allowed. Max length: 60000 characters.
Example: US11299876B2
replaceByRelatedstringoptional
Whether to substitute with a family patent's description when the current patent's description is unavailable: 1 Yes, 0 No. Max length: 1000 characters.

Request example

{
  "patentNumber": "US11299876B2"
}

Response body

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

Any of option 1

NameTypeRequiredDescription
dataobjectrequired
Data value used by this API operation.
data.totalintegeroptional
Number of patent records returned
Example: 1
data.dataarrayoptional
Patent list, each element contains description data
Example: []
data.data[].patentIdstringoptional
Patent ID
Example: example-id
data.data[].pnstringoptional
Publication (grant) number
Example: null
data.data[].pnRelatedstringoptional
Publication number of the substitute patent (only provided when family patent substitution is used)
Example: null
data.data[].descriptionarrayoptional
Description content sections
Example: []
data.columnsarrayoptional
Column definitions for rendering
Example: []
data.costTokenintegeroptional
Tokens consumed
Example: 1
data.typestringoptional
Render style
Example: null
data.titlestringoptional
Provider-specific response title.
Example: null
data.sourceTypestringoptional
Provider-specific source platform type.
Example: null
data.sourceToolstringoptional
Provider-specific source tool name.
Example: null
data.costTimeintegeroptional
Execution time reported by the upstream provider.
Example: null
data.pageintegeroptional
Current page returned by the upstream provider.
Example: null
data.pageSizeintegeroptional
Page size returned by the upstream provider.
Example: null
data.pageItemCountintegeroptional
Item count on the current page returned by the upstream provider.
Example: null
data.totalPageintegeroptional
Total page count returned by the upstream provider.
Example: null
data.dataSnapshotMonthstringoptional
Data snapshot month returned by the upstream provider.
Example: null

Any of option 2

NameTypeRequiredDescription
datanullrequired
Data value used by this API operation.

Response example

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

{
  "data": {
    "total": 1,
    "data": [
      {
        "patentId": "example-id",
        "description": []
      }
    ],
    "columns": [],
    "costToken": 1
  },
  "code": 0,
  "msg": null,
  "ts": "0",
  "time": "2026-01-01 00:00:00",
  "cost": "-1",
  "traceId": null
}

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.

Related APIs

MCP

Use the MCP endpoint when an agent needs to discover and call API tools with JSON-RPC.

GET /api/skill-api/v1/mcp
POST /api/skill-api/v1/mcp
Authorization: Bearer nk-xxxxxxxxxxxxxxxxx
Content-Type: application/json

Call a tool

{
  "jsonrpc": "2.0",
  "id": "tool-call-1",
  "method": "tools/call",
  "params": {
    "name": "nexscope_patent_description_data",
    "arguments": {
      "patentNumber": "US11299876B2"
    }
  }
}

Online test

Execute the current API with your API key and JSON payload.

112 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/patent-description-data/run
MCP method
nexscope_patent_description_data
cURL
curl -X POST \
  https://api.nexscope.ai/api/skill-api/v1/skills/patent-description-data/run \
  -H "Authorization: Bearer nk-..." \
  -H "Content-Type: application/json" \
  -d '{ "patentNumber": "US11299876B2" }'
Response
No response yet. Run the request to see the response here.