Nexscope

Patent Claims

Read a patent's claims to understand what the patent covers. Call the Patent Claims API via REST or MCP from 112 credits per call.

CostRecent 10 credits / call
Try online
POST · https://api.nexscope.ai/zy/claimDataMCP · nexscope_patent_claims

What this API does

Read a patent's claims to understand what the patent covers. The request accepts patentId, patentNumber, replaceByRelated. Its documented result includes patentId, pn, pnRelated, claims, claimCount.

Patent Claims API use cases

Investigate a product IP question

To investigate a product ip question, a compliance analyst submits patentId and patentNumber to Patent Claims. The returned patentId, pn, pnRelated help identify records relevant to the proposed product.

Collect records for an IP review

A compliance analyst uses Patent Claims with patentId and patentNumber to collect records for an ip review. The returned patentId, pn, pnRelated help collect bibliographic evidence for a specialist review.

Document evidence for specialist assessment

For this workflow, a compliance analyst calls Patent Claims with patentId and patentNumber to document evidence for specialist assessment. The result helps document the records supporting an IP research question.

Patent Claims API FAQ

What does the Patent Claims API return?

Read a patent's claims to understand what the patent covers. The documented output includes patentId, pn, pnRelated, claims, claimCount. It corresponds to the supplied patentId, patentNumber, replaceByRelated. 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 Claims 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 Claims API from my app or an MCP client?

Send a POST request to https://api.nexscope.ai/zy/claimData 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_patent_claims. 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 creditsConnect this API with MCP

Try this API
Endpoint
https://api.nexscope.ai/zy/claimData
MCP method
nexscope_patent_claims

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/claimData

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/claimData' \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "patentNumber": "CN115000000A"
}'

Code example

{
  "patentNumber": "CN115000000A"
}

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
200Default HTTP response for both success and many business errors. Only outer JSON code 0 indicates success or asynchronous acceptance; inspect data for the result.
429Execution admission rate limit; honor Retry-After when present.
503Execution admission is temporarily unavailable; honor Retry-After when present.
Opt-inX-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.
All categories/ Patent Intelligence ZY
POSThttps://api.nexscope.ai/zy/claimData

Run this API

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

Endpoint

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

Request parameters

NameTypeRequiredDescription
patentIdstringoptional
ZY internal patent ID, multiples separated by English commas, upper limit 100, maximum length 60,000 characters.
patentNumberstringoptional
Public announcement numbers, multiple ones separated by English commas, the upper limit is 100, and the maximum length is 60,000 characters.
replaceByRelatedstringoptional
Whether to replace the current patent claim with a similar patent family when it cannot be obtained: `1` yes, `0` no, the maximum length is 1,000 characters.

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

NameTypeRequiredDescription
totalintegeroptional
Number of records.
dataarrayoptional
Patent List.
columnsarrayoptional
Rendered column definitions.
costTokenintegeroptional
Consume token.
typestringoptional
Rendering style.
patentIdstringoptional
Patent ID.
pnstringoptional
Public (announcement) number.
pnRelatedstringoptional
Publication number of the superseding patent; provided only when a patent family substitution is used.
claimsarrayoptional
Array of claims, containing claim text and metadata.
claimCountintegeroptional
Number of claims.

Responses

CodeDescription
200Default HTTP response for both success and many business errors. Only outer JSON code 0 indicates success or asynchronous acceptance; inspect data for the result.
429Execution admission rate limit; honor Retry-After when present.
503Execution admission is temporarily unavailable; honor Retry-After when present.
Opt-inX-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_patent_claims",
    "arguments": {
      "patentNumber": "US11299876B2"
    }
  }
}

Legacy MCP v1

Existing API-key clients can continue using the compatibility endpoint. New integrations should use MCP v2.

GET / POST /mcp/legacy

Data Example

Request parameters

{
  "patentNumber": "US11205304B2",
  "replaceByRelated": "0"
}

Response

