This skill guides you on how to query simple bibliographic data for patents using the Zhihuiya patent database, helping users retrieve structured patent metadata efficiently.
Core Concepts
The Zhihuiya Simple Bibliography tool retrieves basic bibliographic (front-page) information for patents. Given one or more patent IDs or publication numbers, it returns structured metadata including title, abstract, applicants, inventors, assignees, classification codes, filing dates, priority claims, and citation references.
Lookup modes: You can look up patents by either patentId (Zhihuiya internal patent ID) or patentNumber (public publication/grant number). If both are supplied, patentId takes priority. Multiple values are separated by commas, with a maximum of 100 per request.
Parameter Guide
| Parameter | Type | Required | Description |
|---|---|---|---|
| patentId | string | Conditionally | Zhihuiya internal patent ID. Comma-separated for multiple values, max 100. At least one of patentId or patentNumber must be provided. |
| patentNumber | string | Conditionally | Public publication/grant number (e.g., US11234567B2, CN115000000A). Comma-separated for multiple values, max 100. At least one of patentId or patentNumber must be provided. |
Priority rule: When both patentId and patentNumber are present, the API uses patentId and ignores patentNumber.
Response Data Fields
| Field | API Name | Description |
|---|---|---|
| Patent ID | patentId | Zhihuiya internal patent identifier |
| Title | title | Patent title |
| Abstract | abstractContent | Patent abstract text |
| Publication Number | publicationNumber | Publication number |
| Publication/Grant Number | pn | Full publication/grant number |
| Country Code | country | Country code of the patent |
| Publication Country | publicationCountry | Country where the patent was published |
| Publication Date | publicationDate | Publication date |
| Publication Kind | publicationKind | Kind code of the publication |
| Patent Type | patentType | Type of patent (e.g., invention, utility model, design) |
| Kind Code | kind | Patent kind code |
| Application Number | applicationNo | Application number |
| Application Date | applicationDate | Application filing date |
| Applicants | applicants | List of applicants |
| Inventors | inventors | List of inventors |
| Assignees | assignees | List of patent assignees/owners |
| Assignee Addresses | assigneeAddresses | List of assignee addresses |
| IPC Main | ipcMain | Main IPC classification code |
| IPC Further | ipcFurther | Additional IPC classification codes |
| CPC Main | cpcMain | Main CPC classification code |
| CPC Further | cpcFurther | Additional CPC classification codes |
| LOC | loc | Locarno classification codes (design patents) |
| GBC | gbc | GBC classification codes |
| Priority Claims | priorityClaims | List of priority claim entries |
| PCT Application No | pctApplicationNo | PCT international application number |
| PCT Filing Date | pctFilingDate | PCT international filing date |
| PCT Entry Date | pctEntryDate | PCT national phase entry date |
| Cited Patents | citedPatents | List of cited patent references |
| Cited Non-Patents | citedNonPatents | List of cited non-patent literature |
How to call
- API endpoint：
POST /zhihuiya/simpleBibliography(for full parameters/responses/error codes seereferences/api.md） - Python script：
python scripts/zhihuiya_simple_bibliography.py '<JSON 参数>' [--inline] - Cost constraints: This tool consumes compute; within the same session, the same parameter combination is by default called only once, and the script has a 24h local cache. On failure/empty results, do not automatically try different keywords, paginate, or change the zip code to probe repeatedly; if further retrieval is needed, first explain to the user that it will incur additional consumption.
Output strategy (script default behavior)：
- Alwayswrite the full response to
<cwd>/linkfox/<YYYY-MM-DD>/<session>/data/linkfox-zhihuiya-simple-bibliography-<timestamp>.json（<cwd>is the working directory when the script runs, which in Claude Code is the current project directory;<session>is taken from the environment variableSESSION_ID, automatically aggregated according to the user's task;writing to /tmp is prohibited, if the current directory is not writable, report an error) - Response body ≤ 8 KB: after writing to disk, print the full JSON to stdout
- Response body > 8 KB: after writing to disk, stdout outputs only a summary (top-level fields, common counts such as
total/costToken, length of the largest list field + first 3 samples) - Add
--inlineto force full printing to stdout (also written to disk)
Data reading recommendations: First look at the summary to judge whether it is sufficient; when specific fields are needed, prefer to use jqorConvertFrom-Json to extract on demand from the saved json file, avoiding putting the entire JSON into the context.
Resolving authentication and compute issues
When the following abnormal situations occur, use references/onboarding.md to guide resolution:
Abnormal situation
- API Key not configured: The environment variable is not configured
LINKFOX_AGENT_API_KEY, andLINKFOXAGENT_API_KEY。 - Response 401 or 402 status code
- Response indicates insufficient compute or balance: The message contains "insufficient compute balance/insufficient billing/insufficient balance/quota exceeded/insufficient balance/package expired/recharge required/please recharge", or similar meanings.
Usage Examples
1. Look up a single patent by publication number
User: "Show me the bibliographic info for patent US11234567B2."
Action: Call with patentNumber = "US11234567B2"
2. Look up multiple patents by publication number
User: "Get the basic info for CN115000000A, EP4000000A1, and JP2023100000A."
Action: Call with patentNumber = "CN115000000A,EP4000000A1,JP2023100000A"
3. Look up patents by Zhihuiya patent ID
User: "Retrieve bibliography for patent IDs abc123 and def456."
Action: Call with patentId = "abc123,def456"
4. Retrieve inventor and applicant information
User: "Who are the inventors and applicants for patent US20230001234A1?"
Action: Call with patentNumber = "US20230001234A1", then extract the inventors and applicants fields from the response.
5. Check patent classification codes
User: "What IPC and CPC codes does patent EP3999999B1 have?"
Action: Call with patentNumber = "EP3999999B1", then present ipcMain, ipcFurther, cpcMain, and cpcFurther from the response.
6. Get patent abstract and citation references
User: "Show me the abstract and cited patents for CN114000000B."
Action: Call with patentNumber = "CN114000000B", then display abstractContent and citedPatents.
Display Rules
- Present data clearly: Show bibliographic results in well-structured tables or grouped sections. For a single patent, use a key-value layout. For multiple patents, use a table with the most relevant columns.
- Selective display: When results contain many fields, prioritize showing title, publication number, applicants, inventors, application date, publication date, IPC/CPC main codes, and abstract. Show additional fields only when the user specifically asks.
- List fields: For array fields (inventors, applicants, assignees, classification codes, citations), present them as comma-separated values or bulleted lists depending on length.
- Empty fields: Omit fields that are null or empty from the display rather than showing blank entries.
- Error handling: When a query fails, explain the reason based on the error message and suggest the user verify the patent number or ID format.
- Batch result notice: When querying many patents at once, remind the user that the maximum is 100 per request.
Important Limitations
- Maximum batch size: Up to 100 patent IDs or publication numbers per request.
- At least one identifier required: Either
patentIdorpatentNumbermust be provided; omitting both will cause an error. - patentId takes priority: If both parameters are supplied, only
patentIdis used. - Data scope: This tool returns simple bibliographic data only. It does not return full-text claims, detailed descriptions, legal status, or patent family information.
User Expression & Scenario Quick Reference
Applicable -- Patent bibliographic data retrieval:
| User Says | Scenario |
|---|---|
| "Look up patent XX" / "Get info for patent XX" | Single patent bibliography lookup |
| "Who invented patent XX" / "Who is the applicant" | Inventor / applicant retrieval |
| "What's the IPC code for XX" / "Classification of XX" | Classification code lookup |
| "Show me the abstract of XX" | Abstract retrieval |
| "When was patent XX filed" / "Publication date of XX" | Date information lookup |
| "What patents does XX cite" | Citation reference lookup |
| "Get bibliographic data for these patents: A, B, C" | Batch bibliography query |
| "Patent basic info" / "Patent front page data" | General bibliography retrieval |
Not applicable -- Needs beyond simple bibliographic data:
- Full-text patent claims or detailed description
- Patent legal status or prosecution history
- Patent family / equivalents analysis
- Patent valuation or landscaping
- Freedom-to-operate or infringement analysis
- Patent search by keyword or semantic query (this tool requires specific patent identifiers)
Compute consumption rules
Billed by dynamic rules: compute consumed = 81 × number of data entries returned. Each entry is 1 brief patent bibliographic result
Important: The service of this skill is dynamically calculated by a multiplier and may consume a large amount of compute at once; the user must be reminded, and the user decides whether to continue.
Feedback:
Auto-detect and report feedback via the Feedback API when any of the following apply:
- The functionality or purpose described in this skill does not match actual behavior
- The skill's results do not match the user's intent
- The user expresses dissatisfaction or praise about this skill
- 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.