# Texas Franchise Tax Permit Holders — TX Taxpayer Search (`nexgendata/texas-franchise-tax-registry`) Actor

Search the Texas Comptroller Active Franchise Taxpayers register (3.4M+ permit holders). Name search returns taxpayer number, name, address, org type, and right-to-transact status. The franchise-tax register — NOT the Secretary of State corporate registry.

- **URL**: https://apify.com/nexgendata/texas-franchise-tax-registry.md
- **Developed by:** [NexGenData](https://apify.com/nexgendata) (community)
- **Categories:** Business, Lead generation
- **Stats:** 1 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $100.00 / 1,000 tx taxpayer matches

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/platform/actors/running/actors-in-store#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

## Texas Franchise Tax Permit Holders Search

Search the Texas Comptroller of Public Accounts "Active Franchise Taxpayers" register (3.4M+ permit holders). Pass one or more names; get matching Texas franchise-tax permit holders.

> **What this is (and isn't):** this is the Comptroller's register of entities holding an **active Texas franchise-tax account** (franchise-tax permit holders) — NOT the Texas Secretary of State corporate registry. The SoS corporate registry (SOSDirect) is not available as public keyless/bulk data. Factual public records — not legal or investment advice.

### 📊 What you get

Clean JSON, one record per taxpayer:

- `taxpayer_name` — Taxpayer / entity name
- `taxpayer_number` — Texas taxpayer number (canonical id)
- `address` — Taxpayer address
- `organizational_type` — Comptroller organizational type code
- `responsibility_beginning_date` — Franchise-tax responsibility begin date
- `right_to_transact_business` — Right-to-transact-business status (Active, Forfeited, etc.)

**Pricing:** $0.100 per taxpayer (Pay-Per-Event) — about **10 per $1**. Empty or blocked runs never bill.

### 🤖 Use with AI agents

Point Claude, the OpenAI Agents SDK, an n8n flow or your own code at it and confirm active Texas franchise-tax registration on demand.

### 🇺🇸 US State Business Registries — full family

Part of the NexGenData US state business-registry family — same input shape, same $0.10-per-record pricing:

- **[Delaware](https://apify.com/nexgendata/delaware-corporations-search-scraper)** — the original: DE Division of Corporations lookup (~1.8M entities; file number + entity name).
- **[New York](https://apify.com/nexgendata/new-york-corporations-search-scraper)** — 4.27M active entities; official DOS record with registered agent + CEO.
- **[Pennsylvania](https://apify.com/nexgendata/pennsylvania-corporations-search-scraper)** — 4.07M records; full registered-officer lists per entity.
- **[Colorado](https://apify.com/nexgendata/colorado-business-entity-search-scraper)** — 3.10M entities; live entity status + registered agent.
- **[Connecticut](https://apify.com/nexgendata/connecticut-business-registry-scraper)** — 1.29M entities; business contact + diversity-ownership flags.
- **[Oregon](https://apify.com/nexgendata/oregon-business-registry-scraper)** — 1.57M entities; registered agent + registry date.

***

*Public records from the Texas Comptroller of Public Accounts, assembled for research and monitoring.*

# Actor input Schema

## `entityNames` (type: `array`):

List of taxpayer-name strings to search (partial match, case-insensitive). Each search returns matching active Texas franchise-tax permit holders. Multiple strings = multiple searches.

## `maxEntities` (type: `integer`):

Hard cap on total taxpayers returned across ALL searches in this run (1-2000). Each taxpayer is one dataset row.

## Actor input object example

```json
{
  "entityNames": [
    "Apple"
  ],
  "maxEntities": 5
}
```

# 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 = {
    "entityNames": [
        "Apple"
    ],
    "maxEntities": 5
};

// Run the Actor and wait for it to finish
const run = await client.actor("nexgendata/texas-franchise-tax-registry").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 = {
    "entityNames": ["Apple"],
    "maxEntities": 5,
}

# Run the Actor and wait for it to finish
run = client.actor("nexgendata/texas-franchise-tax-registry").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 '{
  "entityNames": [
    "Apple"
  ],
  "maxEntities": 5
}' |
apify call nexgendata/texas-franchise-tax-registry --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,nexgendata/texas-franchise-tax-registry"
        }
    }
}

```

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/d05SNNPgsekAXe297/builds/mactePQcUpcQrSYwS/openapi.json