canonical: https://jentic.com/apis/uspto.gov/uspto-gov

# Uspto Gov Bulk Data Storage System Services

Bulk Data Storage System (BDSS) allows the public to discover, search, and download patent and trademark data in bulk form. The API exposes 7 endpoints.

## For AI agents

Programmatically returns all products with latest files., returns files associated with products (of level product) based on their full or. Covers 7 operations.

## Scope

Does not handle payments, communications, or crm - use for storage and databases only.

## Capabilities

- Returns all products with Latest Files.
- Manage storage data programmatically
- Integrate Bulk Data Storage System Services into automated workflows
- Query and filter Bulk Data Storage System Services records by parameters
- Monitor Bulk Data Storage System Services operational status and events

## Use cases

### Storage and Databases Operations

Use the Bulk Data Storage System Services to perform storage operations programmatically. The API provides 7 endpoints covering core functionality including returns all products with latest files., returns files associated with products (of level product) based on their full or, returns popular products along with latest files..

Example prompt: Call GET `/products/all/latest` to returns all products with latest files.

### Automated products Management

Automate products operations by combining multiple Bulk Data Storage System Services endpoints. Agents can returns files associated with products (of level product) based on their full or and then returns popular products along with latest files. in a single workflow.

Example prompt: Call GET `/products/byname/{productName}` to returns files associated with products (of level product) based on their full or, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Bulk Data Storage System Services endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle none tokens manually.

Example prompt: Search Jentic for 'returns all products with latest files.', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/products/all/latest` | Returns all products with Latest Files. |
| GET | `/products/byname/{productName}` | Returns files associated with products (of level PRODUCT) based on their full or |
| GET | `/products/popular` | Returns popular products along with latest files. |
| GET | `/products/tree` | Returns products' hierarchical tree. |
| GET | `/products/tree/{shortName}` | Returns products' hierarchical subtree. |
| GET | `/products/{shortName}` | Returns products along with their associated files by short names. |
| GET | `/products/{shortName}/latest` | Returns products along with their latest files by short names. |

## Key resources

- **products** — Operations related to products

## Why Jentic

- **Setup:** Wiring the USPTO Bulk Data Storage System by hand means reading its product tree, tracking the relative BDSS-API paths, and coding each product and file lookup yourself. Through Jentic you install once, import Bulk Data Storage System Services from the API Directory, and your agent calls it without any token setup since these endpoints are open.
- **Permission scoping:** The BDSS product endpoints put the product name in the URL path (`/products/{shortName}`, `/products/byname/{productName}`), so a rule can pin your agent to one product. The service is read-only for bulk data, so a rule limits the agent to the lookups it needs, such as listing latest files or fetching the product tree.
- **Credential handling:** These BDSS endpoints require no credential, so there is nothing to store, and any configuration your Jentic One instance holds is kept encrypted and injected at execution time. Nothing sensitive enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list all products with their latest files' or 'find a bulk data product by name', and Jentic returns the matching Bulk Data Storage System Services operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Dropbox** — Alternative storage API
- **Box** — Alternative storage API
- **Amazonaws** — Complementary storage API

## FAQ

### What authentication does the Bulk Data Storage System Services use?

The Bulk Data Storage System Services uses no authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I returns all products with latest files. with the Bulk Data Storage System Services?

Yes. Use the GET `/products/all/latest` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Bulk Data Storage System Services?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I returns all products with latest files. through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'returns all products with latest files.'. Jentic returns the matching Bulk Data Storage System Services operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Bulk Data Storage System Services have?

The Bulk Data Storage System Services exposes 7 endpoints covering products operations.

### Can I limit what my agent is allowed to do with the USPTO Bulk Data Storage System Services?

Yes. Because Jentic One is self-hosted, you write the rules that decide which BDSS operations and inputs your agent may use. Since the product name sits in the URL path for endpoints like GET `/products/{shortName}` and GET `/products/byname/{productName}`, a rule can pin the agent to a single product, and because the service is read-only you can restrict it to just the lookups it needs, such as listing latest files or fetching the product tree. Any calls outside those rules are blocked before they run.