# Texas Restaurant Inspection Tracker — Austin & Dallas (`recordstack/texas-restaurant-inspection-tracker`) Actor

Restaurant and food-establishment inspection scores from the official Austin and Dallas open-data feeds, normalized into one schema with computed score bands, violation details and an only-new mode.

- **URL**: https://apify.com/recordstack/texas-restaurant-inspection-tracker.md
- **Developed by:** [Alex Meacham](https://apify.com/recordstack) (community)
- **Categories:** Lead generation, Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$4.00 / 1,000 inspections

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 Restaurant Inspection Tracker — Austin & Dallas

Restaurant and food-establishment inspection scores from the official
open-data feeds of Austin and Dallas, normalized into ONE schema.

### Why this exists

Austin (datahub.austintexas.gov) and Dallas (dallasopendata.com)
publish the same kind of record with completely incompatible fields —
Dallas splits violations across 11 numbered column sets, Austin uses a
single combined address string. This actor merges both into one clean
output with a **computed score band** (A 90–100, B 80–89, C 70–79,
Fail below 70), Dallas violation details flattened into a list, and an
**only-new monitor mode** so a scheduled run surfaces just the
inspections you have not seen.

### Who buys it

Food-safety and compliance watchers, restaurant suppliers and POS
companies prospecting by score, local media and data teams tracking
openings and problem kitchens.

### Inputs

- `cities` — Austin and/or Dallas (default both)
- `inspectedWithinDays` — recency window (default 200)
- `failingOnly` — only scores below 70
- `maxScore` — optional score ceiling
- `zipPrefix` — optional ZIP filter
- `onlyNewSinceLastRun` — monitor mode
- `maxResults` — per-run cap (you are only charged per record)

### Honest limit

The City of Dallas stopped updating its inspection dataset in
February 2024 (78,984 historical records). Austin's feed is current
(20,421 records, latest inspection 2026-09-24 at last check). To pull
Dallas history, set `inspectedWithinDays` to ~1000 or more.

### Price

$0.004 per normalized inspection record delivered.

# Actor input Schema

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

Which city feeds to include: Austin and/or Dallas. Note: Dallas's feed ends Feb 2024; set inspectedWithinDays to ~1000+ to include its history.

## `inspectedWithinDays` (type: `integer`):

Only inspections from the last N days.

## `failingOnly` (type: `boolean`):

Only inspections scoring below 70 (the Austin pass mark).

## `maxScore` (type: `integer`):

Optional: only inspections at or below this score.

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

Optional: only this ZIP code or prefix, e.g. 78704.

## `onlyNewSinceLastRun` (type: `boolean`):

Monitor mode: return only inspections this actor has not delivered in earlier runs.

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

Cap on records delivered (and charged) per run.

## Actor input object example

```json
{
  "cities": [
    "Austin",
    "Dallas"
  ],
  "inspectedWithinDays": 200,
  "failingOnly": false,
  "zipPrefix": "",
  "onlyNewSinceLastRun": false,
  "maxResults": 1000
}
```

# Actor output Schema

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

Open the dataset with the inspections found in 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-restaurant-inspection-tracker").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-restaurant-inspection-tracker").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-restaurant-inspection-tracker --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,recordstack/texas-restaurant-inspection-tracker"
        }
    }
}
```

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/HFacFJwuNifjhW9OK/builds/BZA7kZ5gvldeqUKeq/openapi.json