USPTO Patent File Wrapper Python API Docs | dltHub

Build a USPTO Patent File Wrapper-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.

Last updated:

The USPTO Patent File Wrapper API provides access to bibliographic data, assignment history, and prosecution documents for U.S. patent applications. The REST API base URL is https://api.uspto.gov and all requests require an API key in a header.

dlt is an open-source Python library that handles authentication, pagination, and schema evolution automatically. dlthub provides AI context files that enable code assistants to generate production-ready pipelines. Install with uv add "dlt[hub]" and start loading USPTO Patent File Wrapper data in under 10 minutes.


What data can I load from USPTO Patent File Wrapper?

Here are some of the endpoints you can load from USPTO Patent File Wrapper:

ResourceEndpointMethodData selectorDescription
search/api/v1/patent/applications/searchGETSearch patent applications
search_post/api/v1/patent/applications/searchPOSTSearch patent applications with body
application/api/v1/patent/applications/{applicationNumberText}GETGet patent application details
documents/api/v1/patent/applications/{applicationNumberText}/documentsGETList application documents
transactions/api/v1/patent/applications/{applicationNumberText}/transactionsGETGet application transactions

How do I authenticate with the USPTO Patent File Wrapper API?

Authentication requires an API key, which must be passed in the HTTP header named 'X-API-KEY'. You can obtain this key after creating a USPTO.gov account and verifying your identity via the Open Data Portal.

1. Get your credentials

  1. Navigate to the USPTO Open Data Portal (ODP) and create a USPTO.gov account. 2. Complete identity verification through ID.me as a one-time requirement. 3. Sign in to the 'Manage API Key' page (https://data.uspto.gov/apikey) with your verified USPTO.gov account. 4. Follow the on-screen instructions to generate your API key, which will be displayed on your personal dashboard. Note: As of June 18, 2026, you must sign in with a valid USPTO.gov account with Multi-Factor Authentication (MFA) enabled to access the portal.

2. Add them to .dlt/secrets.toml

[sources.uspto_patent_file_wrapper_source] uspto_api_key = "your_api_key_here"

dlt reads this automatically at runtime — never hardcode tokens in your pipeline script. For production environments, see setting up credentials with dlt for environment variable and vault-based options.


How do I set up and run the pipeline?

Set up a virtual environment and install dlt:

uv init uv add "dlt[hub]"

1. Install the dlt AI harness:

uv run dlthub ai init --agent <your-agent> # <agent>: claude | cursor | codex

This installs project rules, a secrets management skill, appropriate ignore files, and configures the dlt MCP server for your agent. Learn more →

2. Install the rest-api-pipeline toolkit:

uv run dlthub ai toolkit install rest-api-pipeline

This loads the skills and context about dlt the agent uses to build the pipeline iteratively, efficiently, and safely. The agent uses MCP tools to inspect credentials — it never needs to read your secrets.toml directly. Learn more →

3. Start LLM-assisted coding:

Use /find-source to load data from the USPTO Patent File Wrapper API into DuckDB.

The rest-api-pipeline toolkit takes over from here — it reads relevant API documentation, presents you with options for which endpoints to load, and follows a structured workflow to scaffold, debug, and validate the pipeline step by step.

4. Run the pipeline:

uv run python uspto_patent_file_wrapper_pipeline.py

If everything is configured correctly, you'll see output like this:

Pipeline uspto_patent_file_wrapper_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset uspto_patent_file_wrapper_data The duckdb destination used duckdb:/uspto_patent_file_wrapper.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs

Inspect your pipeline and data:

uv run dlthub show

This opens the Pipeline Dashboard where you can verify pipeline state, load metrics, schema (tables, columns, types), and query the loaded data directly.


Python pipeline example

This example loads search and documents from the USPTO Patent File Wrapper API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:

import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def uspto_patent_file_wrapper_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.uspto.gov", "auth": {"type": "api_key", "api_key": api_key, "name": "X-API-KEY", "location": "header"}, }, "resources": [ {"name": "search", "endpoint": {"path": "api/v1/patent/applications/search"}}, {"name": "documents", "endpoint": {"path": "api/v1/patent/applications/{applicationNumberText}/documents"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="uspto_patent_file_wrapper_pipeline", destination="duckdb", dataset_name="uspto_patent_file_wrapper_data", ) load_info = pipeline.run(uspto_patent_file_wrapper_source()) print(load_info)

To add more endpoints, append entries from the resource table to the "resources" list using the same name, path, and data_selector pattern.


How do I query the loaded data?

Once the pipeline runs, dlt creates one table per resource. You can query with Python or SQL.

Python (pandas DataFrame):

import dlt data = dlt.pipeline("uspto_patent_file_wrapper_pipeline").dataset() sessions_df = data.search.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM uspto_patent_file_wrapper_data.search LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("uspto_patent_file_wrapper_pipeline").dataset() data.search.df().head()

See how to explore your data in marimo Notebooks and how to query your data in Python with dataset.


What destinations can I load USPTO Patent File Wrapper data to?

dlt supports loading into any of these destinations — only the destination parameter changes:

DestinationExample value
DuckDB (local, default)"duckdb"
PostgreSQL"postgres"
BigQuery"bigquery"
Snowflake"snowflake"
Redshift"redshift"
Databricks"databricks"
Filesystem (S3, GCS, Azure)"filesystem"

Change the destination in dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. See the full destinations list.


Next steps

Continue your data engineering journey with the other toolkits of the dltHub AI harness:

  • data-exploration — Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.
  • dlthub-platform — Deploy, schedule, and monitor your pipeline in production.
uv run dlthub ai toolkit install data-exploration uv run dlthub ai toolkit install dlthub-platform

Was this page helpful?

Community Hub

Need more dlt context for USPTO Patent File Wrapper?

Request dlt skills, commands, AGENT.md files, and AI-native context.

Available Pipelines