# Trademark Filing Watch: New USPTO Application Alerts (`accountable_eel/trademark-filing-watch`) Actor

Watch my brand for similar trademark filings? Get new USPTO and EUIPO trademark applications that contain or resemble your marks, by Nice class. One row per filing with owner, classes and record link. Monitoring bills only new matches; alerts to Slack, Discord or Telegram, or Google Sheets.

- **URL**: https://apify.com/accountable_eel/trademark-filing-watch.md
- **Developed by:** [Adriana Voss](https://apify.com/accountable_eel) (community)
- **Categories:** Lead generation, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $5.00 / 1,000 new trademark filing matcheds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Trademark Filing Watch: New USPTO Application Alerts

Watch USPTO and EUIPO for new trademark applications that contain or resemble your marks, by Nice class. One row per filing with the owner, classes and a record link. Monitoring bills only new matches, and can alert Slack, Discord or Telegram. No API key and no proxy. EUIPO is searched through TMview (`adFrom` / `adTo`). If USPTO later requires a token, the fallback is the official bulk daily XML on bulkdata.uspto.gov; that path is not built yet.

### How to use

1. **In the Apify Console.** Open the actor page and click **Start** — the `terms` field is already pre-filled with a working example. Results land in the run's dataset as soon as each item is found.
2. **Via the API.** Call it directly with a POST request — no Console needed once you have an API token:
   ```bash
   curl "https://api.apify.com/v2/acts/accountable_eel~trademark-filing-watch/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
     -X POST \
     -H "Content-Type: application/json" \
     -d '{"terms":["cloud"]}'
   ```
3. **On a schedule.** Save this actor as an Apify **Task** with the input you want, then add a **Schedule** (hourly, daily, weekly) so it runs on its own — no server of your own required.

### Input

```json
{
  "terms": [
    "cloud"
  ]
}
```

One mark per line. Each line is searched on its own. By default a filing matches when the word mark contains the term. Accepted formats: cloud, ClassCloud, your brand.

### Example runs

For brand owners and IP attorneys. Change the field named in each note.

**1. Watch my brand (who: brand protection).** Change `terms`.

```json
{ "terms": ["yourbrand"], "matchMode": "similar", "onlyNewSinceLastRun": true }
```

**2. New software trademarks in classes 9 and 42 (who: agency lead-gen).** Change `classes`.

```json
{ "terms": ["ai"], "classes": [9, 42], "sinceDays": 7 }
```

**3. New filings by keyword (who: a category watch).** Change `terms`.

```json
{ "terms": ["coffee"], "classes": [30, 43], "sinceDays": 14 }
```

### Output

One row per item, for example:

| query | found | status | filingCount | filings | searchSummary | monitorStatus | truncated | notifyErrors | office | serialNumber | mark | matchType | similarityScore | filedDate | liveStatus | statusCode | ownerNames | niceClasses | goodsAndServices | recordUrl | isNew | firstSeenAt | scrapedAt |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| cloud | true | OK | <filings returned> | \<all filings (full list)> | <search run> | <monitoring status> | <more results were available> | <alert delivery errors> | <office> | <serial or application number> | <word mark> | <how it matched> | <edit distance> | <filed on> | <live or dead> | <uspto status code> | <owners> | <nice classes> | <goods and services> | <record page> | \<is this filing new?> | <first seen on a run> | 1970-01-01T00:00:00.000Z |

A miss comes back as a row with `"found": false` and is never charged.

### Pricing

- **New trademark filing matched**: $10 per 1,000 filings

Plus a $0.002 start fee per run. Each event above is billed independently, only when it actually returns data — misses (`found:false`) are never charged.

### Use it from Clay, n8n, Make, or an AI agent

This actor runs synchronously over plain HTTP — call it directly from a script, a workflow tool, or an AI agent, no Apify Console needed once you have an API token.

```bash
curl "https://api.apify.com/v2/acts/accountable_eel~trademark-filing-watch/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
  -X POST \
  -H "Content-Type: application/json" \
  -d '{"terms":["cloud"]}'
```

**n8n.** Add an HTTP Request node: Method `POST`, URL `https://api.apify.com/v2/acts/accountable_eel~trademark-filing-watch/run-sync-get-dataset-items?token=<YOUR_TOKEN>`, Body Content Type `JSON`, JSON Body `{"terms":["cloud"]}` (swap in an expression from an earlier node for a real value).

**Clay.** Add an "HTTP API" column: Method `POST`, URL `https://api.apify.com/v2/acts/accountable_eel~trademark-filing-watch/run-sync-get-dataset-items?token=<YOUR_TOKEN>`, Body `{"terms":["{{term}}"]}`, mapping the row's term into the `terms` array.

**MCP.** In Claude, Cursor, or any MCP client with the Apify MCP server, ask for "trademark watch for new USPTO filings" — the agent will find and run this actor.

# Actor input Schema

## `terms` (type: `array`):

One mark per line. Each line is searched on its own. By default a filing matches when the word mark contains the term. Accepted formats: cloud, ClassCloud, your brand. You're only charged for the ones we actually find — a miss costs nothing.

## `offices` (type: `string`):

USPTO is the United States trademark register. EUIPO is the European Union register, searched through TMview. Both runs one search per mark on each register.

## `matchMode` (type: `string`):

Contains: the word mark includes the term. Exact: the whole word mark equals the term. Similar: contains, or the normalized edit distance is 2 or less, or the consonant skeleton is the same (Kloud matches Cloud). Similar is scored locally over a wider candidate set.

## `classes` (type: `array`):

Optional. Nice class numbers, for example 9 and 42. Empty means every class.

## `liveOnly` (type: `boolean`):

On: drop dead, expired, refused or withdrawn filings. Off: include them.

## `excludeOwners` (type: `array`):

Optional. Your own company names. A filing is dropped when an owner name contains one of these, so your own applications do not alert you.

## `sinceDays` (type: `integer`):

1 to 90. Filings with a filing date in the last N days. For a daily schedule, 7 covers a weekend.

## `testRun` (type: `boolean`):

Turn this on to test your input on a small sample before running the full list. Turn it off to process everything.

## `onlyFound` (type: `boolean`):

Only keep rows where something was actually found. Misses are always free, whether or not you show them here.

## `includeKeywords` (type: `array`):

Optional. Only keep results that mention at least one of these words (e.g. a job title, a city, a product name). Leave empty to keep everything.

## `excludeKeywords` (type: `array`):

Optional. Drop any result that mentions one of these words. Leave empty to skip nothing.

## `maxResults` (type: `integer`):

1 to 500. Caps how many filings you get (and pay for) for each watched mark.

## `onlyNewSinceLastRun` (type: `boolean`):

On: only filings this watchlist has not returned before are returned and charged. Run it on a schedule. Off: every matching filing is returned every time. A filing not seen for 180 days is forgotten. Status changes on a filing you have already seen are not alerted.

## `deltaName` (type: `string`):

Optional. Name this search's monitoring memory so two schedules stay separate, or so a filter change keeps one memory. Leave empty to derive one from your filters.

## `notifyUrl` (type: `string`):

Optional. After new filings are billed, each one is posted here: mark, owner, classes, filed date and the record link. Discord or Slack: paste the channel webhook URL. Telegram: https://api.telegram.org/bot<token>/sendMessage?chat_id=<chat id>. Any other URL receives JSON. Messages are free. A message that fails never fails the run (notifyErrors says why). Stored encrypted, never logged or written into the results.

## `notifyFormat` (type: `string`):

Leave on Detect from the link. discord.com gets a Discord message, hooks.slack.com Slack, api.telegram.org Telegram, anything else JSON.

## `maxNotificationsPerRun` (type: `integer`):

Up to 100. Above this, one +N more message says how many more filings are in the dataset, so a busy first run does not flood the channel.

## `columns` (type: `array`):

Choose which pieces of information to include in each result row. All are included by default.

## `expandRows` (type: `boolean`):

When on, each filing found gets its own row instead of being grouped under its term. You're still only charged once per term, no matter how many rows it produces.

## `maxConcurrency` (type: `integer`):

Parallel requests. Keep conservative — this target has no browser fallback, so getting blocked costs more than slow-and-steady.

## Actor input object example

```json
{
  "terms": [
    "cloud"
  ],
  "offices": "US",
  "matchMode": "contains",
  "classes": [],
  "liveOnly": true,
  "excludeOwners": [],
  "sinceDays": 7,
  "testRun": false,
  "onlyFound": false,
  "includeKeywords": [],
  "excludeKeywords": [],
  "maxResults": 50,
  "onlyNewSinceLastRun": false,
  "deltaName": "",
  "notifyFormat": "auto",
  "maxNotificationsPerRun": 20,
  "columns": [
    "filingCount",
    "filings",
    "searchSummary",
    "monitorStatus",
    "truncated",
    "notifyErrors",
    "office",
    "serialNumber",
    "mark",
    "matchType",
    "similarityScore",
    "filedDate",
    "liveStatus",
    "statusCode",
    "ownerNames",
    "niceClasses",
    "goodsAndServices",
    "recordUrl",
    "isNew",
    "firstSeenAt"
  ],
  "expandRows": true,
  "maxConcurrency": 2
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "terms": [
        "cloud"
    ],
    "classes": [],
    "excludeOwners": [],
    "includeKeywords": [],
    "excludeKeywords": []
};

// Run the Actor and wait for it to finish
const run = await client.actor("accountable_eel/trademark-filing-watch").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "terms": ["cloud"],
    "classes": [],
    "excludeOwners": [],
    "includeKeywords": [],
    "excludeKeywords": [],
}

# Run the Actor and wait for it to finish
run = client.actor("accountable_eel/trademark-filing-watch").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "terms": [
    "cloud"
  ],
  "classes": [],
  "excludeOwners": [],
  "includeKeywords": [],
  "excludeKeywords": []
}' |
apify call accountable_eel/trademark-filing-watch --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,accountable_eel/trademark-filing-watch"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/7u3uqyKMRQoMNlgO2/builds/am7XgC2mzhGJMDZGd/openapi.json
