USPTO Trademark Leads ™️

foXLabs US lead series: FMCSA carriers · Insurance producers · Employer benefit plans · Federal contractors

🎉 Turn USPTO filings into clean, structured trademark-lead data — no login, no API key, one row per mark, with the applicant, mark, status, class and filing date. Built for IP services, legal and B2B sales to new brands.

🔍 What is the USPTO Trademark Leads — and when should you use it?

Give this actor applicant names or mark text and it returns matching trademarks from the USPTO trademark database (official open data) — as clean, deduplicated rows you can filter, export or feed to an AI agent. Every run reads the source live.

Use it when you need: a company list for outreach; a quick profile before a call; or a starting point for account research.

Use something else when: you need company firmographics — this is trademark filings, not a company registry.

🤖 Use with AI agents

Already on the Apify MCP server? Ask for this Actor by name: foxlabs/uspto-trademark-leads.

Your agent can pay for its own runs. This Actor is pay-per-event with agentic payments, so an agent can discover it, run it and settle the bill over x402 (USDC on Base) or Skyfire — no Apify account or API token of its own. Billing is the same either way: per delivered record, never for errors.

Otherwise paste this into Claude, ChatGPT, Cursor or any MCP-enabled assistant:

I want to pull trademark company records using the Apify Actor `foxlabs/uspto-trademark-leads`.
Input: `mode`, `datePreset`, `onlyNewSinceLastRun`, `dateFrom` and more — see the Input table below. `maxResults` caps how many results are returned.
Start with: {"mode":"new_filings","maxResults":20}
Ask me what to look up, run the Actor, then summarise the rows as a table.

The machine-readable API, MCP config and OpenAPI definition live at apify.com/foxlabs/uspto-trademark-leads.md.

📋 Overview

Everything you need to turn the USPTO trademark database (official open data) into clean, structured data — in one actor, with no login, cookies or API key.

Why teams pick this actor:

• ✅ Whole registry, one call — name or ID in, matching trademarks out.
• 🧹 No empty-promise columns — only fields this registry actually fills; degenerate columns are removed.
• 🔗 Stable identifiers — every row carries the source's own IDs, ready to join across runs and to other Fox Labs actors.
• 💰 Per-row pricing — a minimal price per delivered row, no subscription.
• 🤖 Agent-ready — MCP + x402 agentic payments.

✨ Features

• 🔍 Name or ID lookup — relevance-ranked name search or exact registry-ID lookup.
• 🏢 Full entity profile — status, legal form, formation date, address and the registry’s own contact fields.
• 🧹 Clean schema — deduplicated camelCase rows, ready for CSV/Excel/JSON.

🎬 Quick Start

curl -X POST "https://api.apify.com/v2/acts/foxlabs~uspto-trademark-leads/runs?token=YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"mode":"new_filings","maxResults":20}'

🚀 Getting Started (3 steps)

1. Choose your targets — applicant names or mark text.
2. Set the cap — maxResults limits how many results are returned.
3. Run and export — get a clean dataset as JSON, CSV or Excel.

📥 Input

{"mode":"new_filings","maxResults":20}

Field	Type	Description
mode	string	New filings walks the freshest applications by date (the lead feed). Serial range / serial list fetch specific applications by US serial number.
datePreset	string	Freshest = the newest applications published in TSDR, walking back from the publication frontier — the same freshness every 'daily trademark leads' service…
onlyNewSinceLastRun	boolean	For scheduled daily feeds: stop when reaching the serials already fetched by the previous run, so each run returns exactly the new batch. First run just uses Max…
dateFrom	string	YYYY-MM-DD filing date. Only used when Date range = Custom.
dateTo	string	YYYY-MM-DD filing date. Only used when Date range = Custom. Leave empty for 'today'.
filerType	string	Pro-se applicants filed WITHOUT an attorney — their own contact email is on the application (the classic IP-firm lead). Attorney-represented applications expose…
serialFrom	integer	First US serial number (8 digits, e.g. 99900000). Only used in 'Serial number range' mode.
serialTo	integer	Last US serial number. Only used in 'Serial number range' mode.
serialNumbers	array	Specific 8-digit US serial numbers to fetch. Only used in 'Specific serial numbers' mode.
maxResults	integer	Hard cap on dataset rows per run. Capped at 2,500 (about one full filing day) to keep access to the official source polite and reliable. At the polite pace this…
maxRunSeconds	integer	Stop the scan after this many seconds and keep the leads collected so far, instead of being cut off by the run timeout and losing them. 0 = no budget. This…
includeGoodsServices	boolean	Add the full goods/services description per class. Adds detail; off makes rows leaner.
requestDelayMs	integer	Delay between requests to USPTO. Minimum 2500 ms is enforced — TSDR rate-protects bursts, and this actor deliberately stays low-rate and polite to the official…

