# CQC Provider Verification Check (`nexgenwatch/cqc-provider-verification-check`) Actor

Verify UK care providers and locations against the official CQC weekly directory — one present/absent verdict per identifier. Billed per PRESENT verdict; absent, ambiguous, and unavailable outcomes are returned but never billed.

- **URL**: https://apify.com/nexgenwatch/cqc-provider-verification-check.md
- **Developed by:** [NexGen Watch](https://apify.com/nexgenwatch) (community)
- **Categories:** Business
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $33.50 / 1,000 provider checks

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?

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

## CQC Provider Verification Check

A per-identity **verification** against the official CQC weekly directory: submit provider/location identifiers, get one present/absent verdict each. Billed **per PRESENT verdict** — absent, ambiguous, and unavailable outcomes are returned but never charged.

### How it behaves

Door law: the **weekly official CSV only**. The public CQC API returned 403 and is forbidden (comply-on-objection). The latest dated `*_CQC_directory.csv` is discovered from the CQC transparency page, streamed once and indexed by CQC Location ID, Provider ID and location name. Each submitted identity resolves deterministically: a **present** location returns its Location ID, Provider ID, provider name, service types, address, region, local authority, latest-check date and the source-file receipt, and is billed. An identity **absent** from the weekly directory returns an `absent` verdict and is not billed; a name matching more than one location returns an ambiguity (resolve by Location ID) and is not billed. Check-vs-roster twin of the cqc-care-provider-directory.

### What you get

One record per submitted identity with a deterministic `verdict` (present/absent) and, when present, the CQC fields verbatim plus the dated `source_file`. Absent/ambiguous/unavailable are distinguished in `outcome` and are **not** billed. A run with no definitive result fails loud and charges nothing.

### Billing

| Event | FREE | BRONZE | SILVER | GOLD+ |
|---|---|---|---|---|
| `apify-actor-start` (one-time actor start) | $0.02 | $0.02 | $0.02 | $0.02 |
| `provider_check` (per present verdict) | $0.05 | $0.045 | $0.04 | $0.0335 |

Charged once per present verdict. Absent, ambiguous, and service-fault outcomes are emitted but never charged. Start fee $0.02.

### Source

`https://www.cqc.org.uk/about-us/transparency/using-cqc-data`

# Actor input Schema

## `providers` (type: `array`):

CQC Location IDs (e.g. 1-10552899555), Provider IDs, or exact location names to verify against the official CQC weekly directory CSV. A resolved (present) location bills; absent and ambiguous are emitted but never billed.

## Actor input object example

```json
{
  "providers": [
    "1-10552899555",
    "Square Mile Dental Centre",
    "1-00000000000"
  ]
}
```

# 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 = {
    "providers": [
        "1-10552899555",
        "Square Mile Dental Centre",
        "1-00000000000"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("nexgenwatch/cqc-provider-verification-check").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 = { "providers": [
        "1-10552899555",
        "Square Mile Dental Centre",
        "1-00000000000",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("nexgenwatch/cqc-provider-verification-check").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 '{
  "providers": [
    "1-10552899555",
    "Square Mile Dental Centre",
    "1-00000000000"
  ]
}' |
apify call nexgenwatch/cqc-provider-verification-check --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,nexgenwatch/cqc-provider-verification-check"
        }
    }
}
```

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/hH7KFaDdnWglbBcLm/builds/dnlDZGl27U1oE5evq/openapi.json