# Auto Repair Change Monitor (`repairiq/auto-repair-change-monitor`) Actor

Persist shop snapshots and emit structured technology, hiring, reputation, and capability changes.

- **URL**: https://apify.com/repairiq/auto-repair-change-monitor.md
- **Developed by:** [Ryan Carter](https://apify.com/repairiq) (community)
- **Categories:** Automation, Business
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $5.00 / 1,000 monitored entities

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?

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

## Auto Repair Change Monitor

Compare successive observations and report meaningful changes.

Use a separate named state store for each customer, monitored population, and workflow. Run schedules sequentially; overlapping runs against the same store are unsupported.

### Quick start

Paste this input into the Actor, or save it as `input.json` for the API example. Inline records with example.com URLs are fictional demonstration data. Form prefill values are examples, not defaults for empty API requests.

```json
{
  "items": [
    {
      "shopId": "demo-1",
      "technologies": [
        "Mitchell 1"
      ],
      "capabilities": {
        "onlineBooking": false
      },
      "activeJobSignals": 2,
      "cxRiskScore": 55
    }
  ],
  "entityIdField": "shopId",
  "stateStoreName": "auto-repair-change-state",
  "seedWithoutEvents": true
}
```

### Input and output

The Input tab documents every supported option and default. Supply `items` or a compatible `sourceDatasetId`. A run supports at most 10,000 supplied records. Split larger inputs into separate runs.

Returns shared signal envelopes: `entityId`, `entityType`, `signalType`, `severity`, `confidence`, `observedAt`, `sourceUrl`, `evidence`, and Actor-specific `payload`. Compatible envelopes are unwrapped on input; payload fields must still match this Actor’s expected input. A common envelope does not join or enrich separate observations automatically.

Confidence is a heuristic evidence/completeness indicator, not a calibrated probability. Inspect evidence and missing inputs before acting. Dataset exports support JSON and CSV; nested fields are available through the dataset API.

### Pricing and spending limits

Pay per event, with platform usage included. The Apify Store pricing panel shows the current prices.

- **$0.005 per monitored entity**. One complete entity observation compared with saved state, including comparisons that find no change. Incomplete scans are excluded.
- **Startup: $0.005 per GB of allocated memory**, with a minimum of one startup event. The default memory allocation is 1 GB or less.

Diagnostics and included extra signals have no output-event charge; the startup charge still applies. Set the maximum run cost to control spending. If the remaining budget cannot cover the next event, the Actor stops and returns the results already completed. Check the run summary before assuming the entire input was processed. Fees from a separate upstream scraper are not included.

### Errors and repeat runs

Malformed or empty required input fails with an actionable error. Unsupported or insufficient records can produce free diagnostic signals or rejection counts in `OUTPUT`. Check the run status, summary, diagnostics, and billing record together; zero results does not establish that no opportunities or problems exist.

Use the same `stateStoreName` for sequential observations of the same population. Use a different name for independent workflows. Do not overlap runs sharing a state store. Only delivered listing/lot results advance their reporting snapshot; a budget cutoff defers remaining work. Repeated or interrupted runs can still produce duplicate outputs because dataset writes, charging and state updates are separate operations; deduplicate downstream by entity, signal type and observation time.

### Run it from the API

Start asynchronously to avoid request timeouts on larger inputs. Use the returned run ID to wait for completion, then download its dataset.

```bash
curl --request POST 'https://api.apify.com/v2/acts/repairiq~auto-repair-change-monitor/runs' \
  --header "Authorization: Bearer $APIFY_TOKEN" \
  --header 'Content-Type: application/json' \
  --data-binary @input.json
```

```javascript
import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const input = JSON.parse(await (await import('node:fs/promises')).readFile('input.json', 'utf8'));
const run = await client.actor('repairiq/auto-repair-change-monitor').call(input);
if (run.status !== 'SUCCEEDED') throw new Error('Run failed; inspect its log before using partial results.');
const dataset = client.dataset(run.defaultDatasetId);
for (let offset = 0; ; ) {
    const { items } = await dataset.listItems({ offset, limit: 1000 });
    for (const item of items) console.log(item);
    if (items.length < 1000) break;
    offset += items.length;
}
```

### Limitations and support

Use a separate named state store for each customer, monitored population, and workflow. Run schedules sequentially; overlapping runs against the same store are unsupported.

Use data you have permission to process, and respect source restrictions. No affiliation with the named software vendors, marketplaces, or agencies is implied. Report reproducible problems through the Actor Issues tab with a run ID and a minimal input; omit credentials and private customer data.

### Local development

Requires Node.js 22 or newer. Run `npm ci`, `npm run build`, and `npm test` from this Actor directory. Put local input in `storage/key_value_stores/default/INPUT.json`, then run `npm start`. The repository root’s `npm run verify` also checks schemas, shared copies and real entry-point smoke scenarios.

# Actor input Schema

## `items` (type: `array`):

Inline current shop records. Leave the sample in place to see the output shape.

## `sourceDatasetId` (type: `string`):

Optional Apify dataset containing current shop records.

## `entityIdField` (type: `string`):

Field or dotted path used as the stable shop identifier. Suite datasets carry `entityId`; falls back to shopId, website, then shopName.

## `trackedFields` (type: `array`):

Fields or dotted paths to compare between observations.

## `stateStoreName` (type: `string`):

Named key-value store that persists snapshots across scheduled runs.

## `seedWithoutEvents` (type: `boolean`):

On first observation, save state without emitting first-seen events.

## `includeUnchanged` (type: `boolean`):

Write an unchanged result when no fields changed. Useful for audit trails and for confirming a scheduled run actually checked every entity.

## Actor input object example

```json
{
  "items": [
    {
      "entityId": "demo-shop-1",
      "shopName": "Demo Auto Service",
      "website": "https://demo-auto-service.example",
      "technologies": [
        "Tekmetric",
        "Podium"
      ],
      "capabilities": {
        "onlineBooking": true,
        "financing": false
      },
      "averageRating": 4.3
    }
  ],
  "entityIdField": "entityId",
  "trackedFields": [
    "technologies",
    "capabilities",
    "activeJobSignals",
    "capacityPressureScore",
    "averageRating",
    "cxRiskScore",
    "website",
    "locations"
  ],
  "stateStoreName": "auto-repair-change-state",
  "seedWithoutEvents": true,
  "includeUnchanged": true
}
```

# Actor output Schema

## `results` (type: `string`):

No description

## `summary` (type: `string`):

No description

## `billing` (type: `string`):

Check whether the run stopped at its spending limit.

# 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 = {
    "items": [
        {
            "entityId": "demo-shop-1",
            "shopName": "Demo Auto Service",
            "website": "https://demo-auto-service.example",
            "technologies": [
                "Tekmetric",
                "Podium"
            ],
            "capabilities": {
                "onlineBooking": true,
                "financing": false
            },
            "averageRating": 4.3
        }
    ],
    "seedWithoutEvents": false,
    "includeUnchanged": true
};

