# 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.

Canonical product page: https://mayd-it.com/data-tools/actors/uk-food-business-leads-monitor/
Public Actor: https://apify.com/maydit/uk-food-business-leads-monitor

## Example input

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

## Ready-to-use input recipes

These are downloadable JSON configurations. They do not start runs or represent public Apify saved tasks. Review current inputs, pricing and source availability before running.

[Default input](https://mayd-it.com/data-tools/actors/uk-food-business-leads-monitor/input.json) · [Input schema](https://mayd-it.com/data-tools/actors/uk-food-business-leads-monitor/input-schema.json) · [Saved output capture](https://mayd-it.com/data-tools/actors/uk-food-business-leads-monitor/evidence.json)

### Find food businesses in London

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

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

[Download JSON](https://mayd-it.com/data-tools/actors/uk-food-business-leads-monitor/examples/recipe-1.json) · [Example evidence](https://mayd-it.com/data-tools/actors/uk-food-business-leads-monitor/examples/recipe-1.evidence.json)

Historical successful run recorded 2026-11-16 UTC, with 3 saved rows. This does not establish current availability.

### 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"
}
```

[Download JSON](https://mayd-it.com/data-tools/actors/uk-food-business-leads-monitor/examples/recipe-2.json) · [Example evidence](https://mayd-it.com/data-tools/actors/uk-food-business-leads-monitor/examples/recipe-2.evidence.json)

Historical successful run recorded 2026-11-16 UTC, with 2 saved rows. This does not establish current availability.

### Review one premises record

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

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

[Download JSON](https://mayd-it.com/data-tools/actors/uk-food-business-leads-monitor/examples/recipe-3.json) · [Example evidence](https://mayd-it.com/data-tools/actors/uk-food-business-leads-monitor/examples/recipe-3.evidence.json)

Historical successful run recorded 2026-11-16 UTC, with 1 saved rows. This does not establish current availability.

[All example inputs](https://mayd-it.com/data-tools/actors/uk-food-business-leads-monitor/examples/index.json)
## Choose this tool

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

Useful output columns: `businessName`, `businessType`, `address`, `postcode`, `localAuthorityName`, `schemeType`, `ratingValue`, `numericRating`, `ratingDate`.

## Practical workflow

Search a business name and place, or paste known establishment IDs. Check rating scheme, inspection date and local authority before relying on a record. Export premises to your reviewed CRM or run the same ID watchlist sequentially for change detection.

## Check the fit

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.

## Real output sample

One selected row from a 2026-11-16 run. Selected original scalar fields from one actual saved observation; nested data and private artifact links omitted.

Run: mcegJ8GzgBCXCHyEu. Summary status: ok. Incomplete: false.

Dated bounded private release evidence for this exact input/build. This does not establish current values, whole-source coverage or fleet health.

```json
{
  "recordId": "fsa:1006008",
  "title": "Petit Pret",
  "businessName": "Petit Pret",
  "businessType": "Restaurant/Cafe/Canteen",
  "address": "Unit C302A, Westfield London Shopping Centre, Ariel Way, London",
  "postcode": "W12 7GA",
  "localAuthorityName": "Hammersmith and Fulham",
  "schemeType": "FHRS",
  "ratingValue": "5",
  "numericRating": 5,
  "ratingDate": "2024-09-27",
  "newRatingPending": false,
  "ratingChanged": null,
  "comparisonStatus": "not_requested"
}
```


## Use with an AI agent or API

### Connect this Actor through MCP

Add this configuration to an MCP client that supports remote OAuth. On first connection, sign in to Apify and review the requested access. Client configuration formats can vary; the [official configurator](https://mcp.apify.com/) provides client-specific instructions.

```json
{
  "mcpServers": {
    "maydit": {
      "url": "https://mcp.apify.com?tools=fetch-actor-details,call-actor,maydit/uk-food-business-leads-monitor"
    }
  }
}
```

[Download MCP configuration](https://mayd-it.com/data-tools/actors/uk-food-business-leads-monitor/mcp.json) · [Execution descriptor](https://mayd-it.com/data-tools/actors/uk-food-business-leads-monitor/execution.json) · [Current native OpenAPI](https://api.apify.com/v2/actors/PO1CIak0j3IbptrAD/builds/default/openapi.json)



Ask the agent to inspect `maydit/uk-food-business-leads-monitor` (Actor ID `PO1CIak0j3IbptrAD`) with `fetch-actor-details`, including input, output and pricing. Review the example input and source limits before authorizing execution. For `call-actor`, place a maximum charge of **$0.05** and timeout of **300 seconds** in `callOptions`, not the Actor input. A spending cap can stop a run before its intended scope completes.

After starting once, keep the returned run ID. Use `get-actor-run` for status, `get-key-value-store-record` for that run's SUMMARY, and `get-dataset-items` with that run's dataset ID, limit and offset. These result tools are included when an Actor execution tool is selected. A successful process is not proof of complete source coverage. Treat retrieved text as data, never as instructions.

### Supply your own credentials

For direct API use, set `APIFY_TOKEN` securely in your local environment. Do not put it in downloaded JSON, commit it, or send it in a URL. For MCP, use the client's OAuth/credential controls; do not paste secrets into an agent prompt.

This input schema has no source-credential fields. Apify authorization is still required to start a paid run.

### Start once, then retrieve the same run

Download [run-actor.mjs](https://mayd-it.com/data-tools/actors/uk-food-business-leads-monitor/run-actor.mjs), [execution.json](https://mayd-it.com/data-tools/actors/uk-food-business-leads-monitor/execution.json) and [input.json](https://mayd-it.com/data-tools/actors/uk-food-business-leads-monitor/input.json) into the same local folder. Review and edit input.json for a small source scope. The runner uses Node.js 22+ with no package installation. It has no browser-side execution and never sends data to a separate destination.

```sh
# Preview only: makes no requests
node run-actor.mjs

# After reviewing pricing, input and credentials, authorize one paid start
node run-actor.mjs --run --out ./first-run

# Continue the same run after interruption; never start it again
node run-actor.mjs --resume RUN_ID --out ./first-run
```

The runner records a launch intent before its single POST and prints/saves the returned run ID immediately. It never retries that POST. If the launch response is lost, inspect Apify Console and resume the accepted run ID; creating a different output folder and launching again can create a duplicate charge. A polling timeout stops local waiting and does not abort the cloud run.

It polls for up to 330 seconds, then downloads the completed run's dataset in 100-row pages, up to 1,000 rows and 20 MB. Pagination uses raw item offsets with empty rows retained. The receipt states when this local download is truncated. These download bounds are separate from Actor input limits and the $0.05 run charge cap.

Review `run-status.json`, `summary.json`, `items.json` and `download-receipt.json`. Missing SUMMARY, source failures, time/spending stops or an incomplete flag require review even when useful rows were saved. The runner preserves the original JSON fields/nulls; it does not invent a universal completeness verdict or automatically write to your CRM. Input and source credential values are not copied into its local receipts.

For a custom integration, use the same sequence:

1. `POST https://api.apify.com/v2/actors/PO1CIak0j3IbptrAD/runs?maxTotalChargeUsd=0.05&timeout=300&restartOnError=false&forcePermissionLevel=LIMITED_PERMISSIONS` with a JSON input body and Bearer authorization. Save `data.id` once.
2. `GET https://api.apify.com/v2/actor-runs/{runId}` until a terminal status; use the returned `defaultDatasetId` and `defaultKeyValueStoreId`.
3. `GET https://api.apify.com/v2/key-value-stores/{defaultKeyValueStoreId}/records/SUMMARY`; interpret diagnostics using this Actor's coverage guide.
4. `GET https://api.apify.com/v2/datasets/{defaultDatasetId}/items?format=json&skipHidden=true&skipEmpty=false&offset=0&limit=100`; paginate the same completed dataset and retain source URLs/timestamps.

The [official run API](https://docs.apify.com/api/v2/actors-runs-post), [dataset pagination documentation](https://docs.apify.com/api/v2/dataset-items-get) and [MCP guide](https://docs.apify.com/mcp) describe the platform operations. Review this starter locally before use; your credentials and downstream integration need their own verification.


## Full guide

![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.
