Nexscope Patent Legal Status
This skill guides you on how to query patent legal status information via the Nexscope (Nexscope) platform, helping users quickly determine the current legal standing and event history of a single patent.
Invocation
- API Endpoint:
POST /zhihuiya/legalStatus (full parameters/response/error codes in references/api.md)
- Python Script:
python scripts/patent_legal_status_data.py '<JSON params>' [--inline]
- Cost Constraints: This tool consumes credits. The same parameter combination defaults to a single call per session. The script includes a 24-hour local cache. Do not automatically retry with different keywords, pagination, or modified parameters on failure or empty results; inform the user that additional costs will be incurred before continuing to search. Skill single-patent policy: This endpoint consumes credits. This Skill uses one patent per call to control credits. For multiple patents, obtain explicit user consent before separate calls; the gateway supports up to 100 per request.
Output Strategy (default script behavior):
- Always write the full response to
<cwd>/nexscope/<YYYY-MM-DD>/<session>/data/nexscope-zhihuiya-legal-status-<timestamp>.json (<cwd> is the working directory at script execution time, which in Claude Code is the current project directory; <session> is taken from the SESSION_ID environment variable, auto-grouped by user task; writing to /tmp is forbidden -- error if the current directory is not writable)
- Response body <= 8 KB: print the full JSON to stdout after writing to disk
- Response body > 8 KB: print only a summary to stdout after writing to disk (top-level fields, common counts like
total/costToken, length of the largest list field + first 3 samples)
- Add
--inline to force full output to stdout (still writes to disk)
Data Reading Tip: Check the summary first to determine if it is sufficient; when specific fields are needed, prefer using jq or ConvertFrom-Json to extract from the saved JSON file on demand to avoid loading the entire JSON into context.
Authentication
Set NEXSCOPE_API_KEY. Visit https://www.nexscope.ai/help/skills-external-access?co-from=skillNS to manage credits.
Core Concepts
The Nexscope Patent Legal Status tool returns three layers of legal information for each patent:
- Simple Legal Status -- A high-level summary of the patent's current standing (e.g., Active, Inactive, Pending, Undetermined, PCT designated period, PCT designated expiration).
- Legal Status -- A detailed status describing the patent's lifecycle stage (e.g., Published, Examining, Granted, Abandoned, Withdrawn, Rejected, Expired, Revoked, Ceased, Restoration, etc.).
- Legal Events -- Specific legal actions that have occurred on the patent (e.g., Transfer, License, Pledge, Opposition, Litigation, Re-examination, Customs, Preservation, Invalid-procedure, Oral-procedure, Declassification, Double application, Trust).
Patent identification: Patents can be looked up by either patent ID or publication (announcement) number. When both are provided, patent ID takes priority. This Skill sends one patent per call to control credits; the gateway accepts up to 100 per request.
Parameter Guide
| Parameter |
Required |
Description |
| patentId |
Conditionally |
Patent ID. At least one of patentId or patentNumber must be provided. This Skill sends one patent ID per call; the gateway accepts up to 100 comma-separated IDs. |
| patentNumber |
Conditionally |
Publication (announcement) number. At least one of patentId or patentNumber must be provided. This Skill sends one publication number per call; the gateway accepts up to 100 comma-separated numbers. |
- If the user provides a publication number (e.g., CN115xxxxxxA, US11xxxxxxB2, EP3xxxxxxA1), use
patentNumber.
- If the user provides an internal patent ID, use
patentId.
- When both are supplied,
patentId takes precedence.
Skill single-patent policy: This endpoint consumes credits. If you need to check multiple patents, you must obtain explicit user consent and make separate requests. This Skill uses one patent per call; the gateway supports up to 100 English comma-separated identifiers.
Response Fields
| Field |
Description |
| patentId |
The patent's internal ID |
| pn |
Publication (announcement) number |
| simpleLegalStatus |
High-level status: Active, Inactive, Pending, Undetermined, PCT designated period, PCT designated expiration |
| legalStatus |
Detailed lifecycle status (Published, Examining, Granted, Abandoned, Withdrawn, Rejected, Expired, Revoked, Ceased, etc.) |
| eventStatus |
Legal events (Transfer, License, Pledge, Opposition, Litigation, Re-examination, etc.) |
| legalDate |
Date of the most recent legal status update |
Usage Examples
1. Check whether a single patent is still active
Query the legal status for patent publication number CN115000000A.
2. Identify legal events on a patent
Has patent CN115000000A been involved in any litigation, transfer, or pledge events?
3. Determine if a patent has expired or been revoked
Check if patent US10000000B1 is expired, revoked, or still in force.
Display Rules
- Present data clearly: Show results in a structured table. Include the publication number, simple legal status, detailed legal status, and legal events for each patent.
- Translate status values: When the user's language preference is clear, present status labels in that language while keeping the canonical English value in parentheses for precision.
- Highlight key findings: If the user is checking validity, prominently state whether each patent is Active, Inactive, or Pending at the top of the response.
- Legal date context: When
legalDate is available, include it so users know how recent the status information is.
- Error handling: If the query fails or returns no results, explain the possible reasons (invalid patent number format, patent not found in database) and suggest the user double-check the input.
- Single patent result: Results contain a single patent's data.
Important Limitations
- Skill request policy: This Skill uses one patent per call to control credits; the gateway accepts up to 100 English comma-separated identifiers.
- At least one identifier required: Either
patentId or patentNumber must be provided; the request will fail if both are empty.
- Patent ID priority: When both
patentId and patentNumber are provided, the system uses patentId and ignores patentNumber.
- Data coverage: Results depend on the Nexscope (Nexscope) database coverage; some very recent filings may not yet be reflected.
User Expression & Scenario Quick Reference
Applicable -- Queries about patent legal standing and events:
| User Says |
Scenario |
| "Is this patent still valid/active" |
Simple legal status check |
| "What is the legal status of patent XX" |
Detailed status lookup |
| "Has this patent been transferred or licensed" |
Legal event query |
| "Any litigation on this patent" |
Legal event filtering |
| "Patent legal status for CN115XXXXXXA" |
Direct publication number lookup |
Not applicable -- Needs beyond patent legal status:
- Patent search by keyword, classification, or applicant name
- Patent full-text or claims retrieval
- Patent valuation or commercial analysis
- Freedom-to-operate (FTO) analysis
- Patent family or citation analysis
API Key request rate
All Nexscope API Keys belonging to the same user share one request-rate allowance for public API execution. The allowance is measured over any rolling 1-second window. Your RPS depends on your account entitlements; do not assume every user has a fixed 1 RPS. A single Skill operation may make multiple public API requests, and each request uses this allowance.
If an execution request returns HTTP 429 with outer code 13012, the request-rate allowance was exceeded. Honor the returned Retry-After before considering another request. Outer code 13013 means the concurrent-request limit was exceeded, not the rate limit; honor its Retry-After when supplied. Inspect the response and reconcile state before retrying. Never automatically replay a write operation or a request whose outcome is unclear.
1---2name: ecommerce-patent-legal-status-data3description: Query patent legal status information from the Nexscope (Nexscope) database. Triggered when users mention patent legal status, patent validity check, patent status query, patent event history, simple legal status, legal events such as transfer, license, pledge, opposition, litigation, re-examination, patent legal status, patent validity, patent events, transfer/license/pledge, Nexscope, or patent status lookup. Also triggered when users ask whether a patent is active, inactive, pending, expired, granted, withdrawn, or revoked, or want to look up legal status by patent ID or publication number.4metadata:5 source: https://skillmd.com/skills/nexscope-ai/ecommerce-patent-legal-status-data6---78# Nexscope Patent Legal Status910This skill guides you on how to query patent legal status information via the Nexscope (Nexscope) platform, helping users quickly determine the current legal standing and event history of a single patent.1112## Invocation1314- **API Endpoint**: `POST /zhihuiya/legalStatus` (full parameters/response/error codes in `references/api.md`)15- **Python Script**: `python scripts/patent_legal_status_data.py '<JSON params>' [--inline]`16- **Cost Constraints**: This tool consumes credits. The same parameter combination defaults to a single call per session. The script includes a 24-hour local cache. Do not automatically retry with different keywords, pagination, or modified parameters on failure or empty results; inform the user that additional costs will be incurred before continuing to search. **Skill single-patent policy**: This endpoint consumes credits. This Skill uses one patent per call to control credits. For multiple patents, obtain explicit user consent before separate calls; the gateway supports up to 100 per request.1718**Output Strategy (default script behavior)**:19- **Always** write the full response to `<cwd>/nexscope/<YYYY-MM-DD>/<session>/data/nexscope-zhihuiya-legal-status-<timestamp>.json` (`<cwd>` is the working directory at script execution time, which in Claude Code is the current project directory; `<session>` is taken from the `SESSION_ID` environment variable, auto-grouped by user task; **writing to /tmp is forbidden** -- error if the current directory is not writable)20- Response body <= 8 KB: print the full JSON to stdout after writing to disk21- Response body > 8 KB: print only a summary to stdout after writing to disk (top-level fields, common counts like `total`/`costToken`, length of the largest list field + first 3 samples)22- Add `--inline` to force full output to stdout (still writes to disk)2324**Data Reading Tip**: Check the summary first to determine if it is sufficient; when specific fields are needed, prefer using `jq` or `ConvertFrom-Json` to extract from the saved JSON file on demand to avoid loading the entire JSON into context.2526## Authentication2728Set `NEXSCOPE_API_KEY`. Visit https://www.nexscope.ai/help/skills-external-access?co-from=skillNS to manage credits.2930## Core Concepts3132The Nexscope Patent Legal Status tool returns three layers of legal information for each patent:33341. **Simple Legal Status** -- A high-level summary of the patent's current standing (e.g., Active, Inactive, Pending, Undetermined, PCT designated period, PCT designated expiration).352. **Legal Status** -- A detailed status describing the patent's lifecycle stage (e.g., Published, Examining, Granted, Abandoned, Withdrawn, Rejected, Expired, Revoked, Ceased, Restoration, etc.).363. **Legal Events** -- Specific legal actions that have occurred on the patent (e.g., Transfer, License, Pledge, Opposition, Litigation, Re-examination, Customs, Preservation, Invalid-procedure, Oral-procedure, Declassification, Double application, Trust).3738**Patent identification**: Patents can be looked up by either patent ID or publication (announcement) number. When both are provided, patent ID takes priority. This Skill sends one patent per call to control credits; the gateway accepts up to 100 per request.3940## Parameter Guide4142| Parameter | Required | Description |43|-----------|----------|-------------|44| patentId | Conditionally | Patent ID. At least one of patentId or patentNumber must be provided. This Skill sends one patent ID per call; the gateway accepts up to 100 comma-separated IDs. |45| patentNumber | Conditionally | Publication (announcement) number. At least one of patentId or patentNumber must be provided. This Skill sends one publication number per call; the gateway accepts up to 100 comma-separated numbers. |4647- If the user provides a publication number (e.g., CN115xxxxxxA, US11xxxxxxB2, EP3xxxxxxA1), use `patentNumber`.48- If the user provides an internal patent ID, use `patentId`.49- When both are supplied, `patentId` takes precedence.5051> **Skill single-patent policy**: This endpoint consumes credits. If you need to check multiple patents, you must obtain explicit user consent and make separate requests. This Skill uses one patent per call; the gateway supports up to 100 English comma-separated identifiers.5253## Response Fields5455| Field | Description |56|-------|-------------|57| patentId | The patent's internal ID |58| pn | Publication (announcement) number |59| simpleLegalStatus | High-level status: Active, Inactive, Pending, Undetermined, PCT designated period, PCT designated expiration |60| legalStatus | Detailed lifecycle status (Published, Examining, Granted, Abandoned, Withdrawn, Rejected, Expired, Revoked, Ceased, etc.) |61| eventStatus | Legal events (Transfer, License, Pledge, Opposition, Litigation, Re-examination, etc.) |62| legalDate | Date of the most recent legal status update |6364## Usage Examples6566**1. Check whether a single patent is still active**67```68Query the legal status for patent publication number CN115000000A.69```7071**2. Identify legal events on a patent**72```73Has patent CN115000000A been involved in any litigation, transfer, or pledge events?74```7576**3. Determine if a patent has expired or been revoked**77```78Check if patent US10000000B1 is expired, revoked, or still in force.79```8081## Display Rules82831. **Present data clearly**: Show results in a structured table. Include the publication number, simple legal status, detailed legal status, and legal events for each patent.842. **Translate status values**: When the user's language preference is clear, present status labels in that language while keeping the canonical English value in parentheses for precision.853. **Highlight key findings**: If the user is checking validity, prominently state whether each patent is Active, Inactive, or Pending at the top of the response.864. **Legal date context**: When `legalDate` is available, include it so users know how recent the status information is.875. **Error handling**: If the query fails or returns no results, explain the possible reasons (invalid patent number format, patent not found in database) and suggest the user double-check the input.886. **Single patent result**: Results contain a single patent's data.8990## Important Limitations9192- **Skill request policy**: This Skill uses one patent per call to control credits; the gateway accepts up to 100 English comma-separated identifiers.93- **At least one identifier required**: Either `patentId` or `patentNumber` must be provided; the request will fail if both are empty.94- **Patent ID priority**: When both `patentId` and `patentNumber` are provided, the system uses `patentId` and ignores `patentNumber`.95- **Data coverage**: Results depend on the Nexscope (Nexscope) database coverage; some very recent filings may not yet be reflected.9697## User Expression & Scenario Quick Reference9899**Applicable** -- Queries about patent legal standing and events:100101| User Says | Scenario |102|-----------|----------|103| "Is this patent still valid/active" | Simple legal status check |104| "What is the legal status of patent XX" | Detailed status lookup |105| "Has this patent been transferred or licensed" | Legal event query |106| "Any litigation on this patent" | Legal event filtering |107| "Patent legal status for CN115XXXXXXA" | Direct publication number lookup |108109**Not applicable** -- Needs beyond patent legal status:110111- Patent search by keyword, classification, or applicant name112- Patent full-text or claims retrieval113- Patent valuation or commercial analysis114- Freedom-to-operate (FTO) analysis115- Patent family or citation analysis116117## API Key request rate118119All Nexscope API Keys belonging to the same user share one request-rate allowance for public API execution. The allowance is measured over any rolling 1-second window. Your RPS depends on your account entitlements; do not assume every user has a fixed 1 RPS. A single Skill operation may make multiple public API requests, and each request uses this allowance.120121If an execution request returns HTTP 429 with outer code `13012`, the request-rate allowance was exceeded. Honor the returned `Retry-After` before considering another request. Outer code `13013` means the concurrent-request limit was exceeded, not the rate limit; honor its `Retry-After` when supplied. Inspect the response and reconcile state before retrying. Never automatically replay a write operation or a request whose outcome is unclear.