# US New Business Filings: New LLCs & Corporations (NY, CO, CT) (`clearpath-data/us-new-business-filings`) Actor

Daily feed of newly registered LLCs, corporations and nonprofits from the New York, Colorado and Connecticut open-data portals. Filter by state, entity type and name keyword; get only filings since your last run. One clean schema plus raw fields.

- **URL**: https://apify.com/clearpath-data/us-new-business-filings.md
- **Developed by:** [Clearpath Data](https://apify.com/clearpath-data) (community)
- **Categories:** Lead generation, Business
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.50 / 1,000 new business 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

### US New Business Filings: New LLCs & Corporations (NY, CO, CT)

Get a feed of **newly registered businesses** in New York, Colorado and Connecticut: new LLCs, corporations, nonprofits and partnerships, read from each state's official open-data portal. Run it daily and you get only the filings you haven't seen yet, in one clean schema across the three states, with each state's original fields kept alongside.

**Price:** $0.0015 per filing saved ($1.50 per 1,000). Set `maxResults` or your maximum cost per run to cap the spend.

### What does it do?

- Reads the business-registry datasets that the three states publish on their open-data portals:
  - **New York:** Department of State, *Active Corporations: Beginning 1800* (data.ny.gov)
  - **Colorado:** Secretary of State, *Business Entities in Colorado* (data.colorado.gov)
  - **Connecticut:** Secretary of the State, *Connecticut Business Registry – Business Master* (data.ct.gov)
- **New since last run** (the default): returns only filings you haven't received yet. The first run already returns real data: every matching filing from the last 7 days (`firstRunLookbackDays`, 1 to 90). There's no empty "baseline only" run. Every later run picks up from where the last one stopped.
- **Date range:** returns every filing between two dates, for backfills or one-off lists.
- **Filters** run on the portal side, so you only download (and pay for) what you need:
  - state;
  - entity type (LLC, corporation, nonprofit, partnership, cooperative);
  - domestic or foreign;
  - keywords in the name.
- **Personal data is kept to a minimum.** Rows carry the business's city, state and ZIP. Street addresses are added only if you switch them on, and individuals' names (registered agents, officers) are never included. See [Personal data](#personal-data-use-it-responsibly).

### Quick start

1. Click **Try for free**. The prefill reads Colorado's filings from the last 7 days and stops at 50, so the first run returns data straight away.
2. Add New York and Connecticut, filters or keywords, and press **Start**.
3. Schedule it daily (Console → Schedules) with the same **State name** to get each day's new filings.
4. Or call it from code:

```bash
curl -X POST "https://api.apify.com/v2/acts/clearpath-data~us-new-business-filings/runs?token=YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"states": ["NY", "CT"], "entityTypes": ["llc"], "keywords": ["construction"], "stateName": "ny-ct-construction"}'
```

### Sample output

| filingDate | state | entityName | entityTypeGroup | domesticOrForeign | city | postalCode | status |
|---|---|---|---|---|---|---|---|
| 2026-10-16 | NY | CLOWERS AI DEVELOPMENT, INC. | corporation | domestic | West Seneca | 14224 | Active |
| 2026-10-16 | NY | INOA MOTIVE INC. | corporation | domestic | BRONX | 10460 | Active |
| 2026-10-16 | CO | Vila Biotechnology LLC | llc | domestic | Lakewood | 80226 | Good Standing |
| 2026-10-16 | CO | Tavernoq Inc | corporation | domestic | Boulder | 80302 | Good Standing |
| 2026-10-16 | CT | STONE NAILS BAR LLC | llc | domestic | Waterbury | 06705-2624 | Active |
| 2026-10-16 | CT | NJSB Construction, LLC | llc | foreign | Glastonbury | 06033 | Active |

*Real rows from a test run on 2026-10-19.* Connecticut rows also carry an industry code and description (e.g. 238350, "Finish Carpentry Contractors"). Every row has `entityType` (the state's own type name), `jurisdictionOfFormation`, `sourceUrl`, and a `raw` object holding the state's own fields (minus the personal fields described below).

**How many filings to expect.** In the same test, 2026-10-12 to 2026-10-18 gave **8,676 filings**: NY 4,574, CO 3,173, CT 929. That's about 1,240 a day, and fewer at weekends. It's one week of data, not a forecast.

### How "new since last run" works

- Each US state's progress is saved under your **State name**, in a key-value store named `us-new-business-filings-state` in your own Apify account. It records the latest filing date delivered and the IDs delivered in the last 7 days.
- Each run first re-checks those 7 days for filings the portal loaded late (new IDs with older dates), then takes everything filed after the last delivered date. You don't get duplicates, and late-loaded filings aren't missed.
- If a run stops at **Max results** or your maximum cost, the next run continues where it stopped.
- **No saved state** (new account, or the store was deleted)? Pick an earlier run's dataset in **Previous run's dataset** and the run continues from there.
- Use a different **State name** for each schedule or filter set.

### Use cases

- **B2B sales and lead generation:** new LLCs in your area or niche, e.g. keywords "construction", "dental" or "roofing".
- **Service providers for new businesses:** accountants, banks, insurers, payroll and web agencies looking for companies in their first weeks.
- **Market research:** formation trends by state, entity type, industry (CT) or ZIP code.
- **Compliance and KYC:** check a counterparty's registration date and status against the state record.

### Input

| Field | Default | What it does |
|---|---|---|
| `states` | all three | "NY", "CO", "CT" |
| `mode` | "new" | "new" = since last run; "range" = between `filedFrom` and `filedTo` |
| `filedFrom` / `filedTo` | | "2026-10-01" or relative like "7 days" |
| `firstRunLookbackDays` | 7 | How far back the first run goes (1 to 90) |
| `entityTypes` | all | "llc", "corporation", "nonprofit", "partnership", "cooperative", "other" |
| `jurisdiction` | "any" | "domestic" (formed in that state) or "foreign" (formed elsewhere, registered there) |
| `keywords` | | Names containing any of these (case-insensitive) |
| `includeStreetAddresses` | false | Add street lines (see Personal data) |
| `stateName` | "default" | Name of the saved progress |
| `baselineDatasetId` | | Continue from an earlier run's dataset instead |
| `updateState` | true | Save progress for the next run |
| `maxResults` | 1000 | Stop after this many filings (0 = no limit) |

### Integrations, schedules and AI agents

- **Schedules:** Schedule it daily with the same **State name** to get each day's new filings. See [Apify schedules](https://docs.apify.com/platform/schedules).
- **No-code tools:** send results to Google Sheets, Slack or a CRM with Apify's [Make](https://docs.apify.com/platform/integrations/make), [Zapier](https://docs.apify.com/platform/integrations/zapier) or [n8n](https://docs.apify.com/platform/integrations/n8n) integrations, or a [webhook](https://docs.apify.com/platform/integrations/webhooks) when a run finishes.
- **AI agents (MCP):** connect an MCP client such as Claude Code or Cursor to `https://mcp.apify.com?tools=clearpath-data/us-new-business-filings` and the agent can run this Actor directly. See the [Apify MCP server](https://docs.apify.com/platform/integrations/mcp) docs.

### How much does it cost?

| What | Price |
|---|---|
| New business filing (one row saved) | $0.0015 ($1.50 per 1,000) |
| Actor start (Apify standard) | $0.00005 per GB of memory, per run |

**Examples:**

- The prefill (Colorado, 50 filings): about **$0.08**.
- All three states daily, at the test week's rate of about 1,240 filings a day (an estimate): about **$1.86 a day**.
- New LLCs with "construction" in the name, NY and CT, daily: a few to a few dozen a day, so cents.

Platform usage (compute) is billed by Apify separately as usual. A typical daily run takes seconds at 256 MB.

### Personal data: use it responsibly

Business registries are public records, but they contain personal data. Many small businesses register a **home address**, and registered agents and officers are often **named individuals**. So this Actor:

- **never outputs individuals' names**: no individual registered agents, no New York chairman, service-of-process or registered-agent names. They're stripped from `raw` too. Colorado registered agents that are organisations (e.g. "Northwest Registered Agent LLC") are kept, because they are businesses. New York's agent field doesn't say whether the agent is a person or a company, so it is never included.
- **leaves out street addresses by default.** Rows have city, state and ZIP only. Street lines are added only if you turn on `includeStreetAddresses`, and those rows carry `personalDataIncluded: true`.
- **never collects** Connecticut's e-mail address fields or its owner-demographic flags (woman-, veteran-, minority-, disability- and LGBTQI-owned).
- Business names themselves sometimes contain a person's name (e.g. "Jane Smith Consulting LLC"); that's part of the public record and can't be removed.

You are responsible for having a lawful basis for how you use this data, under the laws that apply to you: for example the GDPR or UK GDPR if you or the people concerned are in Europe, or US state privacy laws. That matters most if you switch street addresses on. Collect only what you need, keep it only as long as you need it, honour opt-outs and deletion requests, and follow e-mail, phone and postal marketing rules (e.g. CAN-SPAM, the TCPA). Don't use this data to harass anyone or to decide on credit, employment, insurance or housing. If you're unsure, ask a lawyer.

### Limits and honest notes

- **Three states only:** New York, Colorado and Connecticut. Other states aren't covered.
- **New York lists active corporations only.** A New York entity that dissolved before you ran this won't appear. NY rows have no status field, so they are marked "Active". New York's metadata says the dataset is posted monthly; in the test it had been updated on 2026-10-17, with filings up to 2026-10-16.
- **Portals lag by a day or more.** Filings appear when each state refreshes its dataset, and some arrive late with older dates (the 7-day re-check catches those).
- **What "filing date" means:** NY = initial DOS filing date; CO = entity form date; CT = registration date. Foreign entities (registered in a state but formed elsewhere) are included unless you filter them out.
- **Entity types are mapped to broad groups.** The original type is always kept in `entityType`. CT "Non-Stock" corporations are grouped as nonprofit.
- **Addresses:** CO and CT give the principal office. NY gives a location address when one exists, otherwise the service-of-process address (where legal papers go, often a lawyer or agent). See `addressType`.
- **Polite access:** no API key or app token. One request at a time per portal, at least 1 second apart, smaller pages when Max results is low, and automatic back-off when a portal says it's busy (HTTP 429). Very large date ranges take a little longer.
- **No guarantees from the states:** the data is provided "as is". See the notices below.

### Sources, licences and notices

- **New York:** data from the New York State Department of State, via data.ny.gov ([dataset](https://data.ny.gov/d/n9v6-gdp6)), used under the OPEN-NY Terms of Use.
- **Colorado:** data from the Colorado Department of State, via data.colorado.gov ([dataset](https://data.colorado.gov/d/4ykn-tg5h)), public domain. The State of Colorado's terms require this notice, which is also on every Colorado row (`sourceDisclaimer`):

  > The data made available here has been modified for use from its original source, which is the State of Colorado. THE STATE OF COLORADO MAKES NO REPRESENTATIONS OR WARRANTY AS TO THE COMPLETENESS, ACCURACY, TIMELINESS, OR CONTENT OF ANY DATA MADE AVAILABLE THROUGH THIS SITE. THE STATE OF COLORADO EXPRESSLY DISCLAIMS ALL WARRANTIES, WHETHER EXPRESS OR IMPLIED, INCLUDING ANY IMPLIED WARRANTIES OF MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE. The data is subject to change as modifications and updates are complete. It is understood that the information contained in the Web feed is being used at one's own risk.
- **Connecticut:** data from the Connecticut Secretary of the State, via data.ct.gov ([dataset](https://data.ct.gov/d/n7gp-d28j)), public domain, provided "as is".
- This Actor is independent and is not affiliated with or endorsed by any state.

### FAQ

**How fresh is the data?** As fresh as each portal. In the test on 2026-10-19, the latest filing dates were 2026-10-16 (NY), 2026-10-18 (CO) and 2026-10-17 (CT).

**Can I get one county or ZIP code?** Filter the dataset on `county` (NY) or `postalCode` after the run, or use name keywords. There are no address filters in v1.

**Why did I get 0 filings?** Either nothing new has been filed since your last run, or the portal hasn't refreshed yet. The run report (`RUN_REPORT`) shows each state's date window and counts.

**Can I export to CSV or Excel?** Yes. Use the **New filings** view and download as CSV, Excel, JSON or XML.

**Can I get e-mail addresses?** No. Connecticut's e-mail fields are deliberately excluded, and the other two states don't publish e-mails.

### Other Clearpath Data Actors

| Actor | What it does |
|---|---|
| [companies-house-new-companies](https://apify.com/clearpath-data/companies-house-new-companies) | New UK companies from Companies House, with officers and PSCs |
| [uk-visa-sponsor-register](https://apify.com/clearpath-data/uk-visa-sponsor-register) | UK visa sponsor licence list from the GOV.UK register, with a changes feed |
| [lei-lookup](https://apify.com/clearpath-data/lei-lookup) | LEI lookup via the GLEIF API (LEI, name, BIC, ISIN) |
| [hiring-changes-monitor](https://apify.com/clearpath-data/hiring-changes-monitor) | Jobs each company opened or closed since your last run |
| [ats-jobs-by-company](https://apify.com/clearpath-data/ats-jobs-by-company) | All open jobs from Greenhouse, Lever, Ashby, Workable, SmartRecruiters and Recruitee boards |
| [remote-jobs-aggregator](https://apify.com/clearpath-data/remote-jobs-aggregator) | Remote jobs from Remote OK and Himalayas |

# Changelog

This Actor's version history is a separate document: https://apify.com/clearpath-data/us-new-business-filings/changelog.md

# Actor input Schema

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

Which state registries to read. NY = New York Department of State (data.ny.gov), CO = Colorado Secretary of State (data.colorado.gov), CT = Connecticut Secretary of the State (data.ct.gov). Leave empty for all three.

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

New since last run: only filings you haven't received yet under this state name (the first run covers the last few days). Date range: every filing in the dates below; nothing is remembered.

## `filedFrom` (type: `string`):

First filing date, as 2026-10-01 or relative like "7 days". Required for Date range; in New since last run it sets where the first run starts.

## `filedTo` (type: `string`):

Last filing date (inclusive) for Date range. Leave empty for up to today.

## `firstRunLookbackDays` (type: `integer`):

When there's no saved state yet (and no "Filed from"), the first run covers this many days back.

## `entityTypes` (type: `array`):

Only these kinds of entity. Each state's own type names are mapped to these groups (the original is kept in entityType). Leave empty for all.

## `jurisdiction` (type: `string`):

Domestic = formed in that state. Foreign = formed elsewhere and registered to do business there.

## `keywords` (type: `array`):

Only entities whose name contains one of these (case-insensitive), e.g. "construction", "dental", "holdings".

## `includeStreetAddresses` (type: `boolean`):

Off by default: rows have city, state and ZIP only. Many small businesses register a home address. Turn on only if you have a lawful reason to process it. People's names (individual agents, officers) are never included.

## `stateName` (type: `string`):

New since last run remembers what you've received under this name in a key-value store named "us-new-business-filings-state" in your account. Use one name per schedule or filter set. Letters, digits and hyphens.

## `baselineDatasetId` (type: `string`):

Optional. Instead of the saved state, continue from the dataset of an earlier run of this Actor (filings after its latest date, plus late-loaded ones).

## `updateState` (type: `boolean`):

Remember what this run delivered so the next run continues from here. Turn off for a one-off test.

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

Stop after this many filings (0 = no limit). New since last run continues from where it stopped next time.

## Actor input object example

```json
{
  "states": [
    "CO"
  ],
  "mode": "new",
  "firstRunLookbackDays": 7,
  "entityTypes": [],
  "jurisdiction": "any",
  "keywords": [],
  "includeStreetAddresses": false,
  "stateName": "default",
  "updateState": true,
  "maxResults": 50
}
```

# Actor output Schema

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

One row per new business filing

## `runReport` (type: `string`):

Per-state window, counts, state used, stop reason, warnings and sources

# 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": [
        "CO"
    ],
    "maxResults": 50
};

// Run the Actor and wait for it to finish
const run = await client.actor("clearpath-data/us-new-business-filings").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": ["CO"],
    "maxResults": 50,
}

# Run the Actor and wait for it to finish
run = client.actor("clearpath-data/us-new-business-filings").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": [
    "CO"
  ],
  "maxResults": 50
}' |
apify call clearpath-data/us-new-business-filings --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,clearpath-data/us-new-business-filings"
        }
    }
}
```

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/RLFa5gJNRsfoTAq87/builds/U7g2U0x4ymIU3JvR5/openapi.json