# UCC Filing Monitor — Debtor & Lender Leads (`intelscrape/ucc-filing-monitor`) Actor

Monitor new UCC lien filings from official state SOS open data (CT, CO). Daily new-filing delta, debtor watchlist hits, and 5-year lapse/continuation deadline alerts. Debtor and secured party details included. No captcha, no API key.

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

## Pricing

from $2.00 / 1,000 dataset items

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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

## UCC Filing Monitor

![Actor Banner](https://api.apify.com/v2/key-value-stores/PyvJzfQg02FD3RYhd/records/ucc-filing-monitor-banner.png)

Monitor **new UCC lien filings** from official state Secretary of State **open data** (Connecticut and Colorado Socrata portals).

### What you get

- **new-filings** — only liens published since your last run (cursor per Tracker ID)
- **watchlist** — hits when a named debtor appears
- **lapse-alerts** — active liens entering the continuation / lapse window

Each dataset item is **one filing** (debtors + secured parties grouped). Billing is **pay-per-event** via `Actor.pushData` → `apify-default-dataset-item`.

### Sources (public SOS open data)

| State | Portal |
|-------|--------|
| CT | https://data.ct.gov/d/xfev-8smz |
| CO | https://data.colorado.gov/d/wffy-3uut |

No captcha, no paid skip-trace API, no login.

### Demo input

```json
{
  "mode": "new-filings",
  "states": ["CT"],
  "trackerId": "demo-smoke",
  "maxResults": 5,
  "lookbackDaysOnFirstRun": 1,
  "resetTracker": true
}
```

### Notes

- First run seeds a baseline (billed like any delivery). Use `lookbackDaysOnFirstRun: 1` for a cheap smoke test.
- Share a `trackerId` across scheduled runs to receive only the delta.

### Free analytics batch-summary

When `includeFilingsAnalytics` is true (default ON), the actor appends one free `ucc-filing-batch-summary` row with state/type/change/debtor rates. No extra PPE charge. SoftCTA mesh frozen at `SOFTCTA_LINKS_UCC_FILING_1_2_7`.

# Actor input Schema

## `mode` (type: `string`):

new-filings = only liens filed since your last run (the daily feed). watchlist = only filings against businesses you are tracking. lapse-alerts = active liens entering their 5-year continuation window.

## `states` (type: `array`):

Which state registries to monitor. Both publish official UCC data daily.

## `trackerId` (type: `string`):

Names this watch's memory. Runs sharing a Tracker ID share one cursor, so each run returns only what the previous one did not. Use separate IDs for separate watches (e.g. 'equipment-leads' vs 'portfolio-monitoring').

## `watchlist` (type: `array`):

Business names to watch for (partial match, case-insensitive). Used in watchlist mode — get alerted when a competing secured party files against a business you have lent to.

## `lapseWithinDays` (type: `integer`):

For lapse-alerts mode: how far ahead to look for liens approaching lapse. A UCC-1 dies 5 years after filing unless continued, and the continuation window opens 6 months (180 days) before.

## `filingTypes` (type: `array`):

Optional filter, partial match (e.g. 'ORIG FIN STMT' for original filings only, 'AMENDMENT', 'RELEASE'). Leave empty for all.

## `debtorState` (type: `string`):

Optional: only return filings whose DEBTOR address is in this state (e.g. 'CT'). Useful when you only sell into one territory.

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

Maximum FILINGS this run may deliver and bill. One filing = one billable row, even when the source lists several debtors for it. A default weekday delta across CT+CO is roughly 200-500 filings; a first run with a 7-day lookback can reach this ceiling, so lower it if you want a cheaper first run.

## `lookbackDaysOnFirstRun` (type: `integer`):

On the very first run there is no cursor, so this decides how much history seeds the baseline. 7 days across CT+CO is several hundred filings and is billed like any other delivery - set it to 1 for a cheap first run. Later runs ignore this.

## `resetTracker` (type: `boolean`):

Wipe this Tracker ID's memory and rebuild the baseline. Turn on only if you want to re-pull history you already received.

## `requirePartyInfo` (type: `boolean`):

Filter out purely administrative filings that carry no debtor and no secured party in the source data (e.g. CT 'OFFICE CORRECT' rows). These cannot tell you who filed or who is lapsing. Turn off to receive them anyway.

## `includeFilingsAnalytics` (type: `boolean`):

When true (default ON), push one free ucc-filing-batch-summary row with state/type/change/debtor breakdowns and SoftCTA. No extra PPE charge.

## `demoMode` (type: `boolean`):

Push synthetic UCC filing fixtures with SoftCTA (no portal I/O).

## Actor input object example

```json
{
  "mode": "new-filings",
  "states": [
    "CT",
    "CO"
  ],
  "trackerId": "default",
  "lapseWithinDays": 180,
  "maxResults": 500,
  "lookbackDaysOnFirstRun": 7,
  "resetTracker": false,
  "requirePartyInfo": true,
  "includeFilingsAnalytics": true,
  "demoMode": false
}
```

# Actor output Schema

## `filings` (type: `string`):

Dataset of delivered UCC filings (one item per filing).

# 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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("intelscrape/ucc-filing-monitor").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 = {}

# Run the Actor and wait for it to finish
run = client.actor("intelscrape/ucc-filing-monitor").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 '{}' |
apify call intelscrape/ucc-filing-monitor --silent --output-dataset

```

## MCP server setup

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

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/trD26PHNkbLEjQHSG/builds/8pHThghatbPUKuAjm/openapi.json