// Run the Actor and wait for it to finish
const run = await client.actor("repairiq/auto-repair-change-monitor").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 = {
    "items": [{
            "entityId": "demo-shop-1",
            "shopName": "Demo Auto Service",
            "website": "https://demo-auto-service.example",
            "technologies": [
                "Tekmetric",
                "Podium",
            ],
            "capabilities": {
                "onlineBooking": True,
                "financing": False,
            },
            "averageRating": 4.3,
        }],
    "seedWithoutEvents": False,
    "includeUnchanged": True,
}

# Run the Actor and wait for it to finish
run = client.actor("repairiq/auto-repair-change-monitor").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 '{
  "items": [
    {
      "entityId": "demo-shop-1",
      "shopName": "Demo Auto Service",
      "website": "https://demo-auto-service.example",
      "technologies": [
        "Tekmetric",
        "Podium"
      ],
      "capabilities": {
        "onlineBooking": true,
        "financing": false
      },
      "averageRating": 4.3
    }
  ],
  "seedWithoutEvents": false,
  "includeUnchanged": true
}' |
apify call repairiq/auto-repair-change-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,repairiq/auto-repair-change-monitor"
        }
    }
}

```

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/dGlc3g2vgiAhBY1wJ/builds/b2wa5fk265iNLuNvf/openapi.json