scientific-db-uspto-database

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

USPTO Database

USPTO 数据库

Use this skill when a task needs official United States patent or trademark records from USPTO systems.

当任务需要来自 USPTO 系统的美国官方专利或商标记录时，使用此 skill。

When to Use

使用场景

Searching granted patents or pre-grant publications.
Checking patent application status, file-wrapper data, assignments, or public prosecution history.
Looking up trademark status, documents, or assignment history.
Building reproducible prior-art, portfolio, or IP landscape research logs.
Comparing USPTO records with secondary tools such as Google Patents, Lens.org, Semantic Scholar, or company patent pages.

Do not use this skill to give legal advice. Treat it as a data-gathering and record-verification workflow.

搜索已授权专利或授权前公开。
查询专利申请状态、file wrapper 数据、转让记录或公开审查历史。
查找商标状态、文件或转让历史。
构建可复现的现有技术、专利组合或 IP 格局研究日志。
将 USPTO 记录与 Google Patents、Lens.org、Semantic Scholar 或公司专利页面等辅助工具进行比较。

不要使用此 skill 提供法律建议。将其视为数据收集和记录核验工作流。

Source Selection

来源选择

Prefer official USPTO or USPTO-supported surfaces first:

Open Data Portal (ODP): current home for migrated USPTO datasets and APIs.
Patent File Wrapper: public patent application bibliographic data and file wrapper records.
PatentSearch API: PatentsView search API for granted patents and pre-grant publication datasets.
TSDR Data API: trademark status and document retrieval.
Patent and Trademark Assignment Search: ownership transfer records.
PTAB data in ODP: Patent Trial and Appeal Board proceedings.

Use secondary sources only as convenience indexes. When the answer matters, cross-check the official record.

优先选择官方 USPTO 或 USPTO 支持的平台：

Open Data Portal (ODP)：已迁移的 USPTO 数据集和 API 的当前入口。
Patent File Wrapper：公开的专利申请 bibliographic 数据和 file wrapper 记录。
PatentSearch API：用于检索已授权专利和授权前公开数据集的 PatentsView 搜索 API。
TSDR Data API：商标状态和文件检索。
Patent and Trademark Assignment Search：所有权转让记录。
ODP 中的 PTAB 数据：Patent Trial and Appeal Board 诉讼程序。

仅将二手来源用作便捷索引。当答案至关重要时，应交叉核验官方记录。

Authentication and Secrets

身份验证和密钥

Many USPTO API flows require an API key. Store keys in environment variables or a secret manager, never in committed files or pasted transcripts.

Common environment names:

bash

export USPTO_API_KEY="..."
export PATENTSVIEW_API_KEY="..."

For PatentSearch, send the key with the

X-Api-Key

header. For TSDR, follow the current USPTO API Manager instructions and rate-limit guidance.

许多 USPTO API 流程需要 API key。将密钥存储在环境变量或 secret manager 中，绝不要存入已提交的文件或粘贴到对话记录中。

常见的环境变量名称：

bash

export USPTO_API_KEY="..."
export PATENTSVIEW_API_KEY="..."

对于 PatentSearch，通过

X-Api-Key

请求头发送密钥。对于 TSDR，请遵循当前 USPTO API Manager 说明和速率限制指南。

PatentSearch Workflow

PatentSearch 工作流

Use PatentSearch for broad patent and pre-grant publication search when the question is about trends, inventors, assignees, classifications, dates, or portfolio slices.

Workflow:

Identify the endpoint from the current PatentSearch reference or Swagger UI.
Build a JSON query with explicit filters.
Request only the fields needed for the analysis.
Sort and paginate deterministically.
Record the endpoint, query body, date, data currency note, and result count.

Python request skeleton:

python

import os
import requests

API_KEY = os.environ["PATENTSVIEW_API_KEY"]
BASE = "https://search.patentsview.org/api/v1"

payload = {
    "q": {
        "_and": [
            {"patent_date": {"_gte": "2024-01-01"}},
            {"assignees.assignee_organization": {"_text_any": ["Google", "Alphabet"]}},
        ]
    },
    "f": ["patent_id", "patent_title", "patent_date"],
    "s": [{"patent_date": "desc"}],
    "o": {"per_page": 100, "page": 1},
}

response = requests.post(
    f"{BASE}/patent/",
    headers={"X-Api-Key": API_KEY, "Content-Type": "application/json"},
    json=payload,
    timeout=30,
)
response.raise_for_status()
print(response.json())

