CQC Provider Verification Check avatar

CQC Provider Verification Check

Pricing

from $33.50 / 1,000 provider checks

Go to Apify Store
CQC Provider Verification Check

CQC Provider Verification Check

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.

Pricing

from $33.50 / 1,000 provider checks

Rating

0.0

(0)

Developer

NexGen Watch

NexGen Watch

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

4 days ago

Last modified

Share

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

Output is one cqc_provider_verification row per result; billing is pay-per-event, the value event being one provider check (a $0.02 start fee per run, then $0.05 per provider check). Source: www.cqc.org.uk.

No login, no API key and no CAPTCHA solving are involved: the source is read logged-out with an identified contact User-Agent.

📊 Sample Output

CQC Provider Verification Check sample output — a table of real provider check rows (query_mode, verdict, location_id, provider_id) from run rZzIZo8Bxo8x8Fbcf on build 0.1.4

Real rows from run rZzIZo8Bxo8x8Fbcf on build 0.1.4 (2026-09-17), the same input as the Quick start below — every value is as the source published it (emails masked, long text shortened):

query_modeverdictlocation_idprovider_idsource_fileinput
idpresent1-105528995551-1000691212916_september_2026_CQC_directory.csv1-10552899555
namepresent1-105528995551-1000691212916_september_2026_CQC_directory.csvSquare Mile Dental Centre
idabsent16_september_2026_CQC_directory.csv1-00000000000

The run finished with the status message: NORMAL: 2 billable answer(s), 1 definitive non-billable (not-found/ambiguous), 0 unavailable, 0 unparseable of 3 | provider_check billable=2 | provider_check charged=2

✅ What you get

Each row is flat JSON with these fields (from the dataset schema and the sample run; a field the source does not publish for a given row is null):

  • query_mode (string/null) — e.g. id
  • verdict (string/null) — e.g. present
  • location_id (string/null) — e.g. 1-10552899555
  • provider_id (string/null) — e.g. 1-10006912129
  • location_name (string/null) — e.g. Square Mile Dental Centre
  • provider_name (string/null) — e.g. Square Mile Dental Centre Limited
  • service_types (string/null) — e.g. Dentist
  • address (string/null) — e.g. 7-9 White Kennet Street,London
  • postcode (string/null) — e.g. E1 7BS
  • region (string/null) — e.g. London
  • local_authority (string/null) — e.g. City of London
  • latest_check_date (string/null) — e.g. 09/Jan/2018 - 00:00
  • location_url (string/null) — e.g. https://www.cqc.org.uk/location/1-10552899555
  • source_file (string/null) — e.g. 16_september_2026_CQC_directory.csv
  • record_type (string) — e.g. cqc_provider_verification
  • input (string/null) — e.g. 1-10552899555
  • source (string/null) — e.g. https://www.cqc.org.uk/about-us/transparency/using-cqc-data
  • outcome (string/null) — e.g. answer
  • outcome_reason (string/null) — e.g. no CQC location/provider with ID 1-00000000000

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.

⚙️ Sample inputs

1. Quick start — the Store example (this is what the sample above came from)

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

The sample run charged exactly: 1 × $0.02 apify-actor-start + 2 × $0.05 provider_check = $0.12 on the Free tier — every delivered row was billed.

2. A smaller, narrowed run

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

A bounded run for checking the field shape before scheduling.

3. A full-size run

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

The same input run on a schedule; each run is billed only for what it delivers.

🧾 JSON sample record

One real record from run rZzIZo8Bxo8x8Fbcf, exactly as it lands in the dataset (emails masked, long text shortened):

{
"query_mode": "id",
"verdict": "present",
"location_id": "1-10552899555",
"provider_id": "1-10006912129",
"location_name": "Square Mile Dental Centre",
"provider_name": "Square Mile Dental Centre Limited",
"service_types": "Dentist",
"address": "7-9 White Kennet Street,London",
"postcode": "E1 7BS",
"region": "London",
"local_authority": "City of London",
"latest_check_date": "09/Jan/2018 - 00:00",
"location_url": "https://www.cqc.org.uk/location/1-10552899555",
"source_file": "16_september_2026_CQC_directory.csv",
"record_type": "cqc_provider_verification",
"input": "1-10552899555",
"source": "https://www.cqc.org.uk/about-us/transparency/using-cqc-data",
"outcome": "answer",
"outcome_reason": null
}

