# Colorado new business registrations monitor (`keepable_injera/us-new-business-registrations-monitor`) Actor

Monitor Colorado daily new LLC and corporation filings from the Colorado Department of State.

- **URL**: https://apify.com/keepable_injera/us-new-business-registrations-monitor.md
- **Developed by:** [Chee Chiaw Lim](https://apify.com/keepable_injera) (community)
- **Categories:** Business, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$2.00 / 1,000 results

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

## Colorado new business registrations monitor

This Apify Actor returns recently formed business entities from the Colorado Department of State. It covers daily new LLC and corporation filings, plus other entity types when selected.

### Coverage and source

Coverage is Colorado only for now. Colorado provides a daily updated public dataset through a SODA API, so the Actor can query formation dates without collecting personal contact details.

The source is [Colorado Department of State business entities](https://data.colorado.gov/d/4ykn-tg5h), published through Colorado Information Marketplace. The API endpoint is https://data.colorado.gov/resource/4ykn-tg5h.json. Formation date determines inclusion, rather than when a record first appeared in the feed.

### Input

| Field | Default | Meaning |
| --- | --- | --- |
| `sinceDays` | 7 | Integer from 1 to 365. Include entities formed since midnight UTC N days ago. |
| `entityTypes` | \[] | Colorado codes such as DLLC, DPC, DNC, or FLLC. Empty selects all types. |
| `cities` | \[] | Principal cities, matched without case sensitivity. Empty selects all cities. |
| `onlyNew` | false | Skip entity IDs previously emitted to the named state store. |
| `maxItems` | 100 | Integer from 1 to 10000. Maximum source records examined before duplicate and onlyNew filtering. |
| `stateStoreName` | us-new-business-registrations-monitor-state | Named key-value store for emitted entity IDs. |

Results sort by formation date descending, then entity ID descending. Requests use pages of 1000 rows with offset paging. Collection stops on a short page or at maxItems. A run can emit fewer than maxItems when records are duplicates or already seen.

### Output

Each record contains entity identifiers, business name and type, status, formation date, jurisdiction, principal city/state/ZIP/country, permitted agent details, and source attribution. Unknown type labels and missing fields are null. Principal ZIP codes contain five digits.

Example record follows.

```json
{
  "entityId": "20261234567",
  "entityName": "Example Business LLC",
  "entityType": "DLLC",
  "entityTypeLabel": "Domestic LLC",
  "status": "Good Standing",
  "formedDate": "2026-10-21",
  "jurisdictionOfFormation": "CO",
  "principalCity": "Denver",
  "principalState": "CO",
  "principalZip": "80203",
  "principalCountry": "US",
  "registeredAgentType": "organization",
  "registeredAgentName": "Example Registered Agent LLC",
  "registeredAgentCity": "Denver",
  "registeredAgentState": "CO",
  "state": "CO",
  "sourceUrl": "https://data.colorado.gov/d/4ykn-tg5h",
  "recordUrl": null,
  "source": "Colorado Department of State via Colorado Information Marketplace",
  "licence": "Public Domain (data.colorado.gov dataset 4ykn-tg5h); State of Colorado Terms of Service https://data.colorado.gov/terms",
  "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.",
  "generatedId": "CO:20261234567",
  "scrapedAt": "2026-10-23T00:00:00.000Z",
  "changeType": "new"
}
```

The dataset has a table view of key fields. `RUN_SUMMARY` in the default key-value store records timestamps, fetched, eligible, and pushed counts, charge-limit status, and any error.

### State and pricing

The state store contains a set of entity IDs under `SEEN_ENTITY_IDS`. An ID absent from the set gets `changeType: "new"`; an ID present gets `"seen"`. Only successful pushes enter the set. With onlyNew false, previously emitted entities appear again. This does not detect amendments to an existing entity. Use a separate state store for independent monitors.

Pricing is $0.002 per result, with no start fee. Each emitted record uses the `result` billing event. The Actor stops at the available charge limit. Seen records skipped by onlyNew do not incur a result charge. Platform compute and storage charges may apply separately.

### Privacy

The output drops all street address fields, all mailing address fields, and agent first, middle, and last names. Individual agents have a null registeredAgentName. Organization agents retain only their organization name and city/state. The Actor does not store raw source rows. Entity names remain the registered business names, which may themselves contain a person's name. The state store contains entity IDs only.

### Licence and disclaimer

Public Domain (data.colorado.gov dataset 4ykn-tg5h); State of Colorado Terms of Service https://data.colorado.gov/terms

The Actor filters records, maps fields, truncates ZIP codes, and removes personal contact fields. Retain source attribution, licence, and this required disclaimer with redistributed output.

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.

### Limits

The feed updates daily and may lag filings or contain omissions. Formation dates, status, and entity types follow the source. Foreign entities can appear when selected. This output does not establish legal standing or replace a certified record. Offset paging can shift if the source changes during a run. The Actor waits at least one second between request starts per host and retries HTTP 429 and 5xx responses up to three times. Network failures stop the run and appear in RUN_SUMMARY.

### Local verification

Run `npm test` for offline tests. For a fixture-backed local run with network access disabled, use a fresh storage directory and run:

```sh
CRAWLEE_STORAGE_DIR=/tmp/colorado-check APIFY_LOCAL_STORAGE_DIR=/tmp/colorado-check NODE_OPTIONS="--import ./scripts/offline-fixture.js" npm start
node scripts/verify-output.js /tmp/colorado-check
```

The preload serves the supplied anonymised fixture, not current source data, and does not simulate source filters. Use normal `npm start` only when a live network run is authorized.

# Actor input Schema

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

Registrations formed since midnight UTC N days ago.

## `maxItems` (type: `integer`):

Maximum source records examined per run, before duplicate and onlyNew filtering.

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

Colorado codes such as DLLC, DPC, DNC, FLLC. Empty selects all.

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

Case-insensitive principal city names. Empty selects all.

## `onlyNew` (type: `boolean`):

Skip entity IDs already emitted to this state store.

## `stateStoreName` (type: `string`):

Persistent seen entity IDs. Use a separate store per independent monitor.

## Actor input object example

```json
{
  "sinceDays": 7,
  "maxItems": 100,
  "entityTypes": [],
  "cities": [],
  "onlyNew": false,
  "stateStoreName": "us-new-business-registrations-monitor-state"
}
```

# Actor output Schema

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

No description

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

// Run the Actor and wait for it to finish
const run = await client.actor("keepable_injera/us-new-business-registrations-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("keepable_injera/us-new-business-registrations-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 keepable_injera/us-new-business-registrations-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,keepable_injera/us-new-business-registrations-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/gfTy6umUM6eBfeiyp/builds/SO55QYQkGzZl5Zx2i/openapi.json