# UK Food Business Leads & Hygiene Monitor (`maydit/uk-food-business-leads-monitor`) Actor

Discover UK food businesses from official FSA records and monitor rating changes. Export business addresses, types and inspection dates with FHRS/FHIS distinctions.

- **URL**: https://apify.com/maydit/uk-food-business-leads-monitor.md
- **Developed by:** [Brandt May](https://apify.com/maydit) (community)
- **Categories:** Lead generation
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.60 / 1,000 saved observations

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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

![UK Food Business Leads & Hygiene Monitor — illustrative workflow](https://mayd-it.com/assets/actor-banners/uk-food-business-leads-monitor-e1221cf5d519.png)

## UK Food Business Leads & Hygiene Monitor

Discover UK food businesses from official FSA records and monitor rating changes. Export business addresses, types and inspection dates with FHRS/FHIS distinctions.

Combine business location and type with scheme-aware hygiene evidence and saved changes, without presenting council contact details as business leads.

### Start in under a minute

1. Run the prefilled three-record discovery example. No login or API key is needed.
2. Open the Dataset for source-linked records and RUN_REPORT for coverage and billing limits.
3. Reuse exact source IDs for a stable watchlist. Turn on comparison and keep the same snapshot name and inputs.

### Useful workflows

#### 1. Find food businesses in London

Export three matching premises with business type, rating scheme and public address.

```json
{
  "businessName": "pret",
  "address": "London",
  "maxResults": 3
}
```

#### 2. Watch two existing premises

Track two exact FSA establishment IDs and distinguish changed ratings from source updates.

```json
{
  "establishmentIds": [
    "1006008",
    "902473"
  ],
  "maxResults": 3,
  "comparePrevious": true,
  "snapshotName": "food-premises"
}
```

#### 3. Review one premises record

Read one known official record with its inspection date and scheme-specific rating.

```json
{
  "establishmentIds": [
    "1006008"
  ],
  "maxResults": 1,
  "comparePrevious": false
}
```

### What the output means

`fhrsId` is the source premises identity. `ratingValue` retains the official label. `numericRating` is populated only for numeric FHRS ratings from 0 to 5; FHIS, Awaiting Inspection and exempt labels remain null. Missing coordinates and component scores remain null. `ratingDate` is not an opening date. `newRatingPending` does not expose the future rating. `ratingChanged` compares scheme and official label; `numericRatingChange` is calculated only between numeric FHRS observations. Council email addresses and websites, business phone fields and individual contact enrichment are excluded.

Each saved row includes a stable record ID, source link, observedAt, contentHash, comparisonStatus and changedFields. First comparison records are new. A later observation can be changed or unchanged. onlyChanges=true skips unchanged output and its result charge. All output is evidence to review; no predicted purchases, revenue or accuracy guarantees are made.

### Coverage and saved history

Search reads one source-ordered window of maxResults (1–100). selectedWindowComplete describes this requested window; sourceUniverseComplete separately states whether it happened to include all current matches. A complete three-record window can have sourceUniverseComplete=false. Source ordering is not promised to be newest-first. There is no removal inference: a record absent from a later window is not treated as deleted, closed, cancelled or unfunded. Search window size and filters separate saved history. Explicit IDs take precedence over all discovery filters.

Comparison history advances only after all requested source observations and intended outputs finish without a source error, time limit, result truncation, billing cap or concurrent writer. An undersized maxResults in ID mode produces partial coverage and preserves the prior baseline. Missing IDs are not deletion evidence. One snapshot should run sequentially. New/changed results are observations since your retained baseline, not source change notifications.

### Costs and limits

Price: $0.001 per saved result, plus the $0.00005 Actor Start event. For example, 20 saved records cost $0.02005 in Actor events, plus applicable Apify platform charges. No result fee is emitted for SUMMARY, RUN_REPORT, empty searches or skipped unchanged observations. A row is charged once when saved; a spending cap prevents unaffordable rows and stops history updates.

The default is three records and a 60-second budget; maximum 100 saved records and 120 seconds. Explicit watchlists support up to 20 IDs. Fixed official hosts only, no redirects, no login, no proxies and no access bypass. Requests to FSA are sequential with at least 1.1 seconds between calls. A large or slow watchlist may hit its time budget and be reported partial. HTTP 401/403/429 stop access attempts. Errors remain visible; no fallback records are invented.

### Good fit and limitations

Hospitality suppliers, local market researchers and hygiene compliance teams using public business records to qualify premises and follow official rating changes.

- Public premises and rating data, not new business openings, owner emails or marketing consent.
- FHRS uses 0–5 ratings; Scottish FHIS labels remain text with numericRating=null. They are not interchangeable scales.
- Rating dates are source inspection/rating dates. NewRatingPending is a source flag, not a forecast of the next rating.
- The Actor retrieves a bounded window or small watchlist. For recurring full-council extracts, use the FSA nightly Open Data service.

### Sources and attribution

[FSA API v2](https://api.ratings.food.gov.uk/Help) supplies official public premises data; [best practices](https://api.ratings.food.gov.uk/Help/BestPractices) recommend nightly Open Data for full council downloads. Contains Food Standards Agency data © Crown copyright and database right, licensed under the [Open Government Licence v3.0](https://www.nationalarchives.gov.uk/doc/open-government-licence/version/3/).

### Companion workflows

Each Actor runs separately with its own inputs, authorization and pricing. These instructions do not configure automatic execution.

#### [Companies House Filing Monitor - UK Company Changes](https://apify.com/maydit/companies-house-filing-monitor)

Add official UK legal-entity history after identifying the business that operates a selected premises.

1. Verify the legal entity and company number independently; a premises trading name or postcode alone is not a Companies House identifier.
2. Use the verified company number in the companion workflow and keep the premises FHRS identity separate from the legal entity.

Not every food business is a registered company, and one company may operate several premises. A missing or name-only match must not be treated as closure or misconduct.

#### [Website Contact Enrichment - Emails, Phones & Sources](https://apify.com/maydit/website-contact-enrichment)

Review published website contact details for a manually verified food business domain.

1. Confirm the business’s own public website independently, then configure that domain in the companion input form.
2. Keep the official FSA premises record, website source link and observation dates together for human qualification.

The FSA record does not supply marketing consent, and public contact details do not establish consent or deliverability. This workflow does not discover or verify a domain from a business name automatically.

### Connect and automate

Export JSON or CSV from Apify, save a Task, and schedule only the frequency the source and your workflow need. Existing Tasks can feed a spreadsheet, CRM, webhook or your AI agent. Check SUMMARY before accepting a run as complete. Use source IDs to deduplicate; always retain sourceUrl and dates.

[Browse Mayd It data tools](https://mayd-it.com/data-tools/) · [Workflow guides](https://mayd-it.com/data-tools/workflows/) · [Quality dashboard](https://mayd-it.com/data-tools/quality/)

Need a source field clarified? Open an issue on this Actor with your non-sensitive input and run ID.

# Actor input Schema

## `establishmentIds` (type: `array`):

Optional exact FHRSIDs (up to 20). When supplied, name, address and business type discovery filters are ignored. IDs remain stable watchlist keys.

## `businessName` (type: `string`):

FSA name search. Empty name is allowed with an address; a name match is not contact consent.

## `address` (type: `string`):

FSA address search, such as a city or postcode. Leave empty if using only a business name.

## `businessTypeId` (type: `integer`):

Optional official FSA business type ID. 0 omits the filter; e.g. 1 is Restaurant/Cafe/Canteen. Applies to discovery only.

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

Search selects its first window of this size. Explicit-ID mode reads requested IDs; a smaller output limit makes that watchlist incomplete and prevents history updates.

## `maxRunSeconds` (type: `integer`):

Includes source requests, parsing, billing and history. The platform timeout can end the run earlier.

## `comparePrevious` (type: `boolean`):

Save a baseline only after a complete selected scope and successful output. Run a snapshot sequentially.

## `onlyChanges` (type: `boolean`):

Implies comparison. A repeated unchanged snapshot can correctly return zero records with zero result charges.

## `snapshotName` (type: `string`):

1–80 letters, digits, underscores or hyphens. Filters and selected window also separate history. No removed-record inference.

## Actor input object example

```json
{
  "establishmentIds": [],
  "businessName": "pret",
  "address": "London",
  "businessTypeId": 0,
  "maxResults": 3,
  "maxRunSeconds": 60,
  "comparePrevious": false,
  "onlyChanges": false,
  "snapshotName": "default"
}
```

# Actor output Schema

## `dataset` (type: `string`):

No description

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

No description

## `report` (type: `string`):

No description

# 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 = {
    "businessName": "pret",
    "address": "London",
    "maxResults": 3
};

// Run the Actor and wait for it to finish
const run = await client.actor("maydit/uk-food-business-leads-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 = {
    "businessName": "pret",
    "address": "London",
    "maxResults": 3,
}

# Run the Actor and wait for it to finish
run = client.actor("maydit/uk-food-business-leads-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 '{
  "businessName": "pret",
  "address": "London",
  "maxResults": 3
}' |
apify call maydit/uk-food-business-leads-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,maydit/uk-food-business-leads-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/PO1CIak0j3IbptrAD/builds/0BOGOhIid1d7eVKPt/openapi.json
