# CMA Merger & Competition Case Change Signals (`starshaped_bullsnake/cma-merger-competition-case-change-signals`) Actor

Track important official CMA merger, competition, and consumer-enforcement case changes.

- **URL**: https://apify.com/starshaped\_bullsnake/cma-merger-competition-case-change-signals.md
- **Developed by:** [Starshape Tools](https://apify.com/starshaped_bullsnake) (community)
- **Categories:** Business
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $50.00 / 1,000 cma case change signals

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?

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

## CMA Merger & Competition Case Change Signals

Tracks important state changes in official Competition and Markets Authority case records for regulatory-intelligence workflows. It is designed for corporate-development, competition, legal-operations, and market-intelligence teams; it is not a case-finder scrape or outcome predictor.

### Official source and licence

Only [CMA cases and projects on GOV.UK](https://www.gov.uk/cma-cases), its [official Atom feed](https://www.gov.uk/cma-cases.atom), and linked official case pages are used. GOV.UK content is available under the [Open Government Licence v3.0](https://www.nationalarchives.gov.uk/doc/open-government-licence/version/3/) unless otherwise stated. Attribution: Contains public sector information licensed under the Open Government Licence v3.0.

The canonical GOV.UK case URL is the stable key. Titles alone are never matched. The full normalized snapshot includes title, case type/state, opened/closed/updated dates, parties, phase, outcome, remedy text, publication links and official URL.

### Signals

Supported: `NEW_CASE`, `NEW_MERGER_INQUIRY`, `CASE_UPDATED`, `CASE_STATUS_CHANGED`, `PHASE_2_REFERRED`, `MERGER_CLEARED`, `CASE_CLOSED`, `CLEARED_WITH_REMEDIES`, `MERGER_PROHIBITED`, `NEW_CONSUMER_ENFORCEMENT_CASE`, `NEW_COMPETITION_ENFORCEMENT_CASE`, `REMEDY_UPDATED`, and `DECISION_PUBLISHED`. Regulatory meanings are emitted only from explicit official case type, state, outcome, remedy, or publication wording. Null transitions do not create regulatory-state signals.

The first live run follows all official listing pages and case pages to create a full baseline with zero signals. Later runs use the official Atom feed to identify new/updated candidates, fetch those case pages, and merge them into the complete snapshot. A daily schedule is recommended.

```json
{ "mode": "live", "caseTypes": ["Mergers"], "signalTypes": ["PHASE_2_REFERRED", "MERGER_CLEARED"], "maxItems": 1000 }
```

```json
{ "signalType": "CASE_STATUS_CHANGED", "title": "Sample case", "caseType": "Mergers", "status": "Closed", "previousValue": "Open", "currentValue": "Closed", "signalSummary": "CASE STATUS CHANGED: Sample case", "sourceUrl": "https://www.gov.uk/cma-cases/sample-case" }
```

Filters and `maxItems` control Dataset output only. Sample mode runs deterministic fixtures through production normalization, diff, and filtering before any network or production KVS access and reports `snapshotUpdated: false`. The compressed KVS snapshot remains complete; every Dataset item is one signal. Parser fixtures, critical-field checks, pagination/feed checks, and count-collapse guards fail explicitly and retain the prior snapshot when source structure becomes unsafe.

Limitations: the initial baseline is network/compute intensive; subsequent feed processing depends on GOV.UK feed coverage. Publication wording varies, so only explicit supported phrases are classified. This Actor is not complete regulatory due diligence or competition-law advice.

# Actor input Schema

## `mode` (type: `string`):

Live official comparison or isolated sample.

## `signalTypes` (type: `array`):

Optional signal-type filter.

## `caseTypes` (type: `array`):

Optional exact official case-type filter.

## `statuses` (type: `array`):

Optional exact case-state filter.

## `keywords` (type: `array`):

Optional title, party, or outcome keywords.

## `baselineOnly` (type: `boolean`):

Refresh baseline without signals.

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

Caps Dataset output only; never truncates the snapshot.

## Actor input object example

```json
{
  "mode": "live",
  "baselineOnly": false,
  "maxItems": 1000
}
```

# Actor output Schema

## `OUTPUT` (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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("starshaped_bullsnake/cma-merger-competition-case-change-signals").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 = {}

# Run the Actor and wait for it to finish
run = client.actor("starshaped_bullsnake/cma-merger-competition-case-change-signals").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 '{}' |
apify call starshaped_bullsnake/cma-merger-competition-case-change-signals --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,starshaped_bullsnake/cma-merger-competition-case-change-signals"
        }
    }
}
```

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/38I2gE8euYz6cvtCS/builds/R7Uqy9RUkuDle4s8F/openapi.json