{
  "code": 0,
  "msg": null,
  "data": {
    "total": 1,
    "data": [
      {
        "patentId": "718ead9c-4f3c-4674-8f5a-24e126827269",
        "claims": [
          {
            "data_format": "original",
            "claim_independent_count": 2,
            "claim_text": "<div class=\"indep-clm\" num=\"1\"><seg-con>1. A virtual content rendering system, </seg-con><seg-trans>comprising:</seg-trans></div>\n<div class=\"indep-clm\" num=\"1\"><seg-refi>an optical apparatus comprising at least a light field generation subsystem that includes one or more waveguides and a plurality of curved reflectors or mirrors located in at least one waveguide of the one or more waveguides, wherein</seg-refi></div>\n<div class=\"indep-clm\" num=\"1\"><seg-refi>the light field generation subsystem is configured to render a four-dimensional light field for displaying virtual contents including one or more virtual objects in the four-dimensional light field using the plurality of curved reflectors or mirrors;</seg-refi></div>\n<div class=\"indep-clm\" num=\"1\"><seg-refi>the plurality of curved reflectors or mirrors are located in the at least one waveguide and are configured to refocus light as a plurality of virtual point sources emitting respective spherical waves at a plurality of radial distances for at least a part of the virtual contents; and</seg-refi></div>\n<div class=\"indep-clm\" num=\"1\"><seg-refi>the optical apparatus is configured to project the light associated with the virtual contents that include a virtual user interface to a user;</seg-refi></div>\n<div class=\"indep-clm\" num=\"1\"><seg-refi>a user interface component coupled to the virtual user interface and configured to receive a user input in response to an interaction comprising a pose or movement of the user with at least a feature in the virtual user interface, the user interface component comprising at least one pose or movement tracking device coupled to the light field generation subsystem and positioned in relation to the user; and</seg-refi></div>\n<div class=\"indep-clm\" num=\"1\"><seg-refi>a processor to receive the user input and to determine an action to be performed based at least in part on the user input.</seg-refi></div>\n<div class=\"dep-clm\" num=\"2\" parent=\"1\"><seg-con>2. The virtual content rendering system of claim 1, </seg-con><seg-trans>further comprising:</seg-trans></div>\n<div class=\"dep-clm\" num=\"2\" parent=\"1\"><seg-refi>the light field generation subsystem comprises the plurality of curved reflectors or mirrors that are configured to refocus a first focal distance of light rays corresponding to at least some of the virtual contents into light rays at one or more radial distances of the plurality of radial distances to render the four-dimensional light field for the at least some of the virtual contents.</seg-refi></div>\n<div class=\"dep-clm\" num=\"3\" parent=\"2\"><seg-con>3. The virtual content rendering system of claim 2, </seg-con><seg-trans>wherein </seg-trans><seg-refi>the at least one pose or movement tracking device comprises a sensor, transducer, camera, or light source configured to track at least one characteristic of the user, and the at least one characteristic pertains to only one eye of a pair of eyes of the user.</seg-refi></div>\n<div class=\"dep-clm\" num=\"4\" parent=\"3\"><seg-con>4. The virtual content rendering system of claim 3, </seg-con><seg-trans>wherein </seg-trans><seg-refi>the at least one characteristic pertains to a hand or a totem of the user.</seg-refi></div>\n<div class=\"dep-clm\" num=\"5\" parent=\"3\"><seg-con>5. The virtual content rendering system of claim 3, </seg-con><seg-trans>wherein </seg-trans><seg-refi>the virtual user interface is configured to provide tactile perception or the four-dimensional light field to the user.</seg-refi></div>\n<div class=\"dep-clm\" num=\"6\" parent=\"3\"><seg-con>6. The virtual content rendering system of claim 3, </seg-con><seg-trans>wherein </seg-trans><seg-refi>the at least one characteristic pertains to a head pose or a natural feature pose of the user.</seg-refi></div>\n<div class=\"dep-clm\" num=\"7\" parent=\"3\"><seg-con>7. The virtual content rendering system of claim 3, </seg-con><seg-trans>wherein </seg-trans><seg-refi>the at least one pose or movement tracking device is configured to track the at least one characteristic by using at least a heat map that stores a frequency and a number of instances of the at least one characteristic at one or more virtual or real objects.</seg-refi></div>\n<div class=\"dep-clm\" num=\"8\" parent=\"3\"><seg-con>8. The virtual content rendering system of claim 3, </seg-con><seg-trans>further comprising </seg-trans><seg-refi>one or more light sources emitting the light including pseudo-random noise to the only one eye of the user and one or more image capturing sensors capturing at least reflected light returned from the only one eye of the user for the at least one pose or movement tracking device to track the at least one characteristic.</seg-refi></div>\n<div class=\"dep-clm\" num=\"9\" parent=\"3\"><seg-con>9. The virtual content rendering system of claim 3, </seg-con><seg-trans>wherein </seg-trans><seg-refi>the least one pose or movement tracking device is configured to determine the at least one characteristic pertaining to the only one eye of the user at least by determining a vector distance with geometries of the only one eye, without using cameras.</seg-refi></div>\n<div class=\"dep-clm\" num=\"10\" parent=\"1\"><seg-con>10. The virtual content rendering system of claim 1, </seg-con><seg-trans>wherein </seg-trans><seg-refi>the virtual user interface is rendered relative to a predetermined reference frame.</seg-refi></div>\n<div class=\"dep-clm\" num=\"11\" parent=\"10\"><seg-con>11. The virtual content rendering system of claim 10, </seg-con><seg-trans>wherein </seg-trans><seg-refi>the user interface is configured to receive the user input in response to the interaction of the user based in part or in whole upon one or more transformations between the predetermined reference frame and a first reference frame.</seg-refi></div>\n<div class=\"dep-clm\" num=\"12\" parent=\"10\"><seg-con>12. The virtual content rendering system of claim 10, </seg-con><seg-trans>wherein </seg-trans><seg-refi>the predetermined reference frame is body-centered, world-centered, head-centered, or hand-centered.</seg-refi></div>\n<div class=\"dep-clm\" num=\"13\" parent=\"1\"><seg-con>13. The virtual content rendering system of claim 1, </seg-con><seg-trans>wherein </seg-trans><seg-refi>the virtual user interface is configured to include a first virtual object to which at least one virtual object of the one or more virtual objects is locked in, and projection of the virtual user interface is based at least in part on environmental data.</seg-refi></div>\n<div class=\"dep-clm\" num=\"14\" parent=\"1\"><seg-con>14. The virtual content rendering system of claim 1, </seg-con><seg-trans>further comprising </seg-trans><seg-refi>a database to store a map of the real world, wherein the map comprises coordinates of real objects of the real world, and the projection of the virtual user interface is based at least in part on the stored map.</seg-refi></div>\n<div class=\"dep-clm\" num=\"15\" parent=\"1\"><seg-con>15. The virtual content rendering system of claim 1, </seg-con><seg-trans>wherein </seg-trans><seg-refi>the virtual user interface is rendered as a virtual object of the one or more virtual objects with a first characteristic that provides virtual tactile perception to the user.</seg-refi></div>\n<div class=\"dep-clm\" num=\"16\" parent=\"15\"><seg-con>16. The virtual content rendering system of claim 15, </seg-con><seg-trans>further comprising </seg-trans><seg-refi>one or more sensor that comprise at least one of a camera, a motion-based sensor, a voice-based sensor, and the user interface comprises a gesture detector.</seg-refi></div>\n<div class=\"indep-clm\" num=\"17\"><seg-con>17. A machine implemented method for implementing a virtual user interface for an augmented reality display system, </seg-con><seg-trans>comprising:</seg-trans></div>\n<div class=\"indep-clm\" num=\"17\"><seg-refi>rendering virtual contents including one or more virtual objects in a four-dimensional light field for displaying virtual contents including one or more virtual objects to a user at least by refocusing light as a plurality of virtual point sources emitting respective spherical waves at a plurality of radial distances for at least a part of the virtual contents with a plurality of curved reflectors or mirrors in at least one waveguide of one or more waveguides and projecting the light associated with the one or more virtual objects including a virtual user interface with at least a light field generation subsystem;</seg-refi></div>\n<div class=\"indep-clm\" num=\"17\"><seg-refi>receiving, at a user interface of the augmented reality display apparatus coupled to the virtual user interface, a user input in response to an interaction comprising a pose or movement of the user with at least a virtual feature in the virtual user interface, the interaction captured by at least one pose or movement tracking device of the augmented reality display apparatus; and</seg-refi></div>\n<div class=\"indep-clm\" num=\"17\"><seg-refi>determining an action to be performed based at least in part on the user input.</seg-refi></div>\n<div class=\"dep-clm\" num=\"18\" parent=\"17\"><seg-con>18. The machine implemented method of claim 17, </seg-con><seg-trans>further comprising:</seg-trans></div>\n<div class=\"dep-clm\" num=\"18\" parent=\"17\"><seg-comp>refocusing a first focal distance of light rays corresponding to at least some of the virtual contents to one or more radial distances of the plurality of radial distances to render the four-dimensional light field for the at least some of the virtual contents;</seg-comp></div>\n<div class=\"dep-clm\" num=\"18\" parent=\"17\"><seg-comp>instrumenting the augmented reality apparatus with the at least one pose or movement tracking device that captures only one eye of a pair of eyes of the user; and</seg-comp></div>\n<div class=\"dep-clm\" num=\"18\" parent=\"17\"><seg-comp>capturing a pose or a movement of the only one eye of the user.</seg-comp></div>\n<div class=\"dep-clm\" num=\"19\" parent=\"18\"><seg-con>19. The machine implemented method of claim 18, </seg-con><seg-trans>further comprising:</seg-trans></div>\n<div class=\"dep-clm\" num=\"19\" parent=\"18\"><seg-refi>correlating a received signal from the only one eye of the user with a transmitted signal based in part or in whole upon a vector distance that is determined with geometries of the only one eye of the user, without using cameras.</seg-refi></div>\n<div class=\"dep-clm\" num=\"20\" parent=\"17\"><seg-con>20. The machine implemented method of claim 17, </seg-con><seg-trans>further comprising:</seg-trans></div>\n<div class=\"dep-clm\" num=\"20\" parent=\"17\"><seg-comp>constructing a heat map at least by tracking and recording a time, a frequency, and a number of instances of the interaction of the user; and</seg-comp></div>\n<div class=\"dep-clm\" num=\"20\" parent=\"17\"><seg-comp>tracking the interaction with the heat map.</seg-comp></div>\n",
            "lang": "EN"
          }
        ],
        "claimCount": 20,
        "pn": "US11205304B2"
      }
    ],
    "columns": [
      {
        "filterable": true,
        "cellType": "text",
        "field": "pn",
        "sortable": true,
        "title": "公开(公告)号"
      },
      {
        "filterable": true,
        "cellType": "text",
        "field": "patentId",
        "sortable": true,
        "title": "专利Id"
      },
      {
        "filterable": true,
        "cellType": "text",
        "field": "pnRelated",
        "sortable": true,
        "title": "替代专利的公开号(仅当使用同族专利替代时提供)"
      },
      {
        "filterable": true,
        "cellType": "number",
        "field": "claimCount",
        "sortable": true,
        "title": "权利要求数量"
      },
      {
        "filterable": true,
        "cellType": "text",
        "field": "claims",
        "sortable": true,
        "title": "权利要求"
      }
    ],
    "type": "tableListWorkbenches"
  }
}

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.

Recent 10 credits / callAPI usage records

Try it

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

Endpoint
/zy/claimData
MCP method
nexscope_patent_claims
cURL
curl -X POST \
  https://api.nexscope.ai/zy/claimData \
  -H "Authorization: Bearer nk-..." \
  -H "Content-Type: application/json" \
  -d '{ "patentNumber": "CN115000000A" }'
Response
No response yet. Run the request to see the response here.

Related APIs