# Texas New Business Leads — Fresh Sales-Tax Permits (`recordstack/texas-new-business-leads`) Actor

New Texas businesses at the earliest public signal: a freshly issued Comptroller sales-tax permit. Filter by city, ZIP, county, or NAICS industry, with a 'genuinely new only' mode that excludes reissued permits. From the official Texas open-data register.

- **URL**: https://apify.com/recordstack/texas-new-business-leads.md
- **Developed by:** [Alex Meacham](https://apify.com/recordstack) (community)
- **Categories:** Lead generation, Developer tools
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 90.9% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$4.00 / 1,000 new business lead delivereds

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 — Fresh Sales-Tax Permits

**Find Texas businesses the week they get their sales-tax permit — before the Google listing, before the signage, before your competitors' lists notice them.**

A new sales-tax permit is one of the earliest public signals a business exists. The Texas Comptroller publishes every active permit on the state's open-data portal, including the issue date for each outlet. This actor turns that register into a lead feed: only the fresh permits, filtered your way.

Measured volume: **3,384 permits issued statewide in the trailing 7 days** (≈480/day), out of ~893,000 active outlets.

### What you get

One row per newly permitted outlet:

- Business (taxpayer) name, organization type, and taxpayer number
- Outlet name and **outlet address** (the business location the permit covers), city, ZIP, county code
- NAICS industry code
- Permit issue date — and the outlet's **first sales date**, which is sometimes in the future: a business that hasn't opened yet is the best lead there is

### Who it's for

- **POS, payments, insurance, payroll, signage, web/marketing, and commercial services** sellers who win by reaching new businesses first.
- **Franchisors and site-selection analysts** tracking openings by industry and geography.
- Anyone building a Texas new-business feed who doesn't want to wrestle a 893k-row register into shape themselves.

### Inputs

| Input | What it does |
|---|---|
| Permit issued within (days) | Recency window, default 30 |
| City · ZIP prefix · County code | Geography filters |
| NAICS code prefix | Industry filter — `7225` restaurants, `238` specialty trades, `44` retail… |
| **Genuinely new outlets only** | Excludes permits reissued to existing businesses by also requiring the first-ever sales date to fall in the window |
| Max results | Cap per run (you're only charged for what's delivered) |

### Pricing

**$0.004 per lead** ($4 per 1,000) — the same price point the store's established new-business-filings actors charge, for a single official source with zero scraping fragility.

### Honest notes

- "New permit" ≠ always "brand-new business": permits get reissued, and existing companies open additional outlets. Both dates are on every row so you can judge, and the *Genuinely new only* switch filters to first-time outlets.
- Source is the Texas Comptroller's official register via the state open-data API — no scraping, no login. The register is the state's own publication schedule; issue dates are the Comptroller's.
- Personal-data discipline: the taxpayer **mailing** address is never emitted (for sole proprietors it can be a home or PO box). Only the outlet — the business location the permit is for — is included. The dataset contains no phone numbers or emails, and neither does this actor's output.
- Texas only, by design: one state, done properly, beats a shallow 50-state blend for Texas-focused sellers.

### Verified before listing

Local end-to-end tests, 2026-10-27: Austin + last-7-days returned 10 correctly shaped leads (sample: `sample-output.json`); NAICS `7225` returned only restaurant outlets; *Genuinely new only* returned Austin outlets whose first sales dates fall in-window — including two that haven't opened yet (first sales 2026-11-15 and 2026-12-01).

# Actor input Schema

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

Outlet city, case-insensitive (e.g. 'Austin', 'Houston'). Leave empty for statewide.

## `countyCode` (type: `string`):

Texas Comptroller county code for the outlet county (e.g. '227' = Travis). Leave empty for all counties.

## `genuinelyNewOnly` (type: `boolean`):

Permits are sometimes reissued to long-running businesses. Turn this on to require the outlet's first-ever sales date to also fall inside the window — only genuinely new outlets (including ones whose first sales date is still in the future: opening soon).

## `issuedWithinDays` (type: `integer`):

Only outlets whose sales-tax permit was issued within this many days before the run.

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

Cap on lead rows delivered (and charged) in this run.

## `naicsPrefix` (type: `string`):

NAICS industry code prefix (2–6 digits). Examples: '7225' restaurants, '238' specialty trade contractors, '44' retail, '62' health care. Leave empty for all industries.

## `zipPrefix` (type: `string`):

ZIP code prefix for the outlet address (e.g. '787' for the Austin metro). Leave empty for statewide.

## Actor input object example

```json
{
  "city": "Austin",
  "countyCode": "227",
  "genuinelyNewOnly": false,
  "issuedWithinDays": 30,
  "maxResults": 100,
  "naicsPrefix": "7225",
  "zipPrefix": "787"
}
```

# Actor output Schema

## `datasetUrl` (type: `string`):

URL to the dataset containing the rows from this 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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("recordstack/texas-new-business-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 = {}

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

```

## MCP server setup

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