🔧 How it works

Transport. Plain HTTPS from the Apify platform, no proxy. Every request carries an identified contact User-Agent.

Charging. Each provider check is charged at the moment it is pushed (provider_check); a row that fails to charge is not delivered, so the dataset count always equals the charged count.

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.

Billing

EventFREEBRONZESILVERGOLD+
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

What is not done. No login, no cookie or CAPTCHA bypass, no private or personal-account data, no browser automation.

💰 Pricing example

EventFreeBronzeSilverGold
Actor Start (apify-actor-start)$0.02$0.02$0.02$0.02
Provider Check (provider_check)$0.05$0.04$0.04$0.03

Worked at the live Free-tier price:

  • 3 provider checks: $0.02 start + 3 × $0.05 = $0.17
  • 25 provider checks: $0.02 start + 25 × $0.05 = $1.27
  • 100 provider checks: $0.02 start + 100 × $0.05 = $5.02

A run that delivers zero rows charges the $0.02 start fee only. A BLOCKED run (source refused) fails loud and charges no value event. The start fee is charged once per GB of run memory; the default run memory is 1024 MB.

Yield on the sample run: NORMAL: 2 billable answer(s), 1 definitive non-billable (not-found/ambiguous), 0 unavailable, 0 unparseable of 3 | provider_check billable=2 | provider_check charged=2.

This actor reads public, logged-out pages and feeds published by www.cqc.org.uk. It collects only what the source publishes to any visitor, identifies itself with a contact User-Agent, and does not access accounts, private data or anything behind authentication. Use the output in line with the source's terms and your local law; the intended use is B2B research and monitoring.

❓ FAQ

Q: Do I need an API key or a login?
A: No. The source (www.cqc.org.uk) is read logged-out; the input schema has no key field and the actor carries no secrets.

Q: Why did my run return 0 rows?
A: Read the run's status message. GENUINE_EMPTY means the source was read and had nothing in scope for your input; BLOCKED means the source refused and the run failed without billing a value event — retry later or narrow the input. A zero-row run bills the start fee only.

Q: How fresh is the data?
A: Every run reads the source live at run time; nothing is cached between runs. Put it on a schedule for a continuous feed.

Q: What formats can I export?
A: The dataset downloads as JSON, CSV, Excel, XML or RSS from the run's Dataset tab or the Apify API, and any run can push to a webhook or integration.

Q: How is this different from the other company registry checks actors?
A: Same output shape and billing model; this one covers www.cqc.org.uk. The siblings under Related Actors cover the other sources or slices — run several on one schedule for a combined feed.

Q: Are there rate limits?
A: The actor paces itself against the source; there is no per-buyer limit beyond your Apify plan's concurrency.

🆘 Troubleshooting

  • Run FAILED with BLOCKED → the source refused the request or changed its page shape → nothing was billed beyond the start fee; retry after a while, and if it persists open an Issue with the run id.
  • Fewer rows than expected → the source had fewer items in scope → widen the input.
  • Input validation error on start → a field is outside the schema's allowed values → start from the Quick start block and change one field at a time.
  • Run TIMED-OUT → a very wide request on a slow day → raise the run timeout in Run options or narrow the input; what was delivered before the timeout is still in the dataset.
  • Connecticut Business Status Check — Check Connecticut business identities against the official state registry (data.ct.gov) — one official answer per identifier: registry status, regist…
  • EU EORI Customs Registration Check — Validates EORI numbers against the European Commission's official EORI service — one definitive registered / not-registered answer per identifier wit…
  • EU VAT Validator — VIES per-answer check — Validate EU VAT numbers against the official EU VIES service — one verdict per number with the registered name and date. No API key; pay per complete…
  • Finland PRH Business Filing Lookup — Look up Finnish companies by Business ID on the official PRH open-data trade register — name, company form, trade-register status, registration date,…
  • 🏢 About NexGenData — NexGen Watch is NexGenData's fleet of 256 public monitoring and lookup actors built on official sources, pay-per-result. Browse the catalog at apify.com/nexgenwatch.

⭐ Found this useful?

If this actor saved you a manual check, a quick review on the Apify Store helps other teams find it. Feature request or a source that changed? Open it from the Issues tab — every one is read.