Patent & IP Risk

Patent Description Data

Retrieve patent description (specification) data from the Nexscope patent database by patent ID or publication number. Triggered when users mention patent specification, patent full text, patent technical description, patent embodiment details, Nexscope specification data, patent specification, patent full text, technical description, embodiment details, Nexscope, or patent detailed description. Even if the user does not explicitly say "Nexscope," this skill should be triggered whenever they need to view the complete specification/description content of one or more patents.

post/api/skill-api/v1/skills/patent-description-data/run

Request

  • Base URL: https://api.nexscope.ai
  • URL: https://api.nexscope.ai/api/skill-api/v1/skills/patent-description-data/run
  • Auth: HTTP bearer

Headers

X-Nexscope-Http-Status'legacy' | 'semantic'

Use semantic for HTTP error statuses on run and task-result requests. Without this header v1 retains legacy status behavior. The JSON envelope is unchanged; code 0 means success or acceptance, not asynchronous completion.

Request body

patentIdstring

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.

patentNumberstring

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.

replaceByRelatedstring

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.

Example request

{
  "patentNumber": "US11299876B2"
}

Response

Successful response.

codeinteger required

0 means accepted or successful; nonzero is a platform error.

msgstring nullable required
tsstring required

Epoch milliseconds.

timestring required

Server local time: yyyy-MM-dd HH:mm:ss.

coststring required

Elapsed milliseconds, never credits; -1 outside web requests.

traceIdstring nullable required

Example response

{
  "data": {
    "total": 1,
    "data": [],
    "costToken": 1
  }
}

Changes

No recorded changes to this operation across all 1 revision of this API.