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.
  • 搜索已授权专利或授权前公开文献。
  • 查看专利申请状态、案卷数据、转让信息或公开审查历史。
  • 查询商标状态、文档或转让历史。
  • 构建可复现的现有技术、专利组合或知识产权格局研究日志。
  • 将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:公开专利申请书目数据和案卷记录。
  • PatentSearch API:用于已授权专利和授权前公开数据集的PatentsView搜索API。
  • TSDR Data API:商标状态和文档检索。
  • 专利和商标转让搜索:所有权转移记录。
  • ODP中的PTAB数据:专利审判和上诉委员会程序数据。
仅将辅助数据源作为便捷索引使用。当结果至关重要时,需交叉核对官方记录。

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密钥。请将密钥存储在环境变量或密钥管理器中,切勿存储在已提交的文件或粘贴的记录中。
常见环境变量名称:
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:
  1. Identify the endpoint from the current PatentSearch reference or Swagger UI.
  2. Build a JSON query with explicit filters.
  3. Request only the fields needed for the analysis.
  4. Sort and paginate deterministically.
  5. 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进行广泛的专利和授权前公开搜索。
工作流:
  1. 从当前PatentSearch参考文档或Swagger UI中确定端点。
  2. 使用明确的过滤器构建JSON查询。
  3. 仅请求分析所需的字段。
  4. 确定性地进行排序和分页。
  5. 记录端点、查询体、日期、数据时效性说明以及结果数量。
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实时文档中验证当前端点名称、字段路径、请求参数和API密钥可用性。

Trademark/TSDR Workflow

商标/TSDR工作流

Use TSDR when the task needs trademark case status, documents, images, owner history, or prosecution events.
Workflow:
  1. Normalize the serial number or registration number.
  2. Check the current TSDR API instructions and required API-key header.
  3. Fetch status first, then documents only if needed.
  4. Respect the lower rate limit for PDF, ZIP, and multi-case downloads.
  5. 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。
工作流:
  1. 标准化序列号或注册号。
  2. 查看当前TSDR API说明和所需的API密钥请求头。
  3. 先获取状态,仅在需要时再获取文档。
  4. 遵守PDF、ZIP和多案件下载的较低速率限制。
  5. 在输出中记录检索日期和序列号/注册号。
对于大规模商标数据提取,优先使用有文档记录的批量数据流,而非抓取公开页面。

File Wrapper and Prosecution History

案卷与审查历史

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搜索开始。
  • 如有可用,使用精确标识符:申请号、公开号、专利号或当事人名称。
  • 记录该记录是已授权专利、授权前公开文献还是待决申请。
  • 在引用之前,交叉核对文档日期和状态与记录详情页面的信息。

Assignment Workflow

转让工作流

For patent or trademark ownership:
  1. Search official assignment data by patent/application/registration number, assignor, assignee, or reel/frame when available.
  2. Record conveyance text, execution date, recordation date, and parties.
  3. Distinguish assignment records from current legal ownership conclusions.
  4. If ownership is material, flag the result for attorney or subject-matter review.
对于专利或商标所有权:
  1. 通过专利/申请/注册号、转让人、受让人或可用的卷/帧号搜索官方转让数据。
  2. 记录转让文本、执行日期、记录日期和相关方。
  3. 区分转让记录与当前合法所有权结论。
  4. 如果所有权至关重要,请将结果标记为需要律师或主题专家审核。

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研究过程都应包含一个日志表:
markdown
| 数据源 | 搜索日期 | 标识符/查询 | 过滤器 | 结果数量 | 备注 |
| --- | --- | --- | --- | ---: | --- |
| PatentSearch | 2026-05-11 | `assignee=Alphabet AND date>=2024` | patent端点 | 118 | 运行前已核对API文档 |
| TSDR | 2026-05-11 | `serial=90000000` | 仅状态 | 1 | 使用API密钥流程,未批量拉取文档 |
对于最终报告,请区分:
  • 官方记录事实
  • 推断分析
  • 辅助数据源的便捷匹配
  • 未解决的空白或需要法律审查的记录

Review Checklist

审查清单

  • Did you use an official USPTO or USPTO-supported source first?
  • Did you verify current endpoint and field names before running code?
  • Are API keys kept out of files, shell history, and output logs?
  • Does the query log include the date searched and exact request shape?
  • Are rate limits respected?
  • Are legal conclusions avoided or explicitly escalated?
  • Are secondary sources labeled as secondary?
  • 是否优先使用了官方USPTO或USPTO支持的数据源?
  • 在运行代码之前是否验证了当前端点和字段名称?
  • API密钥是否未出现在文件、shell历史和输出日志中?
  • 查询日志是否包含搜索日期和精确请求格式?
  • 是否遵守了速率限制?
  • 是否避免了法律结论或明确将其升级处理?
  • 是否将辅助数据源标记为辅助?

References

参考资料