Texas Franchise Taxpayer Status Check avatar

Texas Franchise Taxpayer Status Check

Pricing

from $33.50 / 1,000 franchise status checks

Go to Apify Store
Texas Franchise Taxpayer Status Check

Texas Franchise Taxpayer Status Check

A per-identity check: submit identifiers, get one official answer each. Billed per completed official answer — an unresolved, ambiguous, or unavailable outcome is returned but never charged.

Pricing

from $33.50 / 1,000 franchise status checks

Rating

0.0

(0)

Developer

NexGen Watch

NexGen Watch

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

4 days ago

Last modified

Share

🔎 Texas Franchise Taxpayer Status Check

A per-identity check: submit identifiers, get one official answer each. Billed per completed official answer — an unresolved, ambiguous, or unavailable outcome is returned but never charged.

Output is one franchise_status_answer row per result; billing is pay-per-event, the value event being one franchise status check (a $0.02 start fee per run, then $0.05 per franchise status check). Source: comptroller.texas.gov.

No login, no API key and no CAPTCHA solving are involved: the source is read logged-out with an identified contact User-Agent.

📊 Sample Output

Texas Franchise Taxpayer Status Check sample output — a table of real franchise status check rows (taxpayer_id, fei_number, name, sos_registration_date) from run wowVLnrlLjM666w61 on build 0.1.4

Real rows from run wowVLnrlLjM666w61 on build 0.1.4 (2026-09-17), the same input as the Quick start below — every value is as the source published it (emails masked, long text shortened):

taxpayer_idfei_numbernamesos_registration_datesos_file_numberregistered_agent_name
32106582219800890963DELL TECHNOLOGIES INC.06/26/20260806671479CORPORATION SERVICE COMPANY DBA CSC - LAWYERS INCO
32106582219800890963DELL TECHNOLOGIES INC.06/26/20260806671479CORPORATION SERVICE COMPANY DBA CSC - LAWYERS INCO

The run finished with the status message: NORMAL: 2 billable answer(s), 0 definitive non-billable (not-found/ambiguous), 0 unavailable, 0 unparseable of 2 | franchise-status-check billable=2 | franchise-status-check charged=2

✅ What you get

Each row is flat JSON with these fields (from the dataset schema and the sample run; a field the source does not publish for a given row is null):

  • query_mode (string/null) — e.g. id
  • taxpayer_id (string/null) — e.g. 32106582219
  • fei_number (string/null) — e.g. 800890963
  • name (string/null) — e.g. DELL TECHNOLOGIES INC.
  • dba_name (string/null) — null in every sample row
  • right_to_transact (string/null) — e.g. ACTIVE
  • state_of_formation (string/null) — e.g. TX
  • sos_registration_status (string/null) — e.g. ACTIVE
  • sos_registration_date (string/null) — e.g. 06/26/2026
  • sos_file_number (string/null) — e.g. 0806671479
  • registered_agent_name (string/null) — e.g. CORPORATION SERVICE COMPANY DBA CSC - LAWYERS INCO
  • registered_office_city (string/null) — e.g. AUSTIN
  • registered_office_state (string/null) — e.g. TX
  • mailing_city (string/null) — e.g. ROUND ROCK
  • mailing_state (string/null) — e.g. TX
  • mailing_zip (string/null) — e.g. 78682
  • report_year (string/null) — null in every sample row
  • last_updated (string/null) — e.g. 2026-09-17T17:49:49.094Z
  • record_type (string/null) — e.g. franchise_status_answer
  • input (string/null) — e.g. 32106582219
  • source (string/null) — e.g. https://comptroller.texas.gov/data-search/franchise-tax
  • outcome (string/null) — e.g. answer
  • outcome_reason (string/null) — null in every sample row

What you get

One record per submitted identity. A resolved identity carries the official status fields verbatim; fields the source withholds are honest null with a reason. Not-found, ambiguous, and service-unavailable outcomes are distinguished in the outcome field and are not billed. A run that gets no definitive result at all fails loud and charges nothing.

⚙️ Sample inputs

1. Quick start — the Store example (this is what the sample above came from)

{
"taxpayers": [
"32106582219",
"DELL TECHNOLOGIES INC"
]
}

The sample run charged exactly: 1 × $0.02 apify-actor-start + 2 × $0.05 franchise-status-check = $0.12 on the Free tier — every delivered row was billed.

2. A smaller, narrowed run

{
"taxpayers": [
"32106582219",
"DELL TECHNOLOGIES INC"
]
}

A bounded run for checking the field shape before scheduling.

3. A full-size run

{
"taxpayers": [
"32106582219",
"DELL TECHNOLOGIES INC"
]
}

The same input run on a schedule; each run is billed only for what it delivers.

🧾 JSON sample record

One real record from run wowVLnrlLjM666w61, exactly as it lands in the dataset (emails masked, long text shortened):

