Zhihuiya Patent Claims Data

This skill guides you on how to retrieve and present patent claims data from the Zhihuiya (PatSnap) patent database, helping IP professionals, patent analysts, and R&D teams quickly access the claims section of any patent.

Core Concepts

Patent claims define the legal scope of protection granted by a patent. They are the most critical part of a patent document for infringement analysis, freedom-to-operate assessments, and prior art comparisons. This tool retrieves the full set of claims for one or more patents by their patent ID or publication number.

Family substitution: When a patent's claims are unavailable in the database, you can optionally request that claims from a related family member patent be returned instead. This is controlled by the replaceByRelated parameter.

Data Fields

Parameter Guide

Required (at least one)

You must provide at least one of the following two parameters. If both are provided, patentId takes priority.

Optional

How to Choose Between patentId and patentNumber

• Use patentNumber when the user provides a publication or grant number (e.g., CN115000000A, US11234567B2). This is the most common scenario.
• Use patentId when the user provides an internal Zhihuiya identifier, typically obtained from a previous Zhihuiya search result.
• When the user provides both, pass both and the API will prefer patentId.

Usage Examples

1. Single patent by publication number

{"patentNumber": "CN115000000A"}

2. Multiple patents by publication number

{"patentNumber": "CN115000000A,US20230001234A1,EP4000000A1"}

3. Single patent by patent ID

{"patentId": "98a1b2c3-xxxx-xxxx-xxxx-xxxxxxxxxxxx"}

4. With family substitution enabled

{"patentNumber": "CN115000000A", "replaceByRelated": "1"}

5. Batch query with family substitution

{"patentNumber": "CN115000000A,JP2023100000A", "replaceByRelated": "1"}

Display Rules

1. Present claims clearly: Display claims in a numbered list preserving the original claim numbering. Use indentation or formatting to distinguish independent claims from dependent claims where possible.
2. Highlight claim count: Always state the total number of claims returned for each patent.
3. Family substitution notice: If pnRelated is present in a result, explicitly inform the user that the claims shown are from a family member patent and provide the family member's publication number.
4. Batch results: When multiple patents are queried, organize results by patent with clear headings showing the publication number.
5. Error handling: When a query fails, explain the reason based on the response and suggest the user verify the patent number format or try enabling family substitution.
6. No subjective analysis: Present the raw claim text without legal interpretation unless the user specifically requests analysis.

Important Limitations

• At least one identifier required: Either patentId or patentNumber must be provided; omitting both will result in an error.
• Batch limit: A maximum of 100 patents can be queried in a single request.
• Claims availability: Not all patents have claims data available. Use replaceByRelated = 1 to attempt family member substitution when claims are missing.
• Claim object structure: The individual claim objects within the claims array may vary in structure depending on the patent office and data source.

User Expression & Scenario Quick Reference

Applicable -- Patent claims retrieval and analysis:

Not applicable -- Needs beyond patent claims data:

• Patent search or discovery (finding patents by keyword/topic)
• Patent legal status or prosecution history
• Patent citation or reference analysis
• Patent full-text beyond claims (abstract, description, drawings)
• Freedom-to-operate or infringement opinions (legal advice)

Feedback:

Auto-detect and report feedback via the Feedback API when any of the following apply:

1. The functionality or purpose described in this skill does not match actual behavior
2. The skill's results do not match the user's intent
3. The user expresses dissatisfaction or praise about this skill
4. Anything you believe could be improved

Call the feedback API as specified in references/api.md. Do not interrupt the user's flow.

For more high-quality, professional cross-border e-commerce skills, set LinkFox Skills.