# US State Business Entities - Colorado & Connecticut Registry (`jpopendata/us-state-business-entities`) Actor

Business entities registered in Colorado and Connecticut from the official state open-data portals (public domain): name, ID, type, status, formation date, city, state, ZIP. Track new LLCs and corporations by date, name, type, status, city or ZIP. No agents, emails or street addresses. Unofficial.

- **URL**: https://apify.com/jpopendata/us-state-business-entities.md
- **Developed by:** [JP Open Data](https://apify.com/jpopendata) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.50 / 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

## US State Business Entities — Colorado & Connecticut Registry

Get the business entities registered in **Colorado** and **Connecticut** from the two states' official open-data portals: the Colorado Department of State's "Business Entities in Colorado" (data.colorado.gov) and the Connecticut Secretary of the State's "Connecticut Business Registry - Business Master" (data.ct.gov). Both states publish these datasets as **Public Domain**. No account, no API key.

- **Watch new registrations** — LLCs, corporations, nonprofits, limited partnerships and LLPs formed or registered in a date range (both states update daily). Schedule the Actor daily or weekly with `registeredFrom: "7 days ago"`.
- **Search** by part of the name, entity type, status, city or ZIP code.
- **One row per entity**: name, state ID, entity type, status (plus a common active / delinquent / inactive group), formation or registration date, dissolution date, city, state and 5-digit ZIP code, NAICS industry (Connecticut), and a link to the record on the state portal.
- **Registered business entities only, no personal contact data.** Registered agents, officers and members, e-mail addresses, street and mailing addresses, and Connecticut's owner survey answers (woman-, veteran-, minority-, LGBTQI- and disability-owned) are never requested from the portals, so they are never in the output. Sole proprietorships and trade names (DBAs) are not in these registers. Entity types whose registered names can be a person's own name are excluded: general partnerships (both states), Colorado corporations sole and "other foreign" entities (FO), and Connecticut records of the "Unknown" type — together about 0.3% of Colorado and 0.1% of Connecticut records.

### Quick start — verified input

```json
{
  "states": ["CO", "CT"],
  "maxItems": 100
}
```

Returns the newest 100 registrations across both states, newest first (4 requests, a few seconds). Running the Actor with an **empty input `{}` does exactly the same**.

Watch new Denver LLCs (verified):

```json
{
  "states": ["CO"],
  "entityTypes": ["llc"],
  "cities": ["Denver"],
  "registeredFrom": "7 days ago",
  "maxItems": 1000
}
```

Find companies by name in both states:

```json
{
  "nameKeywords": ["O'Reilly"],
  "statuses": ["active"]
}
```

### Input

| Field | What to enter | Example |
|---|---|---|
| `states` | `CO`, `CT` or both (default). | `["CT"]` |
| `nameKeywords` | Text that must appear in the registered name, any case. Each entry is a phrase; several entries = any of them. | `["dental", "acme holdings"]` |
| `entityTypes` | `llc`, `corporation` (for-profit, incl. benefit corporations), `benefit corporation`, `nonprofit`, `limited partnership`, `llp`, `lllp`, `partnership` (any of these partnerships), `cooperative`, `statutory trust`, `financial institution`, `insurance`, `water company` — or a state's own code such as `DLLC`, `FPC`, `DNC` (Colorado) or `LLC`, `Stock`, `Non-Stock` (Connecticut). General partnerships, `FO`, `CS` and `Unknown` are never returned. | `["llc", "corporation"]` |
| `statuses` | `active`, `delinquent`, `inactive`, or a state's own status such as `Good Standing`, `Voluntarily Dissolved` (Colorado) or `Forfeited` (Connecticut). Empty = every status. | `["active"]` |
| `registeredFrom` / `registeredTo` | Formation or registration date range: `YYYY-MM-DD`, a month `2026-10`, `today`, `yesterday`, `7 days ago`. | `"2026-10-01"` |
| `cities` | City of the principal (Colorado) or business (Connecticut) address. | `["Denver", "Hartford"]` |
| `zipCodes` | 5-digit ZIP codes or 3–4 digit prefixes. | `["80202", "061"]` |
| `maxItems` | Maximum rows (1–100,000), newest first across the selected states. | `500` |
| `maxApiRequests` | Hard cap on requests to the portals in one run (default 200). One request returns up to 1,000 rows. | `50` |

Status groups: `active` = in good standing (Colorado "Good Standing" / "Exists"; Connecticut "Active" without a past-due report); `delinquent` = still exists but a report is past due or similar (Colorado "Delinquent", "Noncompliant"; Connecticut "Active" with sub-status such as "Annual report past due"); `inactive` = dissolved, withdrawn, revoked, merged, forfeited and similar. Use `active` and `delinquent` together for every entity that still exists.

### Output

One row per entity (two real rows, shortened):

```json
{
  "state": "CO",
  "stateName": "Colorado",
  "registrationNumber": "20268262344",
  "name": "EssJayy Home Care Services LLC",
  "nameAsListed": "EssJayy Home Care Services LLC",
  "entityType": "DLLC",
  "entityTypeLabel": "Limited Liability Company",
  "entityKind": "llc",
  "domestic": true,
  "jurisdictionOfFormation": "Colorado",
  "status": "Good Standing",
  "statusDetail": null,
  "statusCategory": "active",
  "registrationDate": "2026-10-12",
  "dissolutionDate": null,
  "naicsCode": null,
  "naicsDescription": null,
  "city": "Denver",
  "stateOrProvince": "CO",
  "postalCode": "80203",
  "country": "US",
  "sourceRecordUrl": "https://data.colorado.gov/resource/4ykn-tg5h.json?entityid=20268262344",
  "datasetUpdatedAt": "2026-10-13T11:24:11.000Z",
  "source": "Colorado Department of State (CDOS) - Business Entities in Colorado, Colorado Information Marketplace (data.colorado.gov, dataset 4ykn-tg5h)",
  "sourceUrl": "https://data.colorado.gov/Business/Business-Entities-in-Colorado/4ykn-tg5h",
  "license": "Public Domain (license stated on the dataset by the State of Colorado). Required notice from the data.colorado.gov Terms of Service: ...",
  "retrievedAt": "2026-10-14T11:52:14.296Z"
}
```

```json
{
  "state": "CT",
  "registrationNumber": "3533439",
  "name": "Around Da Clock LLC",
  "entityType": "LLC",
  "entityKind": "llc",
  "domestic": true,
  "status": "Active",
  "statusCategory": "active",
  "registrationDate": "2026-10-13",
  "naicsCode": "445132",
  "naicsDescription": "Vending Machine Operators",
  "city": "Hartford",
  "stateOrProvince": "CT",
  "postalCode": "06106",
  "country": "US",
  "sourceRecordUrl": "https://data.ct.gov/resource/n7gp-d28j.json?accountnumber=3533439"
}
```

Field notes:

- `name` — Colorado appends a status note to the names of many entities that are no longer in good standing (for example `"Acme LLC, Dissolved September 30, 2025"`). The note is removed from `name`; `nameAsListed` keeps the state's text, and for inactive entities the date fills `dissolutionDate`.
- `registrationDate` is the formation date of a domestic entity or the date a foreign (out-of-state) entity registered in the state. Colorado lists some future dates (filings with a delayed effective date); they come first when sorting newest first.
- `domestic` is `false` for a foreign entity registered in the state; `jurisdictionOfFormation` says where it was formed.
- The address is reduced to **city, state or province, 5-digit ZIP code and country**. ZIP+4 and non-US postal codes are not output. Both registers are typed in by filers: a city that looks like a street, a P.O. box or a contact line is left empty, and the same city can appear in several spellings (for example "COS" for Colorado Springs).
- `naicsCode` / `naicsDescription` are the industry codes Connecticut businesses give when they file (not every business gives one). Colorado has no industry field.
- `sourceRecordUrl` opens the full public record on the state portal (JSON). It is a link only — the Actor itself never reads the columns it does not output.
- The `RUN_SUMMARY` record in the key-value store shows, per state, the license read at the start of the run, when the state last updated the dataset, the requests and pages, rows withheld or not matching, and why a run stopped early (if it did).

### Empty results?

- The name text is not part of any registered name. It is matched as typed (as a phrase, any case): `"acme holdings"` does not match `"Acme Real Estate Holdings"` — use `["acme"]` or two entries.
- The city is spelled differently in the register, or the ZIP code is outside the selected states.
- `registeredFrom` is in the future or the range is very short; Colorado's daily update can lag a day behind Connecticut's.
- The filters exclude everything together, or a filter exists in one state only (e.g. `lllp` is Colorado only, `statutory trust` Connecticut only — the other state is then skipped with a warning).

### How it works

The Actor calls only the public Socrata API of the two portals: one metadata request per state (the run checks that the license still reads "Public Domain" and skips a state whose license has changed) and pages of up to 1,000 rows of the business dataset, ordered by date. Requests are sent one at a time, at least 1.2 seconds apart (the portals' robots.txt asks for 1 second), anonymously and with a hard request budget. Datacenter access works directly; no proxy is needed. If one state's portal fails, the other state's rows are still delivered and the run is marked incomplete.

### Data source, terms and disclaimer

- **Unofficial tool. Not affiliated with or endorsed by the State of Colorado, the Colorado Department of State, the State of Connecticut or the Connecticut Secretary of the State.**

- Colorado data: Colorado Department of State (CDOS), "Business Entities in Colorado", Colorado Information Marketplace, https://data.colorado.gov/Business/Business-Entities-in-Colorado/4ykn-tg5h — license: Public Domain. The data.colorado.gov Terms of Service require applications that use the data to show this notice; every Colorado row carries it in `license`, and **if you publish Colorado data on your own site, show it there too**:

  > 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: Connecticut Secretary of the State, "Connecticut Business Registry - Business Master", CT Open Data Portal, https://data.ct.gov/Business/Connecticut-Business-Registry-Business-Master/n7gp-d28j — license: Public Domain. Provided by the State of Connecticut as a public service on an "as is" basis, without warranty of any kind.

- Changed by this tool: selected fields only, address reduced to city/state/ZIP/country, Colorado status notes split from names, records that are not registered entities (Connecticut name reservations and rejected filings) excluded, and the entity types whose names can be a person's own name excluded (general partnerships in both states, Colorado corporations sole and "other foreign" entities, Connecticut "Unknown"-type records).

- Only public data about registered business entities is returned. Some registered names contain a person's name (for example an LLC named after its owner); they are output as registered names.

- The state registers are the authoritative source. Check the state's own records before relying on a row for legal decisions.

- You are responsible for using the data lawfully, including privacy laws (such as the GDPR and US state privacy laws) and the rules on unsolicited marketing that apply to you.

# Actor input Schema

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

CO (Colorado), CT (Connecticut) or both (default). Full names work too. Other states are not covered.

## `nameKeywords` (type: `array`):

Optional. Text that must appear in the registered name, any case, e.g. "dental", "acme holdings", "O'Reilly". Several entries = any of them. Each entry is matched as typed (a phrase, not separate words).

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

Optional. llc, corporation (for-profit, incl. benefit corporations), benefit corporation, nonprofit, limited partnership, llp, lllp (Colorado), partnership (any of these partnerships), cooperative, statutory trust (Connecticut), financial institution, insurance, water company (Colorado); or a state's own type code such as DLLC, FLLC, DPC, FPC, DNC (Colorado) or LLC, Stock, Non-Stock, B Corp (Connecticut). Several values = any of them. General partnerships, Colorado "other foreign" (FO) entities, corporations sole and Connecticut "Unknown"-type records are never returned (their names can be a person's own name).

## `statuses` (type: `array`):

Optional. active (in good standing), delinquent (exists but a report is past due or similar) or inactive (dissolved, withdrawn, revoked, merged ...); or a state's own status such as "Good Standing", "Voluntarily Dissolved" (Colorado) or "Active", "Forfeited" (Connecticut). Several values = any of them. Empty = every status.

## `registeredFrom` (type: `string`):

Optional. Earliest formation/registration date, YYYY-MM-DD (e.g. "2026-10-01"). A month ("2026-10"), "today", "yesterday" and "7 days ago" also work. Use it with a daily or weekly schedule to watch new registrations.

## `registeredTo` (type: `string`):

Optional. Latest formation/registration date (inclusive), same forms as above. Empty = no upper limit (Colorado lists some future dates for filings with a delayed effective date).

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

Optional. City of the principal (Colorado) or business (Connecticut) address, any case, e.g. "Denver", "Colorado Springs", "Hartford". The register is typed in by filers, so a city can also appear abbreviated (e.g. "COS"). Several values = any of them.

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

Optional. 5-digit ZIP codes or prefixes of 3-4 digits, e.g. "80202", "802" (every ZIP code starting with 802), "06103". Several values = any of them.

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

Maximum rows (1..100,000), newest registration first across the selected states. You are charged per row.

## `maxApiRequests` (type: `integer`):

Safety cap on requests to the state portals for the whole run (1..2,000). Requests are sent one at a time at least 1.2 seconds apart; one request returns up to 1,000 rows, plus one licence check per state. If the cap is reached the rows read so far are kept and the run says it is incomplete.

## Actor input object example

```json
{
  "states": [
    "CO",
    "CT"
  ],
  "nameKeywords": [],
  "entityTypes": [],
  "statuses": [],
  "registeredFrom": "",
  "registeredTo": "",
  "cities": [],
  "zipCodes": [],
  "maxItems": 100,
  "maxApiRequests": 200
}
```

# Actor output Schema

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

One row per business entity with the state's attribution (source, sourceUrl, license, retrievedAt) on every item.

# 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",
        "CT"
    ],
    "nameKeywords": [],
    "entityTypes": [],
    "statuses": [],
    "registeredFrom": "",
    "registeredTo": "",
    "cities": [],
    "zipCodes": [],
    "maxItems": 100,
    "maxApiRequests": 200
};

// Run the Actor and wait for it to finish
const run = await client.actor("jpopendata/us-state-business-entities").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",
        "CT",
    ],
    "nameKeywords": [],
    "entityTypes": [],
    "statuses": [],
    "registeredFrom": "",
    "registeredTo": "",
    "cities": [],
    "zipCodes": [],
    "maxItems": 100,
    "maxApiRequests": 200,
}

# Run the Actor and wait for it to finish
run = client.actor("jpopendata/us-state-business-entities").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",
    "CT"
  ],
  "nameKeywords": [],
  "entityTypes": [],
  "statuses": [],
  "registeredFrom": "",
  "registeredTo": "",
  "cities": [],
  "zipCodes": [],
  "maxItems": 100,
  "maxApiRequests": 200
}' |
apify call jpopendata/us-state-business-entities --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,jpopendata/us-state-business-entities"
        }
    }
}
```

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/CSTbY7JwcgkZ8cddo/builds/oIiUNFtjdheA0i4Jx/openapi.json