The Trademark Image Search API (beta) allows searching Trademark Images using various attributes like feature, accuracy, metricspaces and candidates. This API also allows searching Trademark documents using various metadata attributes like Specimen Description, Filing Description, Filing Basis, Owner's Name, Street Address, etc.

The Trademark Status and Document Retrieval (TSDR) API allows you to make programmatic requests for trademark case status, documents, and images. Beginning on October 2, 2020, you will need an API key to download bulk data from TSDR using the TSDR API. Using API keys will help optimize usage of our TSDR system, which will help enable users like yourself to better access the information you need from TSDR. The below resources will provide you with more information on using the TSDR API.

Contains detailed information on 7.0 million trademark applications filed with or registrations issued by the USPTO between 1870 and 2020.

Contains detailed information on 786,931 assignments and other transactions recorded at the USPTO between 1952 and 2020 and involving 1,491,485 million unique trademark properties.

Round 1 Training DatasetThe data being generated and disseminated is the training data used to construct trojan detection software solutions. This data, generated at NIST, consists of human level AIs trained to perform a variety of tasks (image classification, natural language processing, etc.). A known percentage of these trained AI models have been poisoned with a known trigger which induces incorrect behavior. This data will be used to develop software solutions for detecting which trained AI models have been poisoned via embedded triggers.

Round 1 Test DatasetThe data being generated and disseminated is the test data used to evaluate trojan detection software solutions. This data, generated at NIST, consists of human level AIs trained to perform a variety of tasks (image classification, natural language processing, etc.). A known percentage of these trained AI models have been poisoned with a known trigger which induces incorrect behavior. This data will be used to develop software solutions for detecting which trained AI models have been poisoned via embedded triggers.

Round1 Holdout DatasetThe data being generated and disseminated is the holdout data used to evaluate trojan detection software solutions. This data, generated at NIST, consists of human level AIs trained to perform a variety of tasks (image classification, natural language processing, etc.). A known percentage of these trained AI models have been poisoned with a known trigger which induces incorrect behavior. This data will be used to develop software solutions for detecting which trained AI models have been poisoned via embedded triggers.

Round 2 Training DatasetThe data being generated and disseminated is the training data used to construct trojan detection software solutions. This data, generated at NIST, consists of human level AIs trained to perform image classification. A known percentage of these trained AI models have been poisoned with a known trigger which induces incorrect behavior. This data will be used to develop software solutions for detecting which trained AI models have been poisoned via embedded triggers.

Round 3 Training DatasetThe data being generated and disseminated is the training data used to construct trojan detection software solutions. This data, generated at NIST, consists of human level AIs trained to perform image classification. A known percentage of these trained AI models have been poisoned with a known trigger which induces incorrect behavior. This data will be used to develop software solutions for detecting which trained AI models have been poisoned via embedded triggers.

Round 2 Test DatasetThe data being generated and disseminated is the test data used to evaluate trojan detection software solutions. This data, generated at NIST, consists of human level AIs trained to perform a variety of tasks (image classification, natural language processing, etc.). A known percentage of these trained AI models have been poisoned with a known trigger which induces incorrect behavior. This data will be used to develop software solutions for detecting which trained AI models have been poisoned via embedded triggers.