# Texas New Business Entities Feed (LLCs & Corporations) (`jwaiworks/texas-new-business-entities`) Actor

Texas new LLC and corporation feed from Comptroller open data: name, type, file number, dates, status, NAICS, city and ZIP. Companies only — no street addresses, no sole proprietors. Use in line with CAN-SPAM. Not affiliated with the State of Texas.

- **URL**: https://apify.com/jwaiworks/texas-new-business-entities.md
- **Developed by:** [JW AI Works](https://apify.com/jwaiworks) (community)
- **Categories:** Lead generation, Business
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$2.00 / 1,000 new entities

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

**Get a daily or weekly list of newly chartered Texas LLCs, corporations and partnerships, straight from the Texas Comptroller's official open data ("Active Franchise Taxpayers" on data.texas.gov).** Filter by city, ZIP prefix, NAICS industry or entity type. Monitor mode delivers only entities you have not seen before. Useful for B2B sales, bankers, insurers, accountants, sign makers and local-market research.

*Not affiliated with or endorsed by the State of Texas, the Texas Comptroller of Public Accounts or the Texas Secretary of State.*

### What data does the Texas new LLC feed return?

One row per entity: `entityName`, `entityType` (Texas LLC, Texas profit corporation, foreign corporation, limited partnership and so on), `sosFileNumber`, `taxpayerNumber`, `charterDate`, `taxResponsibilityBeginDate`, `sosStatus`, `rightToTransactBusiness`, `naicsCode` (when present), `city`, `state`, 5-digit `zip`, `countyCode` and a source link.

### Companies only, no personal data

- **No street addresses**: the address column is never even requested; only city, state and 5-digit ZIP.
- **No individuals**: sole proprietors, individual partnerships, estates, trusts, general partnerships, government bodies and local officials are excluded both in the query and again in code.
- **Professional associations and corporations** (PA/PC, often named after a doctor or lawyer) are off by default; turn them on with **Include professional associations/corporations**.
- The dataset has no registered-agent or officer fields, so no people's names are collected.

### How to get a list of new Texas LLCs by city

1. Set **Look back (days)** (default 7, up to 365), or a **From date** and **To date**.
2. Add **Cities**, **ZIP prefixes**, **NAICS prefixes** or **Entity type codes** to narrow the list.
3. Run it to get newly chartered Texas LLCs, corporations and partnerships: name, type, file number, dates, status, NAICS, city and ZIP.

```json
{ "lookbackDays": 7, "cities": ["DALLAS", "FORT WORTH"], "monitorMode": true, "monitorStateName": "dfw-weekly" }
```

### Example output

Real, unedited rows from three small live test runs (Nov 2 and Nov 3, 2026; selected fields). Most new entities have no NAICS code yet; the third row was found with the NAICS prefix filter `5415`.

| entityName | entityType | sosFileNumber | charterDate | sosStatus | naicsCode | city | zip |
|---|---|---|---|---|---|---|---|
| TEXAS DENT FORGE GROUP, LLC | Texas LLC | 0806810976 | 2026-11-02 | Active | null | AUSTIN | 78731 |
| SHEER ENTERPRISES, INC. | Foreign profit corporation | 0806813075 | 2026-11-01 | Active | null | DALLAS | 75205 |
| FREEIT DATA SOLUTIONS, LLC | Texas LLC | 6000016900 | 2026-10-14 | Active | 541511 | AUSTIN | 78767 |

One full record, from the Dallas run (`cities: ["DALLAS"]`, 7-day look-back, Nov 3, 2026):

```json
{
  "taxpayerNumber": "32108267827",
  "entityName": "SHEER ENTERPRISES, INC.",
  "entityTypeCode": "CF",
  "entityType": "Foreign profit corporation",
  "sosFileNumber": "0806813075",
  "fileNumberType": "Certificate of Authority",
  "charterDate": "2026-11-01",
  "taxResponsibilityBeginDate": "2026-11-01",
  "sosStatus": "Active",
  "rightToTransactBusiness": "Active",
  "naicsCode": null,
  "city": "DALLAS",
  "state": "TX",
  "zip": "75205",
  "countyCode": "57",
  "source": "https://data.texas.gov/d/9cir-efmm",
  "checkedAt": "2026-11-03T15:12:52Z"
}
```

### Run it on a schedule

Turn on **Monitor mode** with a **Monitor name**, keep a 7-day **Look back (days)**, and schedule the Actor daily or weekly with an Apify schedule. The overlapping window catches late-posted records, and entities already delivered are skipped and not charged.

### Pricing

Pay per event: **$0.002 per entity delivered** ($2 per 1,000). Example: the dataset showed about 24,400 entities chartered in October 2026 (all types, about 5,600 a week), so a statewide weekly feed costs roughly $10-11; one city's weekly list of 300 costs $0.60.

Users on the free Apify plan get up to 100 entities per run.

### FAQ

**Where does the data come from?** The Texas Comptroller's "Active Franchise Taxpayers" open data on data.texas.gov, read through the portal's official API.

**Does it include people or home addresses?** No. It returns companies only, with city and ZIP, no street addresses, and no individual (sole-proprietor) filers. Professional associations and corporations are off by default.

**How fresh is it?** As fresh as the Comptroller's dataset, which is refreshed regularly; check `charterDate`.

**Why is the NAICS code often empty?** New entities often haven't reported an industry yet.

**Can I use it for outreach?** Yes, but any outreach must follow CAN-SPAM and other anti-spam and marketing laws. Verify an entity's status with the Texas Secretary of State before relying on it.

**Is it gentle on the portal?** Yes: one request per second (the portal's robots.txt crawl delay), 1,000 rows per request, official API only, no search pages.

### Is it legal?

It's built to use only public data. It reads public business information that the Texas Comptroller publishes as open data through the portal's official API, and it excludes individuals and street addresses. Any outreach must follow CAN-SPAM and other anti-spam and marketing laws. This isn't legal advice.

### Example input / example output

**Example input**

```json
{
  "lookbackDays": 1,
  "maxItems": 3,
  "cities": ["AUSTIN"],
  "monitorMode": false
}
```

**Example output** (one Texas new LLC)

```json
{
  "entityName": "EXAMPLE HOLDINGS LLC",
  "entityType": "Texas LLC",
  "charterDate": "2026-11-05",
  "sosStatus": "Active",
  "naicsCode": "541511",
  "city": "AUSTIN",
  "state": "TX",
  "zip": "78701",
  "sosFileNumber": "0801234567"
}
```

### Use it with Make, Zapier, n8n, or AI agents (Apify MCP)

- **Make:** In Make, add the Apify module, connect your Apify account, then run this Actor (or an Actor task) and map dataset items into your scenario. See [Make integration](https://docs.apify.com/integrations/make).
- **Zapier:** In Zapier, use Apify as a trigger (finished Actor/task run) or action (Run Actor / Run Task / Fetch dataset items). See [Zapier integration](https://docs.apify.com/integrations/zapier).
- **n8n:** Install the Apify node, authenticate, then use **Run an Actor** or **Run an Actor and get dataset**. See [n8n integration](https://docs.apify.com/integrations/n8n).
- **AI agents (Apify MCP):** Connect your MCP client to `https://mcp.apify.com`, then use `search-actors`, `fetch-actor-details`, and `call-actor`. Pull results with `get-dataset-items`. See [Apify MCP server](https://docs.apify.com/mcp).

**Related actors:** [Email Auth Checker](https://apify.com/jwaiworks/email-auth-checker) · [ATS Jobs Feed](https://apify.com/jwaiworks/ats-jobs-feed) · [SEC Form D Funding Monitor](https://apify.com/jwaiworks/sec-form-d-funding-monitor) · [PageSpeed & Core Web Vitals Monitor](https://apify.com/jwaiworks/pagespeed-cwv-monitor) · [Podcast Activity Monitor](https://apify.com/jwaiworks/podcast-activity-monitor) · [SAM.gov Opportunities Monitor](https://apify.com/jwaiworks/samgov-opportunities-monitor) · [USPTO Trademark New Filings Feed](https://apify.com/jwaiworks/uspto-trademark-new-filings) · [Copycat Store & Lookalike Domain Suspect Checker](https://apify.com/jwaiworks/copycat-store-checker)

### Disclaimer

Provided as is; not an official record. Verify with the Texas Secretary of State before relying on an entity's status. Not affiliated with or endorsed by the State of Texas, the Texas Comptroller of Public Accounts or the Texas Secretary of State.

# Actor input Schema

## `lookbackDays` (type: `integer`):

How many days back to look for Texas new LLC and corporation charters, ending today, for example `7` for the past week (up to 365). Ignored when From/To dates are set.

## `sinceDate` (type: `string`):

The first date to include, in YYYY-MM-DD format, for example `2026-10-01`. Optional; leave empty to use Look back (days).

## `untilDate` (type: `string`):

The last date to include, in YYYY-MM-DD format, for example `2026-10-31`. Optional; leave empty for today.

## `dateField` (type: `string`):

Which date decides whether an entity is new, for example the charter date (when it was chartered or registered with the Texas Secretary of State, the default) or the date it became liable for franchise tax.

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

Only include entities in these Texas cities, for example `AUSTIN` or `FORT WORTH`. Leave empty for all cities.

## `zipPrefixes` (type: `array`):

Only include entities whose ZIP code starts with these digits, for example `787` for the Austin area or `75201` for one ZIP. Leave empty for all ZIP codes.

## `naicsPrefixes` (type: `array`):

Only include entities whose NAICS industry code starts with these digits, for example `5415` for computer systems design services. Many new entities have no NAICS code yet, so this filter can return few results.

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

Only include these entity type codes, for example `CL` (Texas LLC), `CT` (Texas profit corporation). Leave empty for the default Texas new LLC and corporation set.

## `includeProfessionalEntities` (type: `boolean`):

Turn this on to include professional associations and corporations (PA/PC), for example law, medical or accounting practices. They are off by default because they are often named after a person.

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

The most entities to deliver in one run, for example `100`. Leave empty for no cap.

## `monitorMode` (type: `boolean`):

Turn this on to skip entities this monitor has already delivered, for example on a weekly schedule with a 7-day look-back. Skipped entities are not charged.

## `monitorStateName` (type: `string`):

A name for this monitor's memory, for example `dfw-weekly`. Each name keeps its own list of delivered entities.

## `apiBaseUrl` (type: `string`):

The open data portal address, for example `https://data.texas.gov`, which is the default and the only accepted value, so leave this as it is.

## Actor input object example

```json
{
  "lookbackDays": 7,
  "dateField": "charter",
  "includeProfessionalEntities": false,
  "monitorMode": false,
  "monitorStateName": "default",
  "apiBaseUrl": "https://data.texas.gov"
}
```

# Actor output Schema

## `overview` (type: `string`):

Default dataset items in the overview view.

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

Default dataset items with every field.

## `runSummary` (type: `string`):

RUN_SUMMARY record in the default key-value store (counts, warnings, free-plan cap).

# 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("jwaiworks/texas-new-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 = {}

# Run the Actor and wait for it to finish
run = client.actor("jwaiworks/texas-new-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 '{}' |
apify call jwaiworks/texas-new-business-entities --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,jwaiworks/texas-new-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/tcZNvHvmc8oh7vBNl/builds/89zgGMMdqV9gOQDji/openapi.json