# Texas New Business Pulse: New Sales Tax Permit Outlets (`atlasagent99/texas-new-outlet-pulse`) Actor

Newly permitted Texas business locations from Comptroller open data (Active Sales Tax Permit Holders): outlet name, address, county, NAICS industry and permit/first-sales dates. Filter by county and industry. No owner/taxpayer data.

- **URL**: https://apify.com/atlasagent99/texas-new-outlet-pulse.md
- **Developed by:** [Texasbread](https://apify.com/atlasagent99) (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

from $3.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 Pulse: New Sales Tax Permit Outlets

Get **newly permitted Texas business locations** from the Texas Comptroller's public open dataset of Active Sales Tax Permit Holders (data.texas.gov dataset `jrea-zgmq`). Filter by county and NAICS industry to find brand-new stores, restaurants and service businesses near you.

### Who it's for

Insurance agents, POS and payroll providers, signage, uniform and B2B suppliers, local marketing agencies: anyone who sells to new businesses in their first weeks.

### What you get

| Field | Description |
|---|---|
| outlet_name | Outlet (location) name |
| address, city, zip, county | Outlet location |
| industryCode / industryTitle | NAICS code and title |
| permitIssueDate | Sales tax permit issue date |
| firstSalesDate | First sales date reported to the Comptroller |
| redacted | true when name/address were withheld for privacy |
| dataAsOf | Newest date in the source; the day window counts back from it |
| sourceDataset | Source dataset id |

### Input

Filter by permit date window (days), county and NAICS prefix.

### Privacy

Taxpayer (owner) names and addresses are never requested or output. For individual owners (Comptroller org types IS, S, PI, PZ, ES) the outlet name and street address are always null; city, ZIP, county, industry and dates are still returned. Registered entities (LLC, corporation, nonprofit, etc.) always show the outlet name. Only when the org type is blank is a name heuristic used to null person-like names.

### Pricing

Pay per result: you are charged for each row written to the dataset. The Actor stops automatically when your spending limit is reached.

### Data source and freshness

Official Texas Open Data portal (Socrata API), allowed by the portal's robots.txt. Results are only as fresh as the Comptroller's published dataset.

### Questions or a missing feature?

Open an issue on the Actor's Issues tab.

# Actor input Schema

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

Ignored if From date is set. Counted back from the newest permit date in the source (output field dataAsOf), not today, because the source lags about a week.

## `fromDate` (type: `string`):

Optional permit issue date start

## `toDate` (type: `string`):

Optional permit issue date end

## `counties` (type: `array`):

Texas county names, e.g. Travis, Harris. Empty = statewide

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

e.g. 722 (restaurants), 4451 (grocery), 8121 (salons)

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

0 = no limit

## Actor input object example

```json
{
  "issuedWithinDays": 7,
  "counties": [
    "Travis"
  ],
  "naicsPrefixes": [],
  "maxItems": 0
}
```

# 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 = {
    "counties": [
        "Travis"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("atlasagent99/texas-new-outlet-pulse").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 = { "counties": ["Travis"] }

# Run the Actor and wait for it to finish
run = client.actor("atlasagent99/texas-new-outlet-pulse").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 '{
  "counties": [
    "Travis"
  ]
}' |
apify call atlasagent99/texas-new-outlet-pulse --silent --output-dataset

```

## MCP server setup

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

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/H0zkbBgD7xBiS3ePq/builds/gsrQ42C6O1AJER9t9/openapi.json