SuperAPI AI Directory
Partner with us中文AI newsFavorites
Skillslinkfox-zhihuiya-description-data

linkfox-zhihuiya-description-data

Data & analytics

View repository

Updated 10-15 09:09

About this skill

Zhihuiya Patent Description Data

This skill guides you on how to query patent description (specification) data from the Zhihuiya patent database, helping users retrieve the full-text description content of specific patents.

Core Concepts

A patent description (also called the specification) is the detailed technical document that accompanies a patent filing. It discloses how the invention works, preferred embodiments, and other technical details required by patent law. This tool queries the Zhihuiya database to return description data for one or more patents identified by their internal patent ID or public publication number.

Identifier priority: When both a patent ID and a publication number are provided for the same query, the patent ID takes precedence.

Family substitution: If the description for a given patent is unavailable, the tool can optionally return the description from a related family member patent instead.

Parameters

Parameter Type Required Description
patentId string Conditionally Internal patent ID. At least one of patentId or patentNumber must be provided. Multiple values separated by commas; max 100.
patentNumber string Conditionally Publication / announcement number. At least one of patentId or patentNumber must be provided. Multiple values separated by commas; max 100.
replaceByRelated string No Whether to substitute a family patent's description when the target patent's description is unavailable. 1 = yes, 0 = no.

Response Fields

Field Type Description
total integer Number of patent records returned
data array List of patent description objects
data[].patentId string Patent ID
data[].pn string Publication number
data[].pnRelated string Publication number of the substitute family patent (only present when family substitution is used)
data[].description array Description / specification content sections
columns array Column definitions for rendering
costToken integer Tokens consumed by the query
type string Rendering style hint

How to call

  • API endpoint：POST /zhihuiya/descriptionData(for full parameters/responses/error codes, see references/api.md）
  • Python script：python scripts/zhihuiya_description_data.py '<JSON 参数>' [--inline]
  • Cost constraint: This tool consumes computing power; by default, the same parameter combination is called only once per session, and the script has a 24h local cache. On failure/empty results, do not automatically try different keywords, paginate, or change the postal code to probe continuously; if you need to continue searching, first explain to the user that additional consumption will be incurred.

Output strategy (default script behavior)：

  • Alwayswrite the complete response to <cwd>/linkfox/<YYYY-MM-DD>/<session>/data/linkfox-zhihuiya-description-data-<timestamp>.json（<cwd> is the working directory when the script is executed, which in Claude Code is the current project directory;<session> is taken from the environment variable SESSION_ID, automatically aggregated according to the user's task;writing to /tmp is prohibited, and if the current directory is not writable, report an error)
  • Response body ≤ 8 KB: after saving to disk, print the full JSON to stdout
  • Response body > 8 KB: after saving to disk, stdout outputs only a summary (top-level fields, common counts such as total/costToken, the length of the largest list field + the first 3 samples)
  • Add --inline to force full printing to stdout (also saved to disk)

Data reading suggestions: first look at the summary to determine 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.

Resolve authentication and computing power issues

When the following abnormal situations occur, use references/onboarding.md to guide resolution:

Abnormal situations

  • API Key not configured: the environment variable is not configured LINKFOX_AGENT_API_KEY, and it is also not configured LINKFOXAGENT_API_KEY。
  • Response 401 or 402 status code
  • The response indicates insufficient computing power or balance: the message contains "insufficient computing power balance/insufficient billing/insufficient balance/quota exceeded/insufficient balance/package expired/recharge required/please recharge", or content with a similar meaning.

How to Build Queries

Querying by Publication Number

When users provide a patent publication number (e.g., CN115099012A, US20230012345A1), pass it via the patentNumber parameter:

patentNumber: "CN115099012A"

Querying by Patent ID

When users provide internal Zhihuiya patent IDs, pass them via the patentId parameter:

patentId: "abc123def456"

Batch Queries

Both patentId and patentNumber accept comma-separated values for batch lookups (up to 100):

patentNumber: "CN115099012A,US20230012345A1,EP4123456A1"

Family Substitution

When a patent's description is not available in the database and the user still wants content, enable family substitution:

patentNumber: "CN115099012A"
replaceByRelated: "1"

Usage Examples

1. Look up a single patent description by publication number

patentNumber: "CN115099012A"

2. Look up descriptions for multiple patents at once

patentNumber: "CN115099012A,US20230012345A1"

3. Look up with family substitution enabled

patentNumber: "CN115099012A"
replaceByRelated: "1"

4. Look up by patent ID

patentId: "some-patent-id"

Display Rules

  1. Present data faithfully: Show the returned description content clearly without altering technical details or adding subjective interpretation.
  2. Structured output: When the description contains multiple sections (background, summary, detailed description, claims, etc.), present them with clear headings for readability.
  3. Family substitution notice: If the response includes a pnRelated field, explicitly inform the user that the description was sourced from a related family patent and state the substitute publication number.
  4. Batch results: When multiple patents are returned, clearly separate each patent's content with its publication number as a heading.
  5. Error handling: When a query fails or returns no data, explain the reason and suggest the user verify the patent ID or publication number.
  6. Large content warning: Patent descriptions can be very long. Summarize key sections first and offer to show the full text if the user wants it.

Important Limitations

  • Identifier requirement: At least one of patentId or patentNumber must be provided; the tool cannot search by keyword or applicant name.
  • Batch limit: A maximum of 100 patents can be queried in a single request.
  • Availability: Not all patents have descriptions available in the database. Use replaceByRelated: "1" to attempt family substitution when needed.
  • Priority rule: If both patentId and patentNumber are supplied, patentId takes precedence.

User Expression & Scenario Quick Reference

Applicable -- Queries about patent description / specification content:

User Says Scenario
"Show me the description of patent XX" Single patent description lookup
"Get the full specification for these patents" Batch patent description retrieval
"I need the detailed text of CN115099012A" Lookup by publication number
"Can you find a family patent's description instead" Family substitution query
"What does this patent describe technically" Description content review

Not applicable -- Needs beyond patent description data:

  • Patent search by keyword, applicant, or classification
  • Patent claim analysis or claim chart generation
  • Patent legal status or prosecution history
  • Patent landscape or statistical analysis
  • Freedom-to-operate or infringement opinions

Computing power consumption rules

Billed according to dynamic rules: computing power consumed = 81 × number of returned data entries. Each entry is 1 patent specification result

Important: the service of this skill is dynamically calculated by a multiplier and may consume a large amount of computing power 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:

  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.