Catalog
affaan-m/uspto-database

affaan-m

uspto-database

USPTO patent and trademark data workflow for official record lookup, PatentSearch queries, TSDR checks, assignment data, and reproducible IP research logs. Use when a task needs official United States patent or trademark records from USPTO systems.

NewUpdated Sep 9, 2026

USPTO Database

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

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.

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.

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:

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.

PatentSearch Workflow

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:

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.

Trademark/TSDR Workflow

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.

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.

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.

Reproducible Output

Every USPTO research pass should include a log table:

| 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

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?

References

Files1
1 files · 1.0 KB

Select a file to preview

Overall Score

87/100

Grade

A

Excellent

Grades are signals, not a certification. Always review a skill yourself before use.

Safety

88

Quality

88

Clarity

85

Completeness

82

Summary

This skill guides agents through USPTO patent and trademark data workflows, enabling official record lookup via PatentSearch, TSDR, and assignment data APIs. It provides structured guidance for building reproducible IP research queries, respecting API rate limits, securing credentials, and cross-verifying official records against secondary sources.

Detected Capabilities

http requestenvironment variable readquery buildingdata aggregationapi key handling

Trigger Keywords

Phrases that agents use to match this skill to user intent.

patent search assigneetrademark status lookuppatent assignment historyUSPTO prior art researchTSDR trademark recordspatentsview api query

Risk Signals

INFO

Environment variable read for API keys (USPTO_API_KEY, PATENTSVIEW_API_KEY)

## Authentication and Secrets, ## PatentSearch Workflow
INFO

Outbound HTTP requests to USPTO and PatentsView APIs

## PatentSearch Workflow, ## Trademark/TSDR Workflow
INFO

API key passed in X-Api-Key header

## PatentSearch Workflow (Python example)

Referenced Domains

External domains referenced in skill content, detected by static analysis.

data.uspto.govdeveloper.uspto.govsearch.patentsview.org

Use Cases

  • Search granted patents and pre-grant publications by assignee, date, or classification
  • Check trademark application status and retrieve prosecution documents via TSDR
  • Track patent ownership changes through assignment records and conveyance history
  • Build reproducible prior-art research logs with documented queries and retrieval dates
  • Verify USPTO official records against secondary sources like Google Patents or Lens.org
  • Retrieve patent file wrapper and application status data from ODP

Quality Notes

  • Excellent scope boundaries: skill explicitly limits itself to data gathering and prohibits legal advice
  • Strong credential security guidance: explicitly instructs storing keys in environment variables/secret managers, never in committed files or transcripts
  • Well-documented workflows with clear step-by-step instructions for PatentSearch, TSDR, file wrapper, and assignment searches
  • Includes practical Python code skeleton that demonstrates proper API key handling via os.environ and secure header passing
  • Reproducible output requirement with structured log table template ensures traceability and auditability of research
  • Review checklist at end enforces best practices including endpoint verification, rate-limit respect, and API-key hygiene
  • Guidance to prefer official sources over secondary sources and cross-check records demonstrates integrity of data collection
  • Clear distinction between official records, inferred analysis, and secondary-source matches prevents misrepresentation
  • References section provides links to current API documentation, supporting long-term skill maintenance
  • Disclaimer about not providing legal advice sets appropriate boundary on skill scope
Model: claude-haiku-4-5-20251001Analyzed: Sep 9, 2026

Reviews

Add this skill to your library to leave a review.

No reviews yet

Be the first to share your experience.

Version History

  1. v2.0

    Contract changed: description

    ✦ AIClarifies activation scope: skill now emphasizes use for official US patent or trademark records from USPTO systems.

    triggering2026-09-09

    LATEST
  2. v1.1

    Content updated

    ✦ AINo behavioral changes detected.

    2026-07-14

    View This Version
  3. v1.0

    2026-05-15

    View This VersionInitial version

Use affaan-m/uspto-database in your dev environment

Command Palette

Search for a command to run...