# CAT Dealer & Service Center Scraper (`spry_frame/cat-dealer-scraper`) Actor

Scrapes Caterpillar (CAT) dealer and authorized service center directory from cat.com. Returns name, address, phone, website, hours, services, coordinates, and dealer type for every US location.

- **URL**: https://apify.com/spry\_frame/cat-dealer-scraper.md
- **Developed by:** [COSENT GROUP](https://apify.com/spry_frame) (community)
- **Categories:** Lead generation, Other
- **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/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

## CAT Dealer & Service Center Scraper

Scrapes the complete Caterpillar (CAT) dealer and authorized service center directory from [cat.com](https://www.cat.com/en_US/support/dealer-locator.html).

### What it does

Queries the CAT dealer locator API using a grid of geographic coordinates covering all 50 US states. Each query returns up to 50 locations and paginates via cursor until exhausted. Results are deduplicated by `dealerLocationId`.

No proxies required — cat.com does not use Cloudflare Bot Fight Mode.

### Output fields

| Field | Description |
|---|---|
| `dealerLocationId` | Unique location ID |
| `dealerLocationName` | Branch/location name |
| `dealerName` | Parent dealer company name |
| `locationType` | Dealer type (e.g. TEPS) |
| `streetAddress` | Street address |
| `city` | City |
| `state` | State abbreviation |
| `postalCode` | ZIP code |
| `country` | Country |
| `phone` | Phone number(s) |
| `website` | Dealer website |
| `shopWebsite` | Parts/shop website |
| `latitude` | Latitude |
| `longitude` | Longitude |
| `districtName` | CAT sales district |
| `regionName` | CAT sales region |
| `services` | Services offered (Sales of Parts, Sales of Service, etc.) |
| `hours` | Store hours |
| `isSubDealer` | Whether this is a sub-dealer location |
| `dealerCode` | CAT dealer code |

### Input

| Parameter | Type | Default | Description |
|---|---|---|---|
| `states` | string\[] | `[]` | Filter by state codes e.g. `["TX","CA"]`. Empty = all states |
| `locationType` | string | `""` | API location type filter |
| `maxResults` | integer | `100` | Cap on results (0 = unlimited) |

# Actor input Schema

## `states` (type: `array`):

Only return dealers in these US state abbreviations (e.g. \["TX", "CA"]). Leave empty for all states.

## `locationType` (type: `string`):

Filter by dealer type sent to the API (e.g. 'Digital'). Leave blank for all types.

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

Maximum number of dealer locations to return. Set to 0 for unlimited.

## Actor input object example

```json
{
  "states": [],
  "locationType": "",
  "maxResults": 100
}
```

# Actor output Schema

## `dealerLocationId` (type: `string`):

Unique CAT dealer location identifier.

## `dealerLocationName` (type: `string`):

Branch or location name.

## `dealerName` (type: `string`):

Parent dealer company name.

## `locationType` (type: `string`):

Dealer type code (e.g. TEPS).

## `streetAddress` (type: `string`):

Street address.

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

City.

## `state` (type: `string`):

State abbreviation.

## `postalCode` (type: `string`):

Postal / ZIP code.

## `country` (type: `string`):

Country name.

## `phone` (type: `string`):

Phone number(s).

## `website` (type: `string`):

Dealer website URL.

## `shopWebsite` (type: `string`):

Parts / shop website URL.

## `latitude` (type: `string`):

Latitude coordinate.

## `longitude` (type: `string`):

Longitude coordinate.

## `districtName` (type: `string`):

CAT sales district name.

## `regionName` (type: `string`):

CAT sales region name.

## `services` (type: `string`):

Semicolon-separated list of services offered.

## `hours` (type: `string`):

Store hours by day.

## `isSubDealer` (type: `string`):

Whether this is a sub-dealer location.

## `dealerCode` (type: `string`):

CAT eCommerce dealer code.

## `scrapedAt` (type: `string`):

ISO 8601 timestamp of when this record was scraped.

# 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("spry_frame/cat-dealer-scraper").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("spry_frame/cat-dealer-scraper").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 spry_frame/cat-dealer-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,spry_frame/cat-dealer-scraper"
        }
    }
}

```

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/EQ5YLoRDjOqyeqYwK/builds/GM0brAhVNQPTSU1SJ/openapi.json