# New Business Leads: Fresh LLC Filings in NY, PA & CT (`jserle/us-new-business-leads-feed`) Actor

Fresh business-formation leads across NY, PA and CT in one feed. Published CT business emails and NAICS, PA officers, NY filer intelligence and verified registered agents. Filter by date, county, industry and name. One global result cap.

- **URL**: https://apify.com/jserle/us-new-business-leads-feed.md
- **Developed by:** [JS Tech Solutions](https://apify.com/jserle) (community)
- **Categories:** Lead generation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$3.00 / 1,000 business registration 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?

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

## New Business Leads: Fresh LLC Filings in NY, PA & CT

Discover newly formed businesses **without already knowing their names**. This actor combines New York, Pennsylvania and Connecticut public business registries into one globally capped prospecting feed, with state-verified contacts and explicit source freshness.

Unlike a company-name or KYB lookup, the default run discovers new companies automatically. It returns a balanced mix of NY formation filings, PA businesses with grouped organizers or officers, and CT registrations with published business email, NAICS industry codes, principals and statutory agents.

**Planned launch price: $0.003 per delivered business, or $3 per 1,000 unique businesses.** Pricing must still be configured and verified in Apify before publication.

### Who this is for

- B2B sales teams identifying new LLCs and corporations before they have accumulated a marketing footprint.
- Business banking, payroll, insurance, bookkeeping and merchant-services teams working formation-triggered outreach.
- Registered-agent and annual-report service providers reviewing documented company contacts and CT compliance dates.
- AI agents or CRM pipelines that need one consistent, typed result schema across state registries.

### Four buyer-ready ways to use this feed

#### Accountants and bookkeeping firms

Find recently formed LLCs across your service territory before their first tax, payroll or bookkeeping decisions. Include Connecticut's published annual-report due date when the source supplies it; Pennsylvania officers and Connecticut principals appear only when the registry actually identifies them.

```json
{ "states": ["NY", "PA", "CT"], "includeDecisionMakers": true, "maxResults": 250 }
```

#### Commercial lenders and business-banking teams

Build a regional new-business prospect queue with formation dates, registry identifiers, location evidence and available officers or verified agents. Missing emails and principals remain empty instead of being inferred.

```json
{ "states": ["NY", "PA", "CT"], "formedFrom": "2026-08-01", "maxResults": 500 }
```

#### Insurance brokers and payroll providers

Narrow Connecticut registrations to construction businesses through the official NAICS `23` prefix. Request a published business email only when that channel matters; this excludes New York and Pennsylvania because their source datasets do not publish business email here.

```json
{ "states": ["CT"], "industryCodePrefix": "23", "requireBusinessEmail": true, "maxResults": 100 }
```

#### Marketing agencies and merchant-services teams

Find newly registered businesses before they develop a broad digital footprint. Use a county or industry filter when appropriate, and import the source-published business contact details and transparent lead signals into your CRM.

```json
{ "states": ["CT"], "county": "Fairfield", "requireBusinessEmail": true, "maxResults": 200 }
```

### What each state actually publishes

| Evidence | NY daily filings | PA monthly registry | CT daily registry |
| --- | --- | --- | --- |
| Company, registry ID, formation date and entity type | Yes | Yes | Yes |
| County | Registry-reported | Registry-reported | Derived from the official state town crosswalk |
| Business email and NAICS industry | Not published | Not published | Published when the business supplied them |
| Officers or principals | Not published in the filing feed | Organizer, incorporator or officer rows, grouped by business | Joined from the official Principals dataset |
| Actual registered or statutory agent | Joined from the separate Active Corporations roster, when available | Not published in this dataset | Joined from the official Agents dataset, when available |
| Filing contact or service-of-process recipient | Published as separate, explicitly labeled evidence | Not published | Not published |
| Annual-report due date and ownership-survey flags | Not published | Not published | Published when available |

An unavailable field is `null` or an empty list. Names, emails, agents, status and industry codes are never guessed or inferred. A New York service-of-process recipient is **not** presented as a registered agent.

### Example result

All contact details below are fictional.

```json
{
  "leadId": "CT:001EXAMPLE00001",
  "state": "CT",
  "registryId": "001EXAMPLE00001",
  "businessName": "Example Harbor Analytics LLC",
  "entityType": "LLC",
  "formationDate": "2026-08-22",
  "formationAgeDays": 3,
  "status": "Active",
  "county": "Fairfield",
  "city": "Stamford",
  "cityEvidence": "business_address",
  "businessAddress": {
    "street": "100 Example Street",
    "unit": null,
    "city": "Stamford",
    "state": "CT",
    "postalCode": "06901",
    "country": "United States"
  },
  "businessEmail": "sales@example.com",
  "industryCode": "541511",
  "industryDescription": "Custom Computer Programming Services",
  "decisionMakers": [
    {
      "name": "Jordan Example",
      "role": "Member",
      "businessAddress": null,
      "sourceDatasetId": "ka36-64k6"
    }
  ],
  "registeredAgents": [
    {
      "name": "Example Registered Agent LLC",
      "type": "Organization",
      "businessAddress": null,
      "email": "agent@example.com",
      "phone": "2025550100",
      "sourceDatasetId": "qh2m-n44y"
    }
  ],
  "annualReportDueDate": "2026-09-20",
  "annualReportDueInDays": 26,
  "leadSignals": [
    "formed_within_7_days",
    "registry_published_business_email",
    "named_registry_decision_maker",
    "registry_published_industry_code",
    "verified_registered_agent",
    "annual_report_due_within_45_days"
  ],
  "opportunityScore": 100,
  "opportunityScoreExplanation": "Transparent source-evidence prioritization, not a predicted conversion rate.",
  "source": "https://data.ct.gov/resource/n7gp-d28j.json",
  "sourceDatasetId": "n7gp-d28j",
  "sourcePage": "https://data.ct.gov/d/n7gp-d28j",
  "sourceUpdatedAt": "2026-08-23T08:30:19.000Z",
  "sourceRefreshCadence": "Daily",
  "attribution": "Connecticut Secretary of the State",
  "fetchedAt": "2026-08-25T12:00:00.000Z"
}
```

### Input

| Input | Default | Meaning |
| --- | --- | --- |
| `states` | `["NY", "PA", "CT"]` | State registries to include. |
| `formedFrom` | State-aware | NY and CT start seven days ago; PA uses its latest safely available monthly window. An explicit date overrides both. |
| `formedTo` | None | Inclusive end date. Setting only an end date removes the default lower bound. |
| `county` | None | Exact county match. CT counties are resolved through the official town crosswalk. |
| `city` | None | Exact city or town. NY matches the service-of-process city and labels its provenance. |
| `businessNameContains` | None | Case-insensitive substring for an optional targeted search. |
| `industryCodePrefix` | None | Two to six NAICS digits. This limits results to CT because NY and PA do not publish NAICS here. |
| `requireBusinessEmail` | `false` | Return only registry-published CT business emails. NY and PA are explicitly omitted. |
| `includeDecisionMakers` | `true` | Include grouped PA officers and joined CT principals. |
| `includeRegisteredAgents` | `true` | Join CT statutory agents and the NY Active Corporations roster for actual registered agents. |
| `maxResults` | `100` | Hard cap **across all selected states combined**, up to 10,000. |
| `includeRaw` | `false` | Attach the original business and requested companion records. |

#### Example: new businesses across all three states

```json
{ "maxResults": 100 }
```

#### Example: Connecticut construction prospects with an email

```json
{ "states": ["NY", "PA", "CT"], "industryCodePrefix": "23", "requireBusinessEmail": true, "maxResults": 250 }
```

The run clearly reports that NY and PA were omitted because their datasets do not publish either requested field.

#### Example: New York and Pennsylvania county-level formation leads

```json
{ "states": ["NY", "PA"], "formedFrom": "2026-07-01", "county": "Monroe", "maxResults": 200 }
```

### Delivery, deduplication and charging

- Planned launch pricing is **$0.003 per delivered business registration record**. One hundred records equal **$0.30**, 1,000 records equal **$3.00**, and 10,000 records equal **$30.00** in actor result charges.
- One dataset item is one unique business, identified by its state and state-issued registry identifier.
- Duplicate NY filing rows and duplicate PA officer rows are removed before anything is delivered.
- All officers for a PA business are grouped inside that one business record. They do not create extra paid results.
- Results are selected fairly across requested states, then sorted by formation date and transparent evidence score.
- `maxResults` is one global hard cap, not a per-state cap.
- The actor refuses to deliver results if a pay-per-event allowance cannot be read. It stops cleanly at the run's remaining charge limit.
- Pricing is not set by this source repository. Confirm the configured pay-per-event price in the actor's Pricing tab after deployment and before publication.

### Government sources, cadence and terms

- **New York:** [Daily Corporation and Other Entity Filing Data](https://data.ny.gov/d/k4vb-judh), reported daily; [Active Corporations](https://data.ny.gov/d/n9v6-gdp6), whose stated cadence is monthly. Attribution: New York State Department of State. The datasets do not declare a license in their portal metadata, so review the portal terms for your use case.
- **Pennsylvania:** [Registered Businesses in PA Current by County](https://data.pa.gov/d/xvd7-5r2c), reported monthly. Attribution: Pennsylvania Department of State. The portal describes its license as "Public Domain U.S. Government"; this is the portal's own label for a state dataset and is not an independent legal determination.
- **Connecticut:** [Business Master](https://data.ct.gov/d/n7gp-d28j), reported daily; [Principals](https://data.ct.gov/d/ka36-64k6); [Agents](https://data.ct.gov/d/qh2m-n44y). Attribution: Connecticut Secretary of the State. Business Master declares "Public Domain"; the companion datasets do not state a license in their metadata.

Requests go directly to the official open-data APIs, without login, proxies, app tokens or website scraping. Calls are sequential and honor each host's one-second crawl delay. Every lead includes the actual portal-reported source update timestamp.

Registry contact information is published by the source, not independently verified. Follow applicable privacy, marketing and contact-consent rules. A published filing is not a guarantee of identity, present good standing, an available inbox, or an intention to buy.

Not affiliated with or endorsed by any state agency.

### Related single-state datasets

- [New York Business Filings Feed](https://apify.com/jserle/ny-business-filings-feed)
- [Pennsylvania Business Registry Officers](https://apify.com/jserle/pa-business-registry-officers)
- [Connecticut Business Registry Leads](https://apify.com/jserle/ct-business-registry-leads)

# Actor input Schema

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

Official registries to query. NY and CT publish daily; PA publishes monthly.

## `formedFrom` (type: `string`):

Inclusive YYYY-MM-DD date. The default is seven days ago for NY and CT. PA automatically uses its latest publishable monthly window unless you explicitly set this field.

## `formedTo` (type: `string`):

Inclusive YYYY-MM-DD date. Setting only an end date removes the default lower bound.

## `county` (type: `string`):

Exact county name, case-insensitive. CT counties are derived using the official town crosswalk; NY and PA counties are source-published.

## `city` (type: `string`):

Case-insensitive city match. NY uses the filing's service-of-process city, not an asserted principal-office city.

## `businessNameContains` (type: `string`):

Optional case-insensitive substring. Leave blank to discover new companies you do not already know.

## `industryCodePrefix` (type: `string`):

Two to six digits, such as 23 for construction or 541511 for custom programming. NY and PA do not publish this field, so this filter limits results to CT.

## `requireBusinessEmail` (type: `boolean`):

Return only businesses whose official registry publishes a business email. NY and PA do not expose business email in these datasets, so this limits results to CT.

## `includeDecisionMakers` (type: `boolean`):

Group PA's officer, organizer and incorporator rows into one lead and join CT's separate Principals dataset. NY's filing dataset does not publish officers.

## `includeRegisteredAgents` (type: `boolean`):

Join CT's Agents dataset and NY's Active Corporations roster. NY's service-of-process recipient remains a distinct field and is never mislabeled as an agent.

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

Hard global cap across all selected states, not a separate allowance per state. Only delivered business records are chargeable.

## `includeRaw` (type: `boolean`):

Attach unmodified source rows to each delivered lead. Companion records are attached only when their corresponding option is enabled.

## Actor input object example

```json
{
  "states": [
    "NY",
    "PA",
    "CT"
  ],
  "requireBusinessEmail": false,
  "includeDecisionMakers": true,
  "includeRegisteredAgents": true,
  "maxResults": 100,
  "includeRaw": false
}
```

# Actor output Schema

## `leads` (type: `string`):

Normalized businesses, source-published contact channels, decision makers, verified agents, industry classifications and buyer-facing formation signals.

## `summary` (type: `string`):

Requested and effective states, date windows, source refresh timestamps, fetched and malformed rows, per-state delivery totals and whether the charge limit stopped the run.

# 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": [
        "NY",
        "PA",
        "CT"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("jserle/us-new-business-leads-feed").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": [
        "NY",
        "PA",
        "CT",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("jserle/us-new-business-leads-feed").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": [
    "NY",
    "PA",
    "CT"
  ]
}' |
apify call jserle/us-new-business-leads-feed --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,jserle/us-new-business-leads-feed"
        }
    }
}

```

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/0GUHzILSSXSyN4uou/builds/lYXHG5DSkKl8InJtJ/openapi.json