# Connecticut Business Status Check (`nexgenwatch/connecticut-business-status-check`) Actor

Check Connecticut business identities against the official state registry (data.ct.gov) — one official answer per identifier: registry status, registration date and diversity-ownership certifications, verbatim. Not-found, ambiguous, and unavailable outcomes are returned but never billed.

- **URL**: https://apify.com/nexgenwatch/connecticut-business-status-check.md
- **Developed by:** [NexGen Watch](https://apify.com/nexgenwatch) (community)
- **Categories:** Business
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $33.50 / 1,000 business status checks

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Connecticut Business Status Check

A per-identity **check**: submit identifiers, get one official answer each. Billed **per completed official resolution** — a not-found, ambiguous, or unavailable outcome is returned but never charged.

### How it behaves

Each identity is resolved against the official Connecticut business registry (data.ct.gov `n7gp-d28j`). A business **account number** resolves to at most one entity; an exact **name** matching more than one returns an ambiguity (resolve by account number) and is not billed. A resolved entity returns its registry **status verbatim** plus registration date and the published diversity-ownership certifications. The keyless register does not expose a separate *standing* or *annual-report recency* field, so those are honest `null` with a reason. Unknown identities are not-found and not billed. Per-entity status twin of the connecticut-business-registry-master roster.

### What you get

One record per submitted identity. A resolved identity carries the official fields verbatim; fields the source withholds are honest `null` with a reason. Not-found, ambiguous, and service-unavailable outcomes are distinguished in the `outcome` field and are **not** billed. A run that gets no definitive result at all fails loud and charges nothing.

### Billing

| Event | FREE | BRONZE | SILVER | GOLD+ |
|---|---|---|---|---|
| `apify-actor-start` (one-time actor start) | $0.02 | $0.02 | $0.02 | $0.02 |
| `business-status-check` (per completed resolution) | $0.05 | $0.045 | $0.04 | $0.0335 |

Charged once per completed official resolution. Not-found, ambiguous, and service-fault outcomes are emitted but never charged. Start fee $0.02.

### Source

`https://data.ct.gov/resource/n7gp-d28j.json`

# Actor input Schema

## `entities` (type: `array`):

Connecticut businesses to resolve against the official CT business registry (data.ct.gov). Each item is a business account number (business ID, preferred) or an exact business name. A resolved entity returns its registry status verbatim; a name matching more than one entity returns an ambiguity (resolve by account number) and is not billed; an unknown identity is not-found and not billed. This is the per-entity status twin of the connecticut-business-registry-master roster.

## Actor input object example

```json
{
  "entities": [
    "2873007",
    "C3 PARTNERS LLC"
  ]
}
```

# Actor output Schema

## `results` (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 = {
    "entities": [
        "2873007",
        "C3 PARTNERS LLC"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("nexgenwatch/connecticut-business-status-check").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 = { "entities": [
        "2873007",
        "C3 PARTNERS LLC",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("nexgenwatch/connecticut-business-status-check").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 '{
  "entities": [
    "2873007",
    "C3 PARTNERS LLC"
  ]
}' |
apify call nexgenwatch/connecticut-business-status-check --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,nexgenwatch/connecticut-business-status-check"
        }
    }
}
```

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/uFWXocspKOJx6o9JF/builds/CP0Mqd48sejeJkG1A/openapi.json