# US State Business Registry Search - Entity Status & Type (`kdhan/us-business-registry-search`) Actor

Search US state business registries by company name: registration status, entity type and formation date from official state open data (Colorado, Connecticut, New York, Oregon). Live queries, no API key. No agent, officer or owner names or addresses.

- **URL**: https://apify.com/kdhan/us-business-registry-search.md
- **Developed by:** [Doohan Kim](https://apify.com/kdhan) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.00 / 1,000 entity records

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 Registry Search

Search US state business registries by company name and get registration status, entity type and
formation date from the official state open-data portals (Socrata). Live queries per run, no API
key, nothing stored. Supported states: **Colorado, Connecticut** (default), **New York, Oregon** (list them in `states`).

The Actor does **not** output registered agents, officers, owners, e-mail addresses or street
addresses. Only the entity's principal city and state, when the registry has them.

### Input

```json
{
  "searchTerms": ["acme", "o'brien"],
  "states": ["CO", "CT"],
  "matchMode": "prefix",
  "status": "active",
  "maxResultsPerTerm": 25
}
```

All fields are optional; an empty input searches `acme` in Colorado and Connecticut.
`matchMode`: `prefix` (name starts with the term), `contains`, `exact`. `status`: `active` or `all`.
`maxResultsPerTerm` (1-500) applies to each term in each state.

### Output (one row per record)

`entityName`, `state`, `entityId`, `status`, `statusCategory` (`active`, `not-in-good-standing`,
`inactive`, `other`), `entityType`, `formationDate`, `jurisdictionOfFormation`, `principalCity`,
`principalState`, `sourceUrl`, `dataAsOf`, `matchedTerm`, `found`, `disclaimer`.
A term with no match gives one row with `found: false` (free). If a state portal does not answer,
the row has `found: null` and an `error` - that is **not** a "no match".

### Pricing

Pay-per-event, event name `entity-record` (one matching record returned). Rows with `found` false or
null are not charged.

### Data sources

| State | Portal dataset | Notes |
|---|---|---|
| CO | data.colorado.gov `4ykn-tg5h` | Public Domain per dataset metadata. Names may carry a suffix like ", Dissolved March 24, 2026" as published. |
| CT | data.ct.gov `n7gp-d28j` | Public Domain per dataset metadata. |
| NY | data.ny.gov `n9v6-gdp6` | Active corporations only; monthly snapshot. OPEN NY Terms of Use allow reuse. |
| OR | data.oregon.gov `tckn-sxa6` | Active businesses; portal reuse terms not confirmed, so Oregon is returned only when requested. |

`dataAsOf` is the dataset's last update time reported by the portal.
Optional environment variable `SOCRATA_APP_TOKEN` raises the rate limit; the Actor works without it
and retries with exponential back-off (honouring `Retry-After`) when throttled.

### Limits

- A registry entry is not proof of good standing; verify with the Secretary of State before relying on it.
- Snapshots update daily to monthly depending on the state; see `dataAsOf`.
- Public state business registry data, provided for informational purposes only; not legal advice.

# Actor input Schema

## `searchTerms` (type: `array`):

Company names or name parts (at least 2 characters). Case-insensitive.

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

Two-letter codes: CO, CT, NY, OR. Default CO and CT. Oregon is returned only when listed (portal reuse terms not confirmed).

## `matchMode` (type: `string`):

prefix: name starts with the term. contains: term anywhere in the name. exact: whole name equals the term.

## `status` (type: `string`):

active: only currently active registrations. all: include dissolved, revoked and other statuses.

## `maxResultsPerTerm` (type: `integer`):

Upper limit of records returned for each search term in each state. You are charged per record returned.

## Actor input object example

```json
{
  "searchTerms": [
    "acme"
  ],
  "states": [
    "CO",
    "CT"
  ],
  "matchMode": "prefix",
  "status": "active",
  "maxResultsPerTerm": 25
}
```

# Actor output Schema

## `entities` (type: `string`):

Entity name, state, ID, status, type, formation date, source dataset, data freshness and disclaimer.

# 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 = {
    "searchTerms": [
        "acme"
    ],
    "states": [
        "CO",
        "CT"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("kdhan/us-business-registry-search").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 = {
    "searchTerms": ["acme"],
    "states": [
        "CO",
        "CT",
    ],
}

# Run the Actor and wait for it to finish
run = client.actor("kdhan/us-business-registry-search").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 '{
  "searchTerms": [
    "acme"
  ],
  "states": [
    "CO",
    "CT"
  ]
}' |
apify call kdhan/us-business-registry-search --silent --output-dataset

```

## MCP server setup

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

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/y4t9mTNhVDSiPLnRQ/builds/riVwJ57ooNo6ovzA8/openapi.json