# UK Regulator Case Monitor: CMA, SFO, Ofgem on GOV.UK (`accountable_eel/uk-regulator-case-monitor`) Actor

Track new UK regulator cases, competition inquiries, and enforcement notices from CMA, SFO, and Ofgem published on GOV.UK, with monitoring alerts for new cases.

- **URL**: https://apify.com/accountable_eel/uk-regulator-case-monitor.md
- **Developed by:** [Adriana Voss](https://apify.com/accountable_eel) (community)
- **Categories:** Lead generation, Automation
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $7.50 / 1,000 regulator case returneds

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 Regulator Case Monitor: CMA, SFO, Ofgem on GOV.UK

**Track new UK regulator cases, competition inquiries, and enforcement notices from CMA, SFO, and Ofgem on GOV.UK.**
Monitor UK regulatory authorities including the Competition and Markets Authority (CMA), Serious Fraud Office (SFO), and Office of Gas and Electricity Markets (Ofgem). Turn on monitoring mode and run on a schedule to get only cases and enforcement decisions that are new since your last run, charged per case and free on a quiet day.

Legal compliance teams, competition lawyers, regulatory risk analysts, and corporate intelligence researchers use this actor to track antitrust investigations, merger inquiries, fraud enforcement, and market regulation decisions without manual portal checking.

### How to use

1. **In the Apify Console.** Open the actor page and click **Start** — the `regulators` field is already pre-filled with a working example. Results land in the run's dataset as soon as each item is found.
2. **Via the API.** Call it directly with a POST request — no Console needed once you have an API token:
   ```bash
   curl "https://api.apify.com/v2/acts/accountable_eel~uk-regulator-case-monitor/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
     -X POST \
     -H "Content-Type: application/json" \
     -d '{"regulators":["cma"]}'
   ```
3. **On a schedule.** Save this actor as an Apify **Task** with the input you want, then add a **Schedule** (hourly, daily, weekly) so it runs on its own — no server of your own required.

### Input

```json
{
  "regulators": [
    "cma"
  ]
}
```

Which UK regulators to monitor for new cases, decisions, and regulatory notices. One regulator code per line (cma, sfo, ofgem, fca, ico). Combine with an optional keyword query below. Accepted formats: cma, sfo, ofgem.

One combined search runs per call across the chosen regulators. The keyword filter matches against case titles and descriptions. The search run itself is free; you are only billed per case returned.

### Output

One row per regulatory case or notice:

| query | found | status | searchSummary | caseCount | monitorStatus | truncated | caseId | title | regulator | regulatorName | format | description | caseUrl | publicTimestamp | sourceUrl | isNew | firstSeenAt | notifyErrors | scrapedAt |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| cma | true | OK | <search summary> | <cases returned> | <monitoring status> | <more cases available> | <case id> | <case title> | <regulator> | <regulator name> | <document format> | <case summary> | <case page> | <published on> | <source url> | \<is this case new?> | <first seen on a run> | <notification errors> | 1970-01-01T00:00:00.000Z |

A miss comes back as a row with `"found": false` and is never charged. Missing fields are `null`, never `0` or `""`.

### Pricing

- **Regulator case returned**: $15 per 1,000 cases

Plus a $0.00005 start fee per run. Each event above is billed independently, only when it actually returns data — misses (`found:false`) are never charged.

### Limits

- Data is retrieved from the official GOV.UK Search API.
- Scope covers what GOV.UK publishes: CMA cases are tracked via dedicated case records, while SFO and Ofgem publish enforcement notices, policy papers, and official releases.
- Up to 200 cases per run to keep response times under 60 seconds.

### Example runs

Paste any of these into the Input tab and press Start. All three run keyless and return data with no account required beyond an Apify login.

**Recent CMA competition & merger cases (default prefill):**

```json
{
  "regulators": ["cma"],
  "maxItems": 10
}
```

**Cross-regulator search for merger investigations:**

```json
{
  "regulators": ["cma", "sfo", "ofgem"],
  "query": "merger",
  "maxItems": 15
}
```

**Scheduled daily alert for new antitrust and fraud notices:**

```json
{
  "regulators": ["cma", "sfo"],
  "onlyNewSinceLastRun": true,
  "deltaName": "daily-antitrust-fraud-alerts",
  "maxItems": 20
}
```

### Use it from Clay, n8n, Make, or an AI agent

This actor runs synchronously over plain HTTP — call it directly from a script, a workflow tool, or an AI agent, no Apify Console needed once you have an API token.

```bash
curl "https://api.apify.com/v2/acts/accountable_eel~uk-regulator-case-monitor/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
  -X POST \
  -H "Content-Type: application/json" \
  -d '{"regulators":["cma"]}'
```

**n8n.** Add an HTTP Request node: Method `POST`, URL `https://api.apify.com/v2/acts/accountable_eel~uk-regulator-case-monitor/run-sync-get-dataset-items?token=<YOUR_TOKEN>`, Body Content Type `JSON`, JSON Body `{"regulators":["cma"]}` (swap in an expression from an earlier node for a real value).

**Clay.** Add an "HTTP API" column: Method `POST`, URL `https://api.apify.com/v2/acts/accountable_eel~uk-regulator-case-monitor/run-sync-get-dataset-items?token=<YOUR_TOKEN>`, Body `{"regulators":["{{regulator case}}"]}`, mapping the row's regulator case into the `regulators` array.

**MCP.** In Claude, Cursor, or any MCP client with the Apify MCP server, ask for "UK CMA Cases Tracker and Alerts" — the agent will find and run this actor.

# Actor input Schema

## `regulators` (type: `array`):

Which UK regulators to monitor for new cases, decisions, and regulatory notices. One regulator code per line (cma, sfo, ofgem, fca, ico). Combine with an optional keyword query below. Accepted formats: cma, sfo, ofgem. You're only charged for the ones we actually find — a miss costs nothing.

## `query` (type: `string`):

Optional search term or company name to filter regulator cases (e.g. 'Meta', 'merger', 'energy', 'fraud').

## `sinceDays` (type: `integer`):

Optional. Only return cases and notices published within the last N days. Leave empty to retrieve recent cases.

## `maxItems` (type: `integer`):

Caps how many cases or notices you get (and pay for) in one run. Up to 200.

## `onlyNewSinceLastRun` (type: `boolean`):

On: only new cases and decisions published since your last run are returned and charged for — run this on a schedule as an alert. Off: returns the most recent matching cases every time.

## `deltaName` (type: `string`):

Optional. Name this search's monitoring memory so you can run multiple independent regulator alert schedules on the same account.

## `notifyUrl` (type: `string`):

Optional, needs monitoring on. After cases are billed, each new case is posted here: title, regulator, date, link and summary. Discord/Slack webhook, Telegram bot link, or any HTTP webhook URL.

## `notifyFormat` (type: `string`):

Leave on Detect from URL: discord.com links get Discord embeds, hooks.slack.com gets Slack blocks, api.telegram.org gets Telegram messages, and any other URL gets JSON.

## `maxNotificationsPerRun` (type: `integer`):

Up to 100 alert messages per run.

## `testRun` (type: `boolean`):

Turn this on to test your input on a small sample before running the full list. Turn it off to process everything.

## `onlyFound` (type: `boolean`):

Only keep rows where something was actually found. Misses are always free, whether or not you show them here.

## `includeKeywords` (type: `array`):

Optional. Only keep results that mention at least one of these words (e.g. a job title, a city, a product name). Leave empty to keep everything.

## `excludeKeywords` (type: `array`):

Optional. Drop any result that mentions one of these words. Leave empty to skip nothing.

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

Optional. Stop the run once this many results have been found — useful for a quick, cheap sample. Leave blank for no limit.

## `columns` (type: `array`):

Choose which pieces of information to include in each result row. All are included by default.

## `expandRows` (type: `boolean`):

When on, each case found gets its own row instead of being grouped under its regulator case. You're still only charged once per regulator case, no matter how many rows it produces.

## `maxConcurrency` (type: `integer`):

Parallel requests. Keep conservative — this target has no browser fallback, so getting blocked costs more than slow-and-steady.

## Actor input object example

```json
{
  "regulators": [
    "cma"
  ],
  "query": "",
  "maxItems": 20,
  "onlyNewSinceLastRun": false,
  "deltaName": "",
  "notifyFormat": "auto",
  "maxNotificationsPerRun": 20,
  "testRun": false,
  "onlyFound": false,
  "includeKeywords": [],
  "excludeKeywords": [],
  "columns": [
    "searchSummary",
    "caseCount",
    "monitorStatus",
    "truncated",
    "caseId",
    "title",
    "regulator",
    "regulatorName",
    "format",
    "description",
    "caseUrl",
    "publicTimestamp",
    "sourceUrl",
    "isNew",
    "firstSeenAt",
    "notifyErrors"
  ],
  "expandRows": true,
  "maxConcurrency": 1
}
```

# Actor output Schema

## `results` (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 = {
    "regulators": [
        "cma"
    ],
    "includeKeywords": [],
    "excludeKeywords": []
};

// Run the Actor and wait for it to finish
const run = await client.actor("accountable_eel/uk-regulator-case-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 = {
    "regulators": ["cma"],
    "includeKeywords": [],
    "excludeKeywords": [],
}

# Run the Actor and wait for it to finish
run = client.actor("accountable_eel/uk-regulator-case-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 '{
  "regulators": [
    "cma"
  ],
  "includeKeywords": [],
  "excludeKeywords": []
}' |
apify call accountable_eel/uk-regulator-case-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,accountable_eel/uk-regulator-case-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/jAkyeRvtHhfgVypDX/builds/wTzyAr0S0ldC7xeyb/openapi.json
