# Texas New Business Leads: New LLCs & Corps (Comptroller) (`atlasagent99/texas-new-entity-leads`) Actor

Daily new Texas LLCs and corporations from the Comptroller's official franchise-tax open data: name, mailing address, county, NAICS, SOS file number, charter date and status. Filter by city, ZIP, county, NAICS. Also bulk status lookup by taxpayer number.

- **URL**: https://apify.com/atlasagent99/texas-new-entity-leads.md
- **Developed by:** [Texasbread](https://apify.com/atlasagent99) (community)
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

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

## Texas New Business Leads: New LLCs & Corps (Comptroller open data)

Get **newly registered Texas LLCs and corporations** every day, straight from the Texas Comptroller's official *Active Franchise Taxpayers* open dataset (3.5M+ entities, ~24k new charters per month). Filter by city, ZIP, county or NAICS industry code, or bulk-check the status of up to 500 taxpayer numbers.

### Who it's for

- Insurance, banking, payroll, bookkeeping, signage, web-design and B2B sales teams who want to reach **brand-new Texas businesses** first.
- KYB / compliance teams checking whether entities still have the **right to transact business** in Texas.

### What you get (one row per entity)

`businessName`, `address`, `city`, `state`, `zip`, `countyCode`, `countyFips`, `naicsCode` (when published), `entityTypeCode`, `sosFileNumber`, `sosCharterDate`, `sosStatusCode`, `rightToTransactCode`, `franchiseTaxResponsibilityBegan`, `taxpayerNumber`, exemption fields and a source link.

Business entity data only. No personal names, phones or emails are output.

### Examples

- New Austin businesses this week: `{"cities":["AUSTIN"],"charteredWithinDays":7}`
- New construction companies in Harris County, last 30 days: `{"countyCodes":["101"],"naicsPrefixes":["236","238"],"charteredWithinDays":30}`
- Bulk status check: `{"taxpayerNumbers":["32107827142"]}`

### Codes

- `entityTypeCode` is the Comptroller's raw organization code (most common: CL, CT, CI, CN, CF, PL). CL is limited liability company; for the full list see the Comptroller's record layout linked from the dataset page.
- `rightToTransactCode` `A` = active.
- `countyCode` is the Comptroller's county number (1-254, alphabetical); `countyFips` is derived for Texas addresses.

### Pricing

Pay per result. Use **Max results** to cap your spend.

### Source & terms

Data: https://data.texas.gov/d/9cir-efmm (Texas Comptroller of Public Accounts, public open data). Updated by the Comptroller; the actor reads the official Socrata API, honors robots.txt and its 1-second crawl delay. Mailing addresses can be a registered agent's or owner's address. Verify with the Comptroller before legal use.

# Actor input Schema

## `charteredWithinDays` (type: `integer`):

Only entities whose Texas SOS charter/registration date is in the last N days. Leave empty for all active entities.

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

Mailing-address cities, e.g. HOUSTON, DALLAS. Empty = all.

## `zips` (type: `array`):

5-digit ZIPs. Empty = all.

## `countyCodes` (type: `array`):

Comptroller county number 1-254 (alphabetical; e.g. 101 = Harris, 57 = Dallas, 227 = Travis, 15 = Bexar, 220 = Tarrant).

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

e.g. 236 (construction), 722 (restaurants), 5412 (accounting). Only rows that publish a NAICS code match.

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

Raw Comptroller organization codes, e.g. CL (LLC), CT, CI, CN, CF, PL. See README.

## `nameContains` (type: `string`):

Case-insensitive text in the business name.

## `taxpayerNumbers` (type: `array`):

Bulk status lookup by 11-digit Texas taxpayer number (up to 500). When set, other filters are ignored.

## `texasAddressOnly` (type: `boolean`):

Skip out-of-state entities registered in Texas.

## `activeRightToTransactOnly` (type: `boolean`):

Only entities whose Texas right to transact business is active (code A).

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

You pay per result; this caps cost.

## Actor input object example

```json
{
  "charteredWithinDays": 7,
  "cities": [
    "AUSTIN"
  ],
  "texasAddressOnly": true,
  "activeRightToTransactOnly": false,
  "maxItems": 50
}
```

# 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 = {
    "charteredWithinDays": 7,
    "cities": [
        "AUSTIN"
    ],
    "maxItems": 50
};

// Run the Actor and wait for it to finish
const run = await client.actor("atlasagent99/texas-new-entity-leads").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 = {
    "charteredWithinDays": 7,
    "cities": ["AUSTIN"],
    "maxItems": 50,
}

# Run the Actor and wait for it to finish
run = client.actor("atlasagent99/texas-new-entity-leads").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 '{
  "charteredWithinDays": 7,
  "cities": [
    "AUSTIN"
  ],
  "maxItems": 50
}' |
apify call atlasagent99/texas-new-entity-leads --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,atlasagent99/texas-new-entity-leads"
        }
    }
}
```

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/Iz1wW8nZTQrjFsdy2/builds/hRHOXjYubYLwscegZ/openapi.json