📤 Output

One row per result, saved to the dataset. Every row carries scrapedAt. Lookups that cannot be completed are reported in the run log rather than silently dropped.

Field	Description
serialNumber	Serial Number
markText	Mark Text
filingDate	Filing Date
isProSe	Is Pro Se
contactEmail	Contact Email
correspondentPhone	Correspondent Phone
ownerName	Owner Name
ownerAddress	Owner Address
attorneyName	Attorney Name
intlClasses	Intl Classes
status	active / inactive / dissolved
tsdrUrl	Tsdr Url

💼 Use cases

1. New-brand lead-gen — find companies filing new trademarks. Input: applicant names or classes. Output: marks + applicants + dates. Use: a fresh lead list.

2. IP services sales — target applicants by class. Input: mark text. Output: marks + status. Use: a prospect list.

3. Brand monitoring — watch filings around a brand. Input: mark text. Output: new filings. Use: an alert feed.

🔗 Integration

JavaScript / Node.js

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: 'YOUR_TOKEN' });
const run = await client.actor('foxlabs/uspto-trademark-leads').call({"mode":"new_filings","maxResults":20});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items[0]);

Python

from apify_client import ApifyClient
client = ApifyClient('YOUR_TOKEN')
run = client.actor('foxlabs/uspto-trademark-leads').call(run_input={"mode":"new_filings","maxResults":20})
for item in client.dataset(run['defaultDatasetId']).iterate_items():
    print(item)

Automation (n8n / Zapier / Make): schedule or webhook → HTTP request to the actor API with your input → handle the JSON dataset → push to a sheet, CRM or dashboard.

📊 Pricing

Pay-per-event: per delivered record. Empty or failed lookups are never billed. View current pricing.

❓ FAQ

Do I need an account, login or API key? No. This reads the USPTO trademark database (official open data).

What do I search by? Applicant names or mark text.

How current is the data? Every run queries the source live, so results are as fresh as the registry.

What trademark data is included? The applicant, mark text, status, Nice class, serial/registration number and filing date from the USPTO.

Can I export to CSV / Excel / JSON? Yes — directly from the Apify dataset.

🐛 Troubleshooting

• Fewer rows than expected — raise maxResults, or refine the input.
• A name returns an unexpected entity — it matched a similar registered name; search the exact registry ID.
• No rows for a name — try the entity’s exact legal name or its registry ID.

⚖️ Is it legal to scrape this data?

This actor reads the public USPTO trademark database. Results can still contain personal data (e.g. a person’s name); personal data is protected by the GDPR and similar laws, so only process it with a legitimate basis. See Apify’s blog post on the legality of web scraping.

🤝 Support & contact

• 🌐 Website: data.foxlabs.com.tr
• 📧 Email: info@foxlabs.com.tr
• 🐛 Issues: open a ticket in the Actor’s Issues tab
• 🧰 More clean B2B data actors: Fox Labs on Apify

Changelog

0.1.8 — 2026-09-20 — README examples corrected against the real input schema

• The README's code examples did not match this Actor. They used queries and maxResultsPerQuery — keys that do not exist in this Actor's input schema — with a placeholder value, and the input table listed those same phantom fields. Anyone who copied the AI-agent, cURL, JavaScript or Python example got a failing run. Every example now uses the real schema and matches the Console prefill: {"mode":"new_filings","maxResults":20}
• The input table is regenerated from input_schema.json, so it lists the fields the Actor actually accepts.
• Removed claims carried over from the same generator template where present: "formation / status monitoring", "a canonical registry record for KYB and due diligence", "every row carries query", and industry described as a NACE code.
• No code, output field or pricing change.

0.1 — 2026-09-07

• Enabled AI-agent payments (x402) + rebuilt the README to the full standard (What-is / when, AI-agents + x402 agentic payments + MCP, Overview, Features, Use cases, Integration, FAQ, Troubleshooting, Support & contact).

0.0

• Initial release: data from the USPTO trademark database (official open data) by name or registry ID.