# Homebrew Formulae / Casks Version Delta Monitor (`collinjreynolds/homebrew-version-delta-monitor`) Actor

Monitors Homebrew formulae and casks for version (and checksum/revision) changes via the official formulae.brew.sh JSON API. Emits only deltas. First run baselines without charging. PPE event: version-delta.

- **URL**: https://apify.com/collinjreynolds/homebrew-version-delta-monitor.md
- **Developed by:** [Collin Reynolds](https://apify.com/collinjreynolds) (community)
- **Categories:** Developer tools, AI
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.00 / 1,000 new homebrew version changes

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

## Homebrew Formulae / Casks Version Delta Monitor

Watch public **Homebrew formulae and casks** for **version / revision / checksum changes** via the official [`formulae.brew.sh`](https://formulae.brew.sh) JSON API. Only **deltas** since the last run are written to the dataset — ideal for Mac IT/admin stacks, Brewfile monitoring, and scheduled agentic changelogs.

**Pricing (pay per event):** **`$0.001` per `version-delta`** (each newly detected formula/cask version change). Actor start is a small platform event (~`$0.00005`). First run baselines quietly (0 dataset items / 0 delta charges) so you are not billed for history.

### Why use this

- **API-only** — official `formulae.brew.sh` JSON (no HTML scraping)
- **Delta-only** — subsequent runs emit only when version/revision/checksum fingerprints change
- **First-run safe** — empty state seeds `LAST_SEEN` with zero PPE delta charges
- **No auth required** for public formulae and casks
- **Schedule-friendly** — pair with an Apify schedule for continuous monitoring
- **Formulae + casks** in one Actor

### Input

| Field | Required | Description |
|-------|----------|-------------|
| `formulae` | no\* | List of Homebrew formula names (`wget`, `git`, `jq`, …) |
| `casks` | no\* | List of Homebrew cask tokens (`visual-studio-code`, `iterm2`, …) |
| `resetState` | no | Clear `LAST_SEEN` and re-baseline (0 emits that run) |

\* At least one of `formulae` / `casks` must be non-empty.

#### Example

```json
{
  "formulae": ["wget", "git", "jq"],
  "casks": ["visual-studio-code", "iterm2"],
  "resetState": false
}
```

### Output

Each dataset item is a version change, for example:

- `kind`, `name`, `tap`, `version`, `revision`, `checksum`, `homepage`, `package_description`, `license`, `api_url`, `fingerprint`, `previous_fingerprint`

### First-run behavior

| Situation | Dataset items | `version-delta` charges |
|-----------|---------------|-------------------------|
| Empty state | **0** | **0** (baseline only) |
| Later runs with unchanged versions | **0** | **0** |
| Later runs with version/rev/checksum change | 1 per changed package | 1 per item |

### Tips

1. Run once to baseline, then attach a **schedule** (e.g. daily).
2. Keep watchlists focused — each package is one HTTP GET.
3. Set a user **max total charge** on the run so costs stay predictable.

### ToS / scope

Uses the public formulae.brew.sh JSON API only. See [AGREEMENT.md](./AGREEMENT.md). Prefer watchlist mode over bulk catalog dumps.

# Actor input Schema

## `formulae` (type: `array`):

List of public Homebrew core formula names to watch (e.g. wget, git, jq).

## `casks` (type: `array`):

List of public Homebrew cask tokens to watch (e.g. visual-studio-code, iterm2).

## `resetState` (type: `boolean`):

If true, ignore and clear the stored LAST\_SEEN fingerprint map before this run (re-baseline; 0 emits that run).

## Actor input object example

```json
{
  "formulae": [
    "wget",
    "git",
    "jq"
  ],
  "casks": [
    "visual-studio-code",
    "iterm2"
  ],
  "resetState": false
}
```

# Actor output Schema

## `overview` (type: `string`):

Dataset items for newly detected version/checksum/revision changes. First run baselines with 0 items.

# 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 = {
    "formulae": [
        "wget",
        "git",
        "jq"
    ],
    "casks": [
        "visual-studio-code",
        "iterm2"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("collinjreynolds/homebrew-version-delta-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 = {
    "formulae": [
        "wget",
        "git",
        "jq",
    ],
    "casks": [
        "visual-studio-code",
        "iterm2",
    ],
}

# Run the Actor and wait for it to finish
run = client.actor("collinjreynolds/homebrew-version-delta-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 '{
  "formulae": [
    "wget",
    "git",
    "jq"
  ],
  "casks": [
    "visual-studio-code",
    "iterm2"
  ]
}' |
apify call collinjreynolds/homebrew-version-delta-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,collinjreynolds/homebrew-version-delta-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/4EjuIvAZbM1BIrhnG/builds/WAuMMM4aanA2iq039/openapi.json