# SERFF Rate Filing Monitor — New Filings Daily, No Login (`chimerical_quicklime/serff-rate-filing-monitor`) Actor

Scheduled monitor for NAIC SERFF Filing Access. Watches one or more states for new insurance rate and form filings and returns only filings not seen on previous runs. Pay only for new filings; optional webhook alerts. No login. MCP-ready for AI agents. $20 per 1,000 new filings.

- **URL**: https://apify.com/chimerical\_quicklime/serff-rate-filing-monitor.md
- **Developed by:** [Khrystyna Skotte](https://apify.com/chimerical_quicklime) (community)
- **Categories:** Lead generation, Automation, Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $20.00 / 1,000 new filings

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

## SERFF Rate Filing Monitor

Watches NAIC **SERFF Filing Access** state portals on a schedule and returns **only the insurance rate and form filings that are new since the last run**. Point it at one or more states, optionally narrow it to a company, product or type of insurance, run it daily, and get a clean feed of new filings (plus an optional webhook alert) instead of re-downloading the same 100,000 rows.

You are charged only for **new** filings. Filings already reported on an earlier run are free.

### What it does

1. Searches each state's SERFF Filing Access portal for filings submitted in the last `lookbackDays` days.
2. Compares every filing against the monitor's memory of filings it has already reported.
3. Pushes the new filings to the dataset (with `firstSeenAt`) and remembers them.
4. Optionally POSTs a JSON summary to your `webhookUrl`.

Memory lives in a named key-value store `serff-monitor-<hash of monitorId>` on your Apify account, so it survives between runs and between builds. Use a different `monitorId` for each independent watch list.

### Scheduling (the intended way to use it)

1. Create a task from this actor with your states/filters.
2. Run it once with `firstRunMode: "baseline"`. That run records every filing currently in the window and returns **nothing**. From then on only filings submitted after the baseline are reported.
3. Add an **Apify Schedule** (e.g. daily at 07:00) for the task. Every scheduled run returns only what is new.
4. Keep `lookbackDays` larger than the schedule interval (7 days for a daily schedule is a safe default), so a missed or failed run cannot lose filings.

If you skip the baseline, the first run reports everything in the window as new (default `firstRunMode: "emitAll"`), which is also how the actor's default test run behaves.

### Input

| Field | Default | Description |
|---|---|---|
| `states` | `["TX"]` | Two-letter codes of the state portals to watch. Each is searched separately. Every state plus DC works except FL and PR, which are not on SERFF Filing Access. |
| `businessType` | `P` | `P` = Property & Casualty, `L` = Life, Accident/Health, Annuity, Credit. |
| `companyName` | `""` | Partial company-name match. |
| `companyCode` | `""` | NAIC company code. |
| `productKeyword` | `""` | SERFF product-name search. |
| `typeOfInsurance` | `""` | Keeps filings whose type of insurance code or name contains this text (e.g. `19.0`, `Personal Auto`). |
| `lookbackDays` | `7` | Submission-date window: today minus N days to today. |
| `includeDetails` | `false` | Opens each new filing's detail page for dates, statuses and company addresses. Slower. |
| `maxNewFilings` | `10` | Cap on new filings per run. Filings past the cap are not marked as seen, so they come out on the next run. Raise it for scheduled use. |
| `firstRunMode` | `emitAll` | `baseline` = record existing filings and emit nothing on the first run of this `monitorId`. |
| `webhookUrl` | `""` | POST target for the per-run summary. |
| `monitorId` | `default` | Namespaces the seen-set. One ID per watch list. |
| `proxyConfiguration` | Apify RESIDENTIAL | SERFF blocks datacenter IPs; keep residential. |

### Output

One record per new filing:

```json
{
  "filingId": "134895644",
  "serffTrackingNumber": "FDLY-134895644",
  "companyName": "Stillwater Insurance Company",
  "naicCompanyCode": "25180",
  "productName": "Homeowners",
  "typeOfInsuranceCode": "04.0000",
  "typeOfInsuranceName": "Homeowners Sub-TOI Combinations",
  "filingType": "Specimen Policy",
  "filingStatus": "ASIS",
  "filingStatusDescription": "Assigned to Intake Staff",
  "state": "TX",
  "businessType": "Property & Casualty",
  "detailUrl": "https://serff-sfa.naic.org/serff/sfa/search/filingSummary.xhtml?filingId=134895644",
  "firstSeenAt": "2026-09-28T18:50:28.201Z",
  "monitorId": "default",
  "source": "NAIC SERFF Filing Access",
  "sourceUrl": "https://serff-sfa.naic.org/serff/sfa/home/TX"
}
```

With `includeDetails: true` each record also carries `typeOfInsurance`, `submissionDate`, `serffStatus`, `dispositionDate`, `dispositionStatus`, `stateStatus`, `stateStatusLastChanged` and a `companies` array (name, NAIC code, address, phone).

The run's key-value store also gets a `SUMMARY` record with scanned/new counts per state.

### Webhook payload

Sent once per run when `webhookUrl` is set (also when nothing is new, so it doubles as a heartbeat):

```json
{
  "monitorId": "default",
  "runAt": "2026-09-28T18:50:28.201Z",
  "newCount": 1,
  "scanned": 94,
  "states": { "TX": { "scanned": 94, "new": 1 } },
  "filings": [ { "...first 50 new filing records..." } ]
}
```

### Pricing

Pay per event: a small start fee per run plus a per-record fee **only for new filings**. A daily monitor on a quiet filter costs a few cents a day; nothing is charged for re-seen filings.

### Notes

- The monitor remembers up to 50,000 filing IDs per `monitorId` and drops the oldest beyond that.
- Resetting a monitor: delete the `serff-monitor-…` key-value store (or pick a new `monitorId`) and run a fresh baseline.
- For a one-off bulk export instead of a monitor, use the companion SERFF Insurance Rate Filings Scraper.

# Actor input Schema

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

Two-letter codes of the SERFF Filing Access state portals to watch, e.g. TX, CA, NY. Each state is searched separately. All states plus DC are available except FL and PR, which do not use SERFF Filing Access.

## `businessType` (type: `string`):

Line of business to search.

## `companyName` (type: `string`):

Only watch filings from this insurance company (partial match). Leave empty for all companies.

## `companyCode` (type: `string`):

Only watch filings from this NAIC company code. Leave empty for all.

## `productKeyword` (type: `string`):

Only watch filings whose product name matches this keyword (SERFF product name search). Leave empty for all products.

## `typeOfInsurance` (type: `string`):

Only keep filings whose type of insurance (code or name) contains this text, e.g. "19.0" or "Personal Auto". Case-insensitive. Leave empty for all.

## `lookbackDays` (type: `integer`):

How many days back the submission-date window reaches. Each run searches filings submitted between today minus this many days and today. Set it comfortably larger than your schedule interval so nothing is missed.

## `includeDetails` (type: `boolean`):

Open each new filing's detail page to add submission/disposition dates, SERFF and state status, and the filing companies with addresses. Slower.

## `maxNewFilings` (type: `integer`):

Stop after this many new filings have been returned in one run. Filings beyond the cap are not marked as seen and will be returned on the next run.

## `firstRunMode` (type: `string`):

What to do on the very first run of a monitor ID. "emitAll" returns every filing in the window as new. "baseline" silently records the filings that already exist and returns nothing, so later scheduled runs only report filings submitted after the baseline. Scheduled users should set "baseline" once.

## `webhookUrl` (type: `string`):

Optional. After each run a JSON summary {monitorId, runAt, newCount, scanned, states, filings:\[first 50 new filings]} is POSTed to this URL.

## `monitorId` (type: `string`):

Name of this monitor. The set of already-seen filings is stored per monitor ID, so use a different ID for each separate watch list (e.g. "tx-auto", "fl-homeowners").

## `proxyConfiguration` (type: `object`):

SERFF blocks datacenter IPs. Keep the Apify RESIDENTIAL proxy group.

## Actor input object example

```json
{
  "states": [
    "TX"
  ],
  "businessType": "P",
  "companyName": "",
  "companyCode": "",
  "productKeyword": "",
  "typeOfInsurance": "",
  "lookbackDays": 7,
  "includeDetails": false,
  "maxNewFilings": 10,
  "firstRunMode": "emitAll",
  "webhookUrl": "",
  "monitorId": "default",
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}
```

# Actor output Schema

## `records` (type: `string`):

Dataset of filings that are new since the previous run (JSON).

# 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 = {
    "states": [
        "TX"
    ],
    "proxyConfiguration": {
        "useApifyProxy": true,
        "apifyProxyGroups": [
            "RESIDENTIAL"
        ]
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("chimerical_quicklime/serff-rate-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 = {
    "states": ["TX"],
    "proxyConfiguration": {
        "useApifyProxy": True,
        "apifyProxyGroups": ["RESIDENTIAL"],
    },
}

# Run the Actor and wait for it to finish
run = client.actor("chimerical_quicklime/serff-rate-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 '{
  "states": [
    "TX"
  ],
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}' |
apify call chimerical_quicklime/serff-rate-filing-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,chimerical_quicklime/serff-rate-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/fUTbADeiFRmpwiO06/builds/pBrr9hTyoVfC2qOK3/openapi.json