# Colorado New Business Filings: LLC & Corp Leads (`infocomp/new-business-filings-colorado`) Actor

Colorado new business filings from Secretary of State open data: new LLCs, corporations and nonprofits, daily. Filter by date, type, city, ZIP or county. Name, entity ID, type, formation date, status, city, ZIP, county. No street or agent data. $3/1,000. Not affiliated with Colorado.

- **URL**: https://apify.com/infocomp/new-business-filings-colorado.md
- **Developed by:** [InfoComp Data](https://apify.com/infocomp) (community)
- **Categories:** Lead generation, Business, Developer tools
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$3.00 / 1,000 new business leads

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

## New Business Filings Leads: Colorado | Business Leads

Get a fresh list of **businesses that just formed or registered in Colorado**: new LLCs, corporations, nonprofits, partnerships and cooperatives, plus out-of-state companies that just registered to do business in Colorado. Each row is one business entity with its **name, Colorado entity ID, entity type, formation date, status, city, state, ZIP and county**, plus a link to its record on the Colorado Secretary of State's site.

Data comes from the **Colorado Department of State's official open dataset "Business Entities in Colorado"**, published on the State of Colorado's open-data portal with a **Public Domain** license and updated daily. The Actor uses the official keyless API, filters on the server and needs no logins, no API key and no scraping.

**Firm-level only.** The output has **no street address, no mailing address and no registered-agent data**. The Actor never even requests those columns, because new LLCs often list a home address and registered agents are often individuals.

### Who is it for?

- **B2B sales teams** selling to brand-new businesses: business banking, payroll, bookkeeping and accounting, insurance, merchant services, web design, phone systems, office space.
- **Local service providers** that want new businesses in their city, ZIP code or county.
- **Market researchers and economic developers** tracking new business formation by type, county and week.

### Pricing

**$3.00 per 1,000 leads.** One `New business lead` event ($0.003) per saved row. There's no start fee and no run fee. **Failed runs, empty results and duplicate rows are free.** If you set a maximum cost per run, the Actor stops cleanly when it reaches it.

| Leads | Price |
|---|---|
| 100 (default run) | $0.30 |
| 1,000 | $3.00 |
| A full month of Colorado filings (about 14,600) | about $44 |

### Input

| Field | Default | What it does |
|---|---|---|
| `daysBack` | 7 | Entities formed in the last N days, including today (Colorado time). Used when `dateFrom` is empty. |
| `dateFrom`, `dateTo` | empty | Exact range, `YYYY-MM-DD`. `dateTo` empty = today. Max 366 days per run. |
| `entityTypes` | all | `llc`, `corporation`, `nonprofit`, `partnership`, `cooperative`, `other`. |
| `formedIn` | `any` | `colorado` = new Colorado entities only; `outside_colorado` = out-of-state entities newly registered in Colorado. |
| `onlyGoodStanding` | true | Skip new entities that are already dissolved, withdrawn, merged or converted. |
| `cities` | any | Principal-address city, e.g. `Denver`, `Colorado Springs`. Case-insensitive. |
| `zipCodes` | any | 5-digit principal-address ZIP codes, e.g. `80202`. |
| `counties` | any | Colorado counties, e.g. `Denver`, `El Paso`. Matched by ZIP code (see "County" below). |
| `coloradoAddressOnly` | false | Skip entities whose principal address is outside Colorado. |
| `maxResults` | 100 | Stop after this many leads, newest first. |

Cities, ZIP codes and counties are combined with OR: a business matches if it's in **any** of them.

```json
{
  "daysBack": 7,
  "counties": ["Denver", "El Paso"],
  "entityTypes": ["llc", "corporation"],
  "maxResults": 500
}
```

**Tip:** schedule it daily with `"daysBack": 2` to catch each day's new filings. The State usually loads a day's filings after midnight, so "today" is often almost empty until the next morning.

### What's in each row?

| Field | Meaning |
|---|---|
| `companyName` | Entity name as filed. |
| `entityId` | Colorado Secretary of State entity ID (unique). |
| `entityType`, `entityTypeCode` | Plain-English type, e.g. "Limited Liability Company (Colorado)", and the State's code, e.g. `DLLC`. |
| `formationDate`, `daysSinceFormed` | Date the entity was formed in, or registered with, Colorado. |
| `status` | E.g. `Good Standing`. |
| `jurisdictionOfFormation`, `formedInColorado` | Where the entity was formed, e.g. `CO`, `DE`. |
| `city`, `state`, `zipCode`, `country` | Principal-address city, state, 5-digit ZIP and country. No street. |
| `county`, `countyMatch`, `possibleCounties` | See below. |
| `sosRecordUrl` | The entity's page on the Colorado Secretary of State's site. |
| `sourceUrl`, `source`, `disclaimer`, `retrievedAt` | Dataset page, credit, the State of Colorado's required disclaimer and the retrieval time. |

`companyName`, `city`, `state`, `zipCode`, `country`, `sourceUrl`, `source` and `retrievedAt` use the same names as the other InfoComp Business Leads tools, so outputs are easy to join.

**County.** The State's dataset has no county column, so county comes from the U.S. Census Bureau's 2020 ZIP (ZCTA) to county file. `county` is only filled when the ZIP lies **entirely** within one county (`countyMatch: "zip_in_one_county"`, about 62% of rows in a 30-day test). If the ZIP crosses a county line, `county` is empty and `possibleCounties` lists the counties it touches (`"zip_spans_counties"`). Nothing is guessed. A `counties` filter includes ZIPs that only partly lie in the county.

A run summary (filters, counts, HTTP requests, timing) is saved as `RUN_SUMMARY` in the run's key-value store.

### Output example

A real row from a local test run of the default input on Oct 28, 2026 (not trimmed):

```json
{
  "companyName": "Coda Motion Media LLC",
  "entityId": "20268290248",
  "entityType": "Limited Liability Company (Colorado)",
  "entityTypeCode": "DLLC",
  "formationDate": "2026-10-28",
  "daysSinceFormed": 0,
  "status": "Good Standing",
  "jurisdictionOfFormation": "CO",
  "formedInColorado": true,
  "city": "Centennial",
  "state": "CO",
  "zipCode": "80122",
  "country": "US",
  "county": "Arapahoe County",
  "countyMatch": "zip_in_one_county",
  "possibleCounties": [],
  "sosRecordUrl": "https://www.coloradosos.gov/biz/BusinessEntityDetail.do?masterFileId=20268290248",
  "sourceUrl": "https://data.colorado.gov/Business/Business-Entities-in-Colorado/4ykn-tg5h",
  "source": "Colorado Department of State (CDOS) business entity filings, dataset \"Business Entities in Colorado\" (4ykn-tg5h) on the Colorado Information Marketplace (data.colorado.gov), license: Public Domain. County from the U.S. Census Bureau 2020 ZCTA-to-County Relationship File.",
  "disclaimer": "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. Not affiliated with or endorsed by the Colorado Department of State.",
  "retrievedAt": "2026-10-28T19:22:31Z"
}
```

### Performance

In local tests on Oct 28, 2026, the default input (last 7 days, 100 leads) took **0.4 to 1.1 seconds** of Actor time with **one** HTTP request. A full 30 days of filings (**14,640 leads**) took 6.2 seconds with 3 requests and a peak of about 87 MB of memory. Default memory is 256 MB.

### Good to know

- **Volume:** Colorado had 14,640 new entities formed or registered from Sep 29 to Oct 28, 2026 (about 500 to 850 per weekday). About 78% were Colorado LLCs.
- **Some names are personal names.** Single-owner LLCs are sometimes named after their owner. Names are shown exactly as filed. Use the data in line with your own legal and marketing obligations (for example CAN-SPAM, TCPA and state privacy laws).
- **Principal address may be out of state.** About 10% of new filings list a principal address outside Colorado. Use `coloradoAddressOnly` to skip them.
- **Source changes:** if the State's API ever requires an app token or login, the Actor stops with a clear message instead of signing up for anything.

### Related InfoComp tools

- [Form D Funding Leads: New Startup & Private Raise Filings](https://apify.com/infocomp/form-d-funding-leads): companies that just raised private capital, from public SEC EDGAR Form D filings.
- [FMCSA New Carrier Leads: New MC Authorities | Business Leads](https://apify.com/infocomp/fmcsa-new-carrier-leads): trucking companies, freight brokers and forwarders whose FMCSA operating authority was just granted.
- [FMCSA Carrier Vetting & Watchlist: Authority, Insurance, Flags](https://apify.com/infocomp/fmcsa-carrier-vetting): bulk-check USDOT numbers: operating authority, insurance on file, safety flags and change alerts from FMCSA public data.
- [FDA Medical Device Establishment Leads | Business Leads](https://apify.com/infocomp/fda-device-establishment-leads): medical device makers, contract manufacturers and sterilizers from FDA registration data via openFDA.
- [OIG Exclusion Check & Medicare Opt-Out Screen - Bulk NPI LEIE](https://apify.com/infocomp/oig-exclusion-optout-screen): bulk-check NPIs against the HHS-OIG LEIE file and the CMS Medicare opt-out list.
- [SAM.gov Contract Opportunities Scraper: Federal RFPs & Bids](https://apify.com/infocomp/sam-gov-opportunities): US federal contract opportunities (RFPs, solicitations, awards) from the official SAM.gov API.
- [Tender Feed API: EU TED, UK Find a Tender & Contracts Finder](https://apify.com/infocomp/eu-uk-tenders): EU and UK public tenders in one feed, from official TED, Find a Tender and Contracts Finder APIs.
- [Greenhouse, Lever, Ashby & SmartRecruiters Jobs Scraper API](https://apify.com/infocomp/ats-jobs-feed): live job postings from Greenhouse, Lever, Ashby and SmartRecruiters via their public job-board APIs.
- [US Address Geocoder & FEMA Flood Zone Risk API](https://apify.com/infocomp/us-address-risk-enricher): batch-geocode US addresses with the Census Bureau and add FEMA flood zone and National Risk Index ratings.
- [VIN Decoder Bulk: Specs, Recalls, MPG & Fuel Cost per Mile](https://apify.com/infocomp/bulk-vin-decoder-recalls-mpg): decode VINs in bulk with NHTSA vPIC, plus recall campaigns and EPA fuel economy.
- [Academic Paper Scraper: arXiv, PubMed, Crossref & OpenAlex API](https://apify.com/infocomp/scholarly-paper-search): search arXiv, PubMed, Crossref and OpenAlex in one run, de-duplicated by DOI.
- [CMS Home Health, Hospice & Dialysis Leads | Business Leads](https://apify.com/infocomp/cms-facility-leads): Medicare-certified home health agencies, hospices and dialysis centers from CMS open data, facility-level.
- [HUD Multifamily Owner/Manager Leads | Business Leads](https://apify.com/infocomp/hud-multifamily-leads): HUD-assisted apartment properties with management company, firm phone, Section 8 contract expiry and REAC score.
- [Company Name to Website Finder & Enrichment | Business Leads](https://apify.com/infocomp/wikidata-company-finder): turn company names into official websites, HQ, employees, industry, ticker, LEI and SEC CIK from Wikidata.
- [FDA 510(k) New Clearance Leads | Business Leads](https://apify.com/infocomp/fda-510k-clearance-leads): companies that just got a medical device cleared by FDA: new 510(k) decisions from openFDA.

### Source, terms and disclaimer

- **Source:** Colorado Department of State (CDOS), dataset "Business Entities in Colorado" (ID `4ykn-tg5h`), https://data.colorado.gov/Business/Business-Entities-in-Colorado/4ykn-tg5h. License on the dataset page: **Public Domain**. County data: U.S. Census Bureau, 2020 ZCTA to County Relationship File.
- **Not affiliated with or endorsed by** the Colorado Department of State or the State of Colorado.
- Disclaimer required by the portal's terms (https://data.colorado.gov/terms):

> 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.

### FAQ

**Is this the official Colorado business registry?** No. It's an independent tool built on the State's public-domain open dataset. For official records, use the `sosRecordUrl` link.

**Does it include owners, registered agents, phone numbers, emails or street addresses?** No, by design. You get firm-level fields only.

**Other states?** Colorado only for now. More states will be added only where the state's data terms clearly allow it.

# Actor input Schema

## `daysBack` (type: `integer`):

Return entities formed or registered in the last N days, up to and including 'Formed to' (default today, Colorado time). 7 = the last week. Ignored when 'Formed from' is set.

## `dateFrom` (type: `string`):

Optional. First formation/registration date to include, e.g. 2026-10-01. Leave empty to use 'Days back'. Maximum range: 366 days per run.

## `dateTo` (type: `string`):

Optional. Last formation/registration date to include. Empty = today.

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

Optional. Empty = all types. Colorado and foreign (out-of-state) entities are both included unless you set 'Formed in'.

## `formedIn` (type: `string`):

Filter by the entity's jurisdiction of formation.

## `onlyGoodStanding` (type: `boolean`):

Skip new entities that are already dissolved, withdrawn, merged or converted.

## `cities` (type: `array`):

Optional. Principal-address city, e.g. Denver, Colorado Springs, Boulder. Case-insensitive.

## `zipCodes` (type: `array`):

Optional. 5-digit principal-address ZIP codes, e.g. 80202.

## `counties` (type: `array`):

Optional. Colorado counties, e.g. Denver, El Paso, Boulder. Matched by ZIP code using the U.S. Census ZIP-to-county file, so ZIPs that straddle a county line are included. Cities, ZIPs and counties are combined with OR.

## `coloradoAddressOnly` (type: `boolean`):

Skip entities whose principal address is outside Colorado (about 10% of new filings).

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

Stop after this many leads (newest first). Colorado gets roughly 3,000 to 4,000 new filings a week.

## Actor input object example

```json
{
  "daysBack": 7,
  "entityTypes": [],
  "formedIn": "any",
  "onlyGoodStanding": true,
  "cities": [],
  "zipCodes": [],
  "counties": [],
  "coloradoAddressOnly": false,
  "maxResults": 100
}
```

# Actor output Schema

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

No description

## `summary` (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 = {
    "daysBack": 7,
    "entityTypes": [],
    "cities": [],
    "zipCodes": [],
    "counties": [],
    "maxResults": 100
};

// Run the Actor and wait for it to finish
const run = await client.actor("infocomp/new-business-filings-colorado").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 = {
    "daysBack": 7,
    "entityTypes": [],
    "cities": [],
    "zipCodes": [],
    "counties": [],
    "maxResults": 100,
}

# Run the Actor and wait for it to finish
run = client.actor("infocomp/new-business-filings-colorado").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 '{
  "daysBack": 7,
  "entityTypes": [],
  "cities": [],
  "zipCodes": [],
  "counties": [],
  "maxResults": 100
}' |
apify call infocomp/new-business-filings-colorado --silent --output-dataset

```

## MCP server setup

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

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/ny64OBEaeUl1PlOKr/builds/se57JJbFJpw6nEiI6/openapi.json