Before reusing a query, verify current endpoint names, field paths, request parameters, and API-key availability in the live PatentSearch docs.

当问题涉及趋势、发明人、受让人、分类号、日期或专利组合切片时，使用 PatentSearch 进行广泛的专利和授权前公开检索。

工作流：

根据当前 PatentSearch 参考文档或 Swagger UI 确定 endpoint。
使用明确的筛选条件构建 JSON 查询。
仅请求分析所需的字段。
以确定性的方式进行排序和分页。
记录 endpoint、查询正文、日期、数据时效性说明和结果数量。

Python 请求示例：

python

import os
import requests

API_KEY = os.environ["PATENTSVIEW_API_KEY"]
BASE = "https://search.patentsview.org/api/v1"

payload = {
    "q": {
        "_and": [
            {"patent_date": {"_gte": "2024-01-01"}},
            {"assignees.assignee_organization": {"_text_any": ["Google", "Alphabet"]}},
        ]
    },
    "f": ["patent_id", "patent_title", "patent_date"],
    "s": [{"patent_date": "desc"}],
    "o": {"per_page": 100, "page": 1},
}

response = requests.post(
    f"{BASE}/patent/",
    headers={"X-Api-Key": API_KEY, "Content-Type": "application/json"},
    json=payload,
    timeout=30,
)
response.raise_for_status()
print(response.json())

在复用查询前，应根据实时 PatentSearch 文档验证当前 endpoint 名称、字段路径、请求参数和 API key 可用性。

Trademark/TSDR Workflow

商标和 TSDR 工作流

Use TSDR when the task needs trademark case status, documents, images, owner history, or prosecution events.

Workflow:

Normalize the serial number or registration number.
Check the current TSDR API instructions and required API-key header.
Fetch status first, then documents only if needed.
Respect the lower rate limit for PDF, ZIP, and multi-case downloads.
Capture retrieval date and serial/registration identifier in the output.

For large trademark pulls, prefer documented bulk-data flows rather than screen-scraping public pages.

当任务需要商标案件状态、文件、图像、所有者历史或审查事件时，使用 TSDR。

工作流：

规范化 serial number 或 registration number。
查看当前 TSDR API 说明以及所需的 API key 请求头。
先获取状态，仅在需要时再获取文件。
遵守 PDF、ZIP 和多案件下载的较低速率限制。
在输出中记录检索日期及 serial/registration identifier。

对于大规模商标数据提取，应优先使用有文档说明的批量数据流程，而不是抓取公开网页。

File Wrapper and Prosecution History

File Wrapper 和审查历史

For application status, transaction history, and prosecution documents:

Start with ODP Patent File Wrapper search.
Use exact identifiers when available: application number, publication number, patent number, or party name.
Record whether the record is a granted patent, pre-grant publication, or pending application.
Cross-check document dates and status against the record detail page before citing them.

对于申请状态、事务历史和审查文件：

从 ODP Patent File Wrapper 搜索开始。
在可用时使用精确标识符：application number、publication number、patent number 或 party name。
记录该记录属于已授权专利、授权前公开还是待审申请。
引用之前，对照记录详情页面核验文件日期和状态。

Assignment Workflow

转让工作流

For patent or trademark ownership:

Search official assignment data by patent/application/registration number, assignor, assignee, or reel/frame when available.
Record conveyance text, execution date, recordation date, and parties.
Distinguish assignment records from current legal ownership conclusions.
If ownership is material, flag the result for attorney or subject-matter review.

对于专利或商标所有权：

根据 patent/application/registration number、assignor、assignee 或可用的 reel/frame，在官方转让数据中搜索。
记录 conveyance text、execution date、recordation date 和相关各方。
区分转让记录与当前法律意义上的所有权结论。
如果所有权至关重要，应将结果标记为需要律师或专业事项审查。

Reproducible Output

可复现输出

Every USPTO research pass should include a log table:

markdown

| Source | Date searched | Identifier/query | Filters | Results | Notes |
| --- | --- | --- | --- | ---: | --- |
| PatentSearch | 2026-05-11 | `assignee=Alphabet AND date>=2024` | patent endpoint | 118 | API docs checked before run |
| TSDR | 2026-05-11 | `serial=90000000` | status only | 1 | API-key flow, no document bulk pull |

For final writeups, separate:

official record facts
inferred analysis
secondary-source convenience matches
unresolved gaps or records that require legal review

每次 USPTO 研究都应包含一张日志表：