Recent event cohort
Applications that reached a specified lifecycle event during a date window, narrowed by class or geography.
Custom Data
Tell Us the Business Question. We Will Define the Trademark Dataset.
You do not need to know the exact USPTO status code before contacting us. Describe the records you are trying to identify, the time window and the fields you need; we will confirm whether a source-verifiable dataset can be produced.
Official USPTO source
↓
NormalizeQualifyVerifyDeduplicate
↓
Structured dataset
Data company workflowNormalize / qualify / verify / deliver
Direct answer
What counts as a custom USPTO data order?
A custom order is a dataset whose qualification rules or output columns do not fit one standard product. It can combine supported case status, lifecycle event, date, geography, class, filing basis, representation, contact availability, deduplication and output-field requirements.
Direct answer
Price, minimum order and delivery
Custom datasets are quoted case by case. Tell us the status and date window, geography, Nice classes, contact/provenance fields and expected size; we verify source feasibility and exclude previously allocated serials before accepting the work.
Custom lead requests may combine eligible records from several statuses. Every delivered serial is screened for representation ambiguity and prior customer allocation; no price or immediate fulfillment promise is made before we assess the requirements.
Datasets are delivered after invoice settlement and final verification as CSV, XLSX or a private Google Sheet, via the agreed email or WhatsApp channel. No payment details are collected by this page.
Examples of custom requests
Representation cohort
A selected application population segmented by qualifying applicant-attorney representation.
Status-change research
A historical or current cohort defined by supported status/event changes and dates.
Custom schema
A standard lead family delivered with additional supported fields or provenance columns.
Recurring delivery
Repeat the same defined profile on an agreed cadence with prior-delivery controls, when operationally supported.
Prefer direct TSDR case access instead of a prepared dataset?
A custom lead dataset and a TSDR API key are different products. For supported, authorized status and document lookups using known case identifiers, explore TSDR API access.
Buy TSDR API Key — $20
Request a key for eligible use cases involving public case status, documents and images.
Learn more →TSDR API Documentation
Understand what TSDR can and cannot retrieve.
Learn more →Information that helps us scope the order
Business question / target prospectDate or freshness windowApproximate volumeStatus or lifecycle conditionInternational ClassApplicant geographyFiling basisRepresentation criteriaRequired contact fieldsOutput columns / format
Custom does not mean unlimited
Our current platform is not an arbitrary public query engine. We accept custom orders subject to source availability, implemented qualification logic, verification cost and the engineering required to produce the requested output.
Our current platform is not an arbitrary public query engine. We accept custom orders subject to source availability, implemented qualification logic, verification cost and the engineering required to produce the requested output.
Custom-order workflow
Describe
Explain what you are trying to find in normal business language.
Translate
We map the request to available USPTO fields and qualification rules.
Quote
We confirm scope, feasibility, volume, delivery and payment.
Prepare
The data is processed and checked under the agreed profile.
Deliver
You receive the structured file and any agreed provenance/verification fields.
Turn a business question into a data contract
| Question to define | Example of what we need to know |
|---|---|
| Which records? | The lifecycle event, current status or cohort that should define the initial universe. |
| How recent? | A date window, event age or other freshness rule. |
| Which additional filters? | Class, geography, filing basis, representation, contact availability or another supported dimension. |
| What should be delivered? | Required columns, preferred file format and any provenance/verification fields. |
| How should repeats be handled? | Whether prior deliveries or duplicate serials should be excluded under an agreed rule. |
Examples of questions that can become structured orders
Event-driven cohort
A defined Office Action or abandonment cohort within a requested date window, plus supported representation/contact filters.
Learn more →Representation-driven cohort
Records matching an agreed no-qualifying-attorney profile combined with status, geography or class criteria.
Learn more →Research dataset
A status/lifecycle cohort prepared with identifiers, event dates and provenance fields for analysis rather than outreach.
Learn more →Repeat delivery specification
A recurring or repeat request whose filters and deduplication rules are kept consistent between deliveries when operationally supported.
Learn more →Request Data
Request Custom USPTO Trademark Data
Include the business question, date range, filters, fields and approximate volume.
✓ International data support✓ Quote by scope✓ Custom filters welcome