{
"query_mode": "id",
"taxpayer_id": "32106582219",
"fei_number": "800890963",
"name": "DELL TECHNOLOGIES INC.",
"dba_name": null,
"right_to_transact": "ACTIVE",
"state_of_formation": "TX",
"sos_registration_status": "ACTIVE",
"sos_registration_date": "06/26/2026",
"sos_file_number": "0806671479",
"registered_agent_name": "CORPORATION SERVICE COMPANY DBA CSC - LAWYERS INCO",
"registered_office_city": "AUSTIN",
"registered_office_state": "TX",
"mailing_city": "ROUND ROCK",
"mailing_state": "TX",
"mailing_zip": "78682",
"report_year": "",
"last_updated": "2026-09-17T17:49:49.094Z",
"record_type": "franchise_status_answer",
"input": "32106582219",
"source": "https://comptroller.texas.gov/data-search/franchise-tax",
"outcome": "answer",
"outcome_reason": null
}

🔧 How it works

Transport. Plain HTTPS from the Apify platform, no proxy. Every request carries an identified contact User-Agent.

Charging. Each franchise status check is charged at the moment it is pushed (franchise-status-check); a row that fails to charge is not delivered, so the dataset count always equals the charged count.

How it behaves

Each taxpayer is resolved against the Texas Comptroller's franchise-tax account-status service. An 11-digit taxpayer number resolves directly; a SOS file number or an exact name is searched and only a unique match is followed to the account. A resolved account returns right-to-transact and SOS registration status verbatim and is billed. A name that matches more than one taxpayer returns an ambiguity (refine by taxpayer number) and is not billed; a not-found or a service outage is not billed. The record never claims broader good standing than the Comptroller states.

Billing

EventFREEBRONZESILVERGOLD+
apify-actor-start (one-time actor start)$0.02$0.02$0.02$0.02
franchise-status-check (per completed official answer)$0.05$0.045$0.04$0.0335

Charged once per completed official answer. Invalid / not-found, ambiguous, and service-fault outcomes are emitted but never charged. Start fee $0.02.

Source

https://comptroller.texas.gov/data-search/franchise-tax

What is not done. No login, no cookie or CAPTCHA bypass, no private or personal-account data, no browser automation.

💰 Pricing example

EventFreeBronzeSilverGold
Actor Start (apify-actor-start)$0.02$0.02$0.02$0.02
Franchise Status Check (franchise-status-check)$0.05$0.04$0.04$0.03

Worked at the live Free-tier price:

  • 2 franchise status checks: $0.02 start + 2 × $0.05 = $0.12
  • 25 franchise status checks: $0.02 start + 25 × $0.05 = $1.27
  • 100 franchise status checks: $0.02 start + 100 × $0.05 = $5.02

A run that delivers zero rows charges the $0.02 start fee only. A BLOCKED run (source refused) fails loud and charges no value event. The start fee is charged once per GB of run memory; the default run memory is 1024 MB.

Yield on the sample run: NORMAL: 2 billable answer(s), 0 definitive non-billable (not-found/ambiguous), 0 unavailable, 0 unparseable of 2 | franchise-status-check billable=2 | franchise-status-check charged=2.

This actor reads public, logged-out pages and feeds published by comptroller.texas.gov. It collects only what the source publishes to any visitor, identifies itself with a contact User-Agent, and does not access accounts, private data or anything behind authentication. Use the output in line with the source's terms and your local law; the intended use is B2B research and monitoring.

❓ FAQ

Q: Do I need an API key or a login?
A: No. The source (comptroller.texas.gov) is read logged-out; the input schema has no key field and the actor carries no secrets.

Q: Why did my run return 0 rows?
A: Read the run's status message. GENUINE_EMPTY means the source was read and had nothing in scope for your input; BLOCKED means the source refused and the run failed without billing a value event — retry later or narrow the input. A zero-row run bills the start fee only.

Q: How fresh is the data?
A: Every run reads the source live at run time; nothing is cached between runs. Put it on a schedule for a continuous feed.

Q: What formats can I export?
A: The dataset downloads as JSON, CSV, Excel, XML or RSS from the run's Dataset tab or the Apify API, and any run can push to a webhook or integration.

Q: How is this different from the other company registry checks actors?
A: Same output shape and billing model; this one covers comptroller.texas.gov. The siblings under Related Actors cover the other sources or slices — run several on one schedule for a combined feed.

Q: Are there rate limits?
A: The actor paces itself against the source; there is no per-buyer limit beyond your Apify plan's concurrency.

🆘 Troubleshooting

  • Run FAILED with BLOCKED → the source refused the request or changed its page shape → nothing was billed beyond the start fee; retry after a while, and if it persists open an Issue with the run id.
  • Fewer rows than expected → the source had fewer items in scope → widen the input.
  • Input validation error on start → a field is outside the schema's allowed values → start from the Quick start block and change one field at a time.
  • Run TIMED-OUT → a very wide request on a slow day → raise the run timeout in Run options or narrow the input; what was delivered before the timeout is still in the dataset.

⭐ Found this useful?

If this actor saved you a manual check, a quick review on the Apify Store helps other teams find it. Feature request or a source that changed? Open it from the Issues tab — every one is read.