Childcare Provider Leads — Daycare Contact Lists + Compliance avatar

Childcare Provider Leads — Daycare Contact Lists + Compliance

Pricing

from $6.60 / 1,000 results

Go to Apify Store
Childcare Provider Leads — Daycare Contact Lists + Compliance

Childcare Provider Leads — Daycare Contact Lists + Compliance

Licensed childcare provider lead lists from official state licensing data in 9 states: TX, NY, CA, PA, MA, CT, WA, DE, VT. Phone, email and named contacts where published; filter by county, type, capacity, ages. Violation history where the state publishes it. Delta mode flags new programs.

Pricing

from $6.60 / 1,000 results

Rating

0.0

(0)

Developer

Kyle Maloney

Kyle Maloney

Maintained by Community

Actor stats

0

Bookmarked

4

Total users

1

Monthly active users

4 days ago

Last modified

Share

Childcare Provider Leads - Daycare Contact Lists + Compliance

A licensed childcare provider lead list with a compliance record attached, built on official state licensing open data for nine states: Texas, New York (incl. NYC), California, Pennsylvania, Massachusetts, Connecticut, Washington, Delaware and Vermont. One row per licensed program: name, physical and mailing address, phone, email (where the state publishes it), the named director / contact, licensed capacity, ages served, hours, quality rating, and the program's published inspection / deficiency / enforcement history where the state publishes one.

Keyless state open-data sources (Socrata portals and the California CDSS ArcGIS layer). No login, no API key, no anti-bot games.

Scope and cost — read this first

state is required. There is no default and no hidden nationwide mode, so a run always answers about the states you actually named. To pull several states in one run, add them to the optional states list:

{ "state": "TX" }
{ "state": "NY", "states": ["PA", "VT"], "maxResults": 300 }

With several states, maxResults is shared fairly (a state that runs out of matches hands its unused share to the others). A state that cannot answer — its source is down, fails a live check, or cannot apply a filter you set — is skipped and disclosed on every row (run_states_failed, run_states_failed_reason, run_complete: false); the run only fails, and bills nothing, when none of the requested states can answer.

A call with no state is rejected before the run starts — HTTP 400, no compute, no rows, nothing billed. That is deliberate: this field used to carry a schema default, and because Apify injects defaults server-side, anyone who omitted it was quietly answered about one arbitrary state and charged for it on a run that reported SUCCESS. A rejected call is cheaper than a wrong answer.

What a run costs. Billing is pay-per-result at $12.00 per 1,000 rows (about $1.20 per 100 rows), and paid Apify plans get a graduated discount of 20-70% off that. Only rows actually written to the dataset are billed — a run that fails a pre-flight check emits nothing and bills nothing. Set maxResults to put a hard ceiling on any single run.

How many rows to expect. Scope drives the bill, so size it deliberately: a Texas county search returns a few hundred licensed operations. Run one state per run and combine the datasets rather than guessing at a wide scope.

Contact-field population - measured, not assumed

Measured live on 2026-08-01 across the entire active Texas roster (n = 14,937):

FieldPopulated
phone99.6%
address / city / county / zip99.1%
mailing_address99.1%
administrator_director_name69.1%
email56.6%
website37.8%
capacity99.0%

Email is on a little over half the roster. That is the honest number and it is why every row also carries has_phone, has_email, has_named_contact and a contact_channels array - so you can filter to genuinely reachable leads before you export, rather than discovering the gap afterwards. Texas publishes no email for the other 43.4%; no actor can invent one.

Coverage

Every source was measured live on 2026-09-25. On each run, the actor re-checks every source it touches before emitting a billable row. The checks cover required columns, the row-count band, a negative control, closed vocabularies and freshness.

StateSource (keyless)FeedsFreshness (measured)Notes
TXHHSC data.texas.gov bc5r-88dy + non-compliance tqgd-mf4xRoster; phone 99.6%, email 56.6%; director; lifetime and 2-year deficiencies; enforcement flagsRefreshed dailyUnchanged from v1.1
NY (outside NYC)OCFS data.ny.gov cb42-qumz (16,704 programs)Roster; phone 84.3%; capacity by age group; facility statusRefreshed 2026-09-25; newest licence 2026-09-24The state withholds address and phone for about 2,400-2,600 programs (address_withheld_by_state, phone_withheld_by_state). No email. No violations published
NY (NYC)NYC DOHMH data.cityofnewyork.us gy3q-4tzp (2,750 programs)Roster; phone 100%; permit statusRefreshed 2026-09-25OCFS lists 0 day-care centers in NYC because the city licenses them. Queried only when no county or an NYC county is set
CACDSS ArcGIS CDSS_CCL_Facilities layer 0, child-care rows (13,334 of 36,944), + CCLD Transparency API detailRoster; phone; capacity; lat/long. With includeCompliance: inspection, citation and complaint counts per facilityLayer edited 2026-09-25Licensed centers only. CA does not publish family child-care homes as open data; the old CKAN FCCH files stop at 2025-05. source_status_code is published as a raw code, not decoded
PAdata.pa.gov ajn5-kaxt (7,471 providers)Roster; phone 96.0%; email 92.7%; named responsible person 87.7%; STAR quality levelRefreshed 2026-09-25184 providers carry a future licence-issue date as published. No violations published; negative_sanctions is carried where present
CTdata.ct.gov h8mr-dn95 (3,769 active licences) + inspections 6rnk-h6iy (99,726) + violations ccit-2ev8 (354,493)Roster; phone 99.6%. With includeCompliance: 2-year inspection and citation countsRefreshed 2026-09-25No county column, so a county filter fails this leg. Includes youth camps (see operation_type)
DEdata.delaware.gov iuzd-3dbt (1,242 providers) + compliance wb83-pkcv (14,320)Roster; phone 99.8%. With includeCompliance: 2-year citation countsRefreshed 2026-09-25; compliance covers 2021-09-27 to 2026-09-21
VTdata.vermont.gov ctdw-tmfz (1,048 programs)Roster; phone 100%; email 100%; STARS rating; capacity by age; reported vacanciesRefreshed 2026-09-11No violations published
WAdata.wa.gov was8-3ni8 (3,167 rows, 2,517 distinct)Roster; email 99.7%; named contact 99.8%Refreshed 2026-09-07; newest licence start 2026-08-28Centers and school-age programs only; phone on 7.8%. Duplicate source rows are collapsed (see source_duplicate_rows). No violations published
MAeducationtocareer.data.mass.gov iyks-y3g6 (9,217 programs)Roster; phone 100%; capacityRefreshed 2026-09-21No county column. No violations published

Some states publish no violation data. For those, violations_status reads not_published and every violation count is null, never 0. compliance_basis gives the reason on each row.

States checked and not added (evidence, 2026-09-25):

StateWhy not
COdata.colorado.gov a9rr-k8mu carries no phone, email or contact, so it is not a lead list
NJcru5-4rmm was last updated 2019-08-09
AZThe ADHS layer's RUN_DATE is 2025-02-03, so it is stale
NEIt has a single roster date, 2025-10-15, and has not been refreshed since
MN, MI, WIThe public layers carry no phone, no update date, or neither. MI's county codes are also wrong
OK, VA, TNOnly third-party or unknown-owner mirrors exist. VA's own site is behind reCAPTCHA
FL, GA, OR, KYSearch UIs only, with no bulk or paged API. KY returned 503
NC, ILBehind a reCAPTCHA or Cloudflare challenge
OHThe export requires an emailed request
UTThe endpoint was unreachable

What changed in v1.2 (2026-09-25)

  • Eight more states (see Coverage). Texas behaviour is unchanged: the same input returns the same rows with the same values.
  • states: an optional list for multi-state runs. maxResults is shared fairly across the states. A state that cannot answer is skipped and disclosed, never silently dropped.
  • 34 new fields, all nullable and appended after the v1.1 fields. None were removed or renamed.
  • Failure messages lead with the billing outcome. A failed run's status message now starts with "Nothing was emitted and nothing was billed.", so an API or MCP caller sees it immediately.
  • Unapplied filters fail loudly. A filter that a state's data cannot apply now fails that state's leg instead of being silently ignored. For example, county fails in Connecticut and Massachusetts.

What changed in v1.1 (2026-08-01)

high_risk_flag used to say false on operations that were never checked. In v1.0 the flag was initialised false and left there whenever includeCompliance was off or the non-compliance join threw - a billable row asserting that a childcare operation is not high-risk on a check that never ran. It is now null unless the join actually answered for that specific operation, and violations_status says which.

The compliance data was there all along and was being thrown away. The HHSC roster record publishes its own deficiency counts by risk level (deficiency_high, deficiency_medium_high, deficiency_medium, deficiency_medium_low, deficiency_low), plus total_inspections, total_assessments, total_reports, total_self_reports, and the corrective_action / adverse_action / temporarily_closed enforcement flags. v1.0 fetched every one of those columns on every row and emitted none of them, then spent an extra request per 50 operations computing a partial 2-year version instead. Verified live: operation 97587's roster counts sum to 214 and the non-compliance table holds exactly 214 rows for it; 1311197 = 188/188; 290772 = 123/123. All of it now ships, which means the risk signal survives even when the optional join is off or down.

minCapacity was deleting an entire category. v1.0 read an unpublished capacity as 0, so any minCapacity filter silently dropped every operation Texas publishes no capacity for - 141 of the 236 Child Placing Agencies in the state (59.7%). Unknown capacity is now kept and marked.

"New operations" mode never returned a new operation. The baseline lived in the run's default key-value store, which Apify recreates for every run, so every run saw an empty baseline, declared itself the first one, and re-emitted the whole roster. It now uses a named, filter-scoped store.

Also: administrator_director_name and mailing_address are emitted, the roster page cap follows maxResults instead of stopping at 10,000, roster paging carries a stable tiebreaker, accepts_subsidies and the YES/NO columns are tri-state, and the run fails loudly before billing if the upstream drifts.

Who it is for

  • Sales & marketing teams selling into childcare: curriculum, food service, insurance, staffing, POS, cleaning, playground equipment. Filter on contact_channels, capacity and operation_type.
  • Franchise and M&A scouts sizing a market by county, capacity and permit type.
  • Parents, brokers and referral services who need the compliance record next to the contact details.
  • Researchers and journalists studying childcare supply, subsidy acceptance and enforcement.

Example input

{
"state": "TX",
"county": "Harris",
"operationType": "Licensed Center",
"maxResults": 100,
"includeCompliance": true,
"highRiskThreshold": 10
}

Output fields

Every field below is emitted on every row. null always means not checked - never "checked and negative".

FieldDescription
stateUS state of the licensing registry: TX, NY, CA, PA, MA, CT, WA, DE or VT.
operation_idInternal licensing operation ID (join key to state non-compliance records).
operation_numberPublic operation/license number.
operation_nameName of the childcare operation.
operation_typeLicense type, e.g. Licensed Center, Registered Child-Care Home, Listed Family Home.
addressStreet address of the operation location.
cityCity of the operation location.
countyCounty of the operation location.
zip5-digit ZIP code.
phoneProvider phone number. Populated on 99.6% of the active TX roster.
emailProvider email address. Populated on 56.6% of the active TX roster - the sparsest contact field. Use has_email or contact_channels to filter to reachable leads.
websiteProvider website when on file.
capacityTotal licensed capacity. NULL when TX does not publish one - see capacity_known. Never coerced to 0.
ages_servedLicensed-to-serve age groups.
programs_providedPrograms offered (e.g. drop-in care, meals, part-time).
accepts_subsidiesTrue when the operation accepts child-care subsidies (Y/N as published; 6,038 Y of 14,983). NULL when the column is absent rather than false.
issuance_dateLicense/permit issuance date (YYYY-MM-DD).
deficiency_count_2yNumber of non-compliance records for this operation inside the 2-year window. IMPORTANT: the window keys off corrected_date, so this counts deficiencies CORRECTED in the last two years, not cited - the TX table publishes no citation date. NULL when the join did not answer; 0 means it answered and found none.
deficiency_weighted_score_2yRisk-weighted 2-year score (High 5, Medium High 3, Medium 2, Medium Low 1, Low 0.5) - an editorial weighting, not an HHSC measure. NULL when the join did not answer.
recent_deficiency_datesUp to three most recent correction dates inside the window. NULL (not an empty array) when the non-compliance join did not answer - see violations_status.
high_risk_flagTrue when deficiency_weighted_score_2y meets or exceeds highRiskThreshold. NULL when the non-compliance join did not run or did not answer for this operation - v1.0 emitted false in that case, asserting a childcare operation was not high-risk on a check it never performed. Use high_risk_flag_lifetime for a signal that is always available.
is_new_operationTrue when the operation was absent from the previous run baseline for this filter scope. NULL on a seeding run (nothing has been compared yet) and in roster mode.
source_urlOfficial source dataset URL.
administrator_director_nameNamed decision-maker at the operation, as published by TX HHSC. Populated on 69.1% of the active roster. v1.0 fetched this column and discarded it.
mailing_addressOperation mailing address (99.1% populated). Often differs from the physical address for home-based and multi-site operators.
location_addressPhysical location address as published (99.1% populated).
hours_of_operationPublished operating hours.
days_of_operationPublished operating days (97.6% populated).
care_typeHHSC care-type classification (66.6% populated; TX leaves it blank for the rest).
contact_channelsWhich contactable channels this row actually carries: any of "phone", "email", "website", "named_contact". Lets you filter to genuinely reachable leads instead of discovering the gap after export.
has_phoneTrue when a phone number is published. 99.6% of the active roster.
has_emailTrue when an email address is published. Only 56.6% of the active roster carries one - this is the sparsest contact field and is stated rather than implied.
has_named_contactTrue when administrator_director_name is published (69.1%).
operation_statusRaw HHSC operation_status: "Y" active, "N" inactive.
is_activeoperation_status decoded. Null when HHSC publishes no status.
type_of_issuancePermit type: Full Permit, Registered, Listed, Initial, Certified, Renewed Initial.
conditions_on_permitTrue when HHSC has attached conditions to the permit (1,502 of 14,983 statewide). Null when not published.
deficiency_high_totalHHSC-published count of High-risk deficiencies for this operation, straight from the roster record.
deficiency_medium_high_totalHHSC-published Medium High deficiency count.
deficiency_medium_totalHHSC-published Medium deficiency count.
deficiency_medium_low_totalHHSC-published Medium Low deficiency count.
deficiency_low_totalHHSC-published Low deficiency count.
deficiency_count_totalSum of the five HHSC-published deficiency counts. Verified live against the non-compliance table: operation 97587 sums to 214 and the table holds exactly 214 rows. Null only when HHSC publishes none of the five columns.
deficiency_weighted_score_totalThe same editorial weighting as deficiency_weighted_score_2y (High 5, Medium High 3, Medium 2, Medium Low 1, Low 0.5) applied to the HHSC lifetime counts. Available on every row without the optional join.
total_inspectionsHHSC-published inspection count for the operation.
total_assessmentsHHSC-published assessment count.
total_reportsHHSC-published investigation/report count.
total_self_reportsHHSC-published self-report count.
corrective_actionTrue when HHSC has an open corrective action against the operation (31 of 14,983 statewide). Null when not published.
adverse_actionTrue when HHSC has taken adverse action (31 of 14,983 statewide). Null when not published.
temporarily_closedTrue when the operation is temporarily closed (10 of 14,983 statewide). Null when not published.
open_foster_homesFor child-placing agencies: number of open foster homes.
open_branch_officesNumber of open branch offices.
programmatic_servicesProgrammatic services text (4.1% populated - residential operations only).
treatment_servicesTreatment services text (3.4% populated - residential operations only).
roster_status"ok" when the HHSC roster record for this operation was retrieved.
violations_status"ok" (the 2-year non-compliance join answered for this operation), "unavailable" (its batch failed or was truncated), "not_requested" (includeCompliance was false) or "not_published" (the state publishes no violation data - NY, PA, VT, WA, MA). When it is not "ok", deficiency_count_2y and high_risk_flag are NULL rather than 0/false.
compliance_window_basisExactly what the 2-year window measured. The TX non-compliance table has NO citation or inspection date, so the window keys off corrected_date - the date the deficiency was CORRECTED, not cited. Null when the join did not run.
capacity_knownFalse when TX publishes no total_capacity for the operation (142 of 14,937 active, 141 of them Child Placing Agencies).
capacity_filter_applied"not_applied", "passed", or "kept_unknown_capacity" - the last meaning a minCapacity filter was set and this row was kept because its capacity is unpublished, not because it met the threshold. v1.0 silently deleted these rows.
high_risk_flag_lifetimedeficiency_weighted_score_total at or above highRiskThreshold. Derived from HHSC-published counts, so it is available even when the optional 2-year join is off or fails. Null only when HHSC publishes no deficiency counts.
enforcement_flagTrue when any of corrective_action, adverse_action or temporarily_closed is set. Null when none of the three is published.
deficiencies_corrected_at_inspection_2yHow many of the windowed deficiencies were corrected on the spot at inspection (10.7% of the table statewide) - a lower-severity signal than one requiring a later correction. Null when the join did not answer.
delta_baseline_status"ok" (a real cross-run baseline was loaded), "seeded_this_run" (first run for this filter scope; nothing has been compared yet) or "not_applicable" (roster mode).
run_mode"roster" or "new_operations".
source_datasetPortal/dataset the row came from, e.g. "data.ny.gov/cb42-qumz". Present on every row, TX included.
source_agencyLicensing agency that publishes the row.
license_numberState license / permit / provider number as published (NY DOHMH permit, PA license, CT license, WA FamLink id, VT license id...). NULL for TX (use operation_number) and where the state publishes none.
license_expiration_dateLicense expiration date (YYYY-MM-DD) where the state publishes one.
first_licensed_dateDate the program was first licensed/opened, where published (NY facility_opened_date, CT firsteffectivedate, WA initiallicensedate, MA first_issued_date, CA LICENSEFIRSTDATE).
licensee_nameLegal entity or umbrella organisation that holds the license, where published (PA legal_entity_name, WA providername, MA program_umbrella, CA LICENSEENAME).
contact_nameNamed person published for the program outside Texas (NY provider, PA responsible person, WA primary contact, CA facility contact). Texas and CT directors stay in administrator_director_name.
contact_name_roleWhat contact_name is, as the state labels it.
phone_withheld_by_stateNY only: true when OCFS withholds the phone number (phone_number_omitted = Y, 2,415 programs), so a missing phone is a state privacy decision, not a data gap. NULL where the state has no such flag.
address_withheld_by_stateNY only: true when OCFS withholds the street address (address_omitted = Y).
quality_ratingState quality rating as published: PA Keystone STARS level, VT STARS, WA Early Achievers. NULL where not published.
quality_rating_systemName of the rating system behind quality_rating.
capacity_infantLicensed infant capacity where the state publishes capacity by age (NY, VT).
capacity_toddlerLicensed toddler capacity (NY, VT).
capacity_preschoolLicensed preschool capacity (NY, VT).
capacity_school_ageLicensed school-age capacity (NY, VT, CT).
reported_vacanciesVT only: provider-reported open slots (infant + toddler + preschool + school-age). NULL unless all four are published.
vacancies_reported_dateVT only: date the provider last reported capacity and vacancies.
latitudePublished latitude of the program, where the state publishes one.
longitudePublished longitude of the program.
source_status_codeCA only: the raw CCLD STATUS code on the ArcGIS layer. The layer does not decode it; operation_status carries the decoded status from the CCLD facility page when compliance is requested.
inspection_count_publishedInspection count as published: CT distinct inspection cases (since 2005), CA inspection visits on the CCLD facility page. NULL where the state publishes none.
last_inspection_dateMost recent published inspection/visit date (CT, CA). Future-dated visits are ignored.
citation_count_publishedCitations/non-compliance findings published for the program: CT (clean "No Violations" rows excluded), DE (last ~5 years), CA (Type A + Type B). NULL where the state publishes none - never 0 for a state that publishes nothing.
citation_severe_count_publishedCA only: Type A (serious) citations.
last_citation_dateDate of the most recent published citation (CT, DE).
complaint_count_publishedCA only: complaint count on the CCLD facility page.
compliance_basisPlain-language statement of what the compliance fields on this row measure, including "not published by this state" where there is no compliance dataset.
source_duplicate_rowsHow many extra identical source rows for this program were collapsed during this read (WA publishes 650 exact duplicates; one facility appears 361 times). NULL for TX.
run_states_requestedComma list of the states this run was asked for.
run_states_okStates whose sources passed their live checks and answered.
run_states_failedStates that could not answer (source down, drift, or a filter that state cannot apply). NULL when every state answered.
run_states_failed_reasonWhy each failed state could not answer. A failed state contributes NO rows - its absence is disclosed here, never a silent zero.
run_completeTrue when every requested state answered.

Data sources

The non-Texas sources, their row counts and freshness are listed under Coverage above. Each non-Texas source gets the same pre-flight drift gate as Texas: required columns present, row count inside a measured band, a negative control that must return 0 rows, closed vocabularies where the source has them, and a freshness bound. A source that fails its gate fails only its own state leg.

Texas HHSC (keyless Socrata)

  • HHSC CCL Daycare and Residential Operations Data (bc5r-88dy) - 14,983 operations, 14,937 active. Refreshed daily; newest permit issuance was 1 day old when measured.
  • HHSC CCL Non-Compliance Data (tqgd-mf4x) - 138,974 deficiency records, joined on operation_id.

Live drift assertions

The actor checks the upstream before producing a single billable row, and fails the run loudly if any of these regress:

  • both datasets resolve and still publish every column the actor reads (including deficiency_high and administrator_director_name)
  • a negative control (county = 'ZZZZ_NOT_A_REAL_COUNTY') returns exactly 0 rows - proof the $where clause is being applied
  • closed vocabularies: standard_risk_level stays inside {High, Medium High, Medium, Medium Low, Low}; operation_status inside {Y, N}; corrective_action / adverse_action / temporarily_closed inside {YES, NO}. An unrecognised risk level would otherwise be silently scored 1
  • dataset sizes stay inside measured bands (roster 8k-40k against 14,983; non-compliance 50k-500k against 138,974)
  • the newest permit issuance is within 180 days (measured: 1 day)

Every measured value is written to the run log, so tightening a band later is evidence-based.

Use as an MCP tool

Callable by AI agents (Claude, Cursor, etc.) via mcp.apify.com. The violations_status and contact_channels fields let an agent tell a verified negative from an unanswered question, and a reachable lead from an unreachable one.

Honest notes & limitations

  • Nine states, not fifty. Every other state was checked; see the rejected list under Coverage. A state is added only when its own licensing agency publishes a current, keyless, machine-readable roster with contact fields.
  • Compliance depth varies by state. Texas, Connecticut, Delaware and California publish inspection/citation records and those are joined; NY, PA, VT, WA and MA publish none, so those rows read violations_status: not_published with null counts - never 0.
  • California is licensed centers only (no family child-care homes), and its compliance counts come from one CCLD detail request per facility, so includeCompliance on a large CA pull is slower.
  • Washington is centers and school-age programs only, and publishes a phone on only 7.8% of them - email (99.7%) is the channel there.
  • Some fields are only as good as the state publishes them. For example 184 Pennsylvania providers carry a licence-issue date in the future, as published.
  • The 2-year window measures corrections, not citations. The TX non-compliance table publishes no citation or inspection date. corrected_date is the only usable timestamp, so deficiency_count_2y counts deficiencies corrected in the last two years. Every row states this in compliance_window_basis. Measured live: corrected_date is populated on 138,974 of 138,974 rows, and a 2-year window covers 43.0% of the table - the rest are older corrections, not uncorrected violations. For a citation-anchored view use the HHSC lifetime counts (deficiency_count_total).
  • The risk weighting is editorial. High 5, Medium High 3, Medium 2, Medium Low 1, Low 0.5 is this actor's scale, not an HHSC measure. deficiency_high_total and friends are the raw HHSC numbers if you would rather weight them yourself.
  • Deficiency counts are not a quality verdict. A large centre inspected 91 times will out-score a small home inspected twice. Read total_inspections alongside the counts.
  • temporarily_closed, corrective_action and adverse_action are rare (10, 31 and 31 operations statewide) - which is exactly what makes them worth filtering on.
  • No emails for 43.4% of the roster. See the table at the top.

Was this useful?

If a run answered your question, a short review on this Store page helps other buyers find the Actor; every published review is read. If a run gave a wrong or confusing answer, open an Issue on this page with the run ID and it will be treated as a defect, not feedback.

FAQ

How do I get only leads I can actually email? Filter has_email = true, or contact_channels containing "email". Email availability depends on the state: Texas 56.6%, Pennsylvania 92.7%, Vermont 100%, Washington 99.7%; New York, California, Connecticut, Delaware and Massachusetts publish no provider email.

How do I reach a decision-maker rather than a front desk? administrator_director_name carries the named administrator or director on 69.1% of operations; combine with has_named_contact = true.

Why is high_risk_flag sometimes null? Because the actor did not check. null means the non-compliance join did not run (you set includeCompliance: false) or did not answer for that operation; false means it ran and the score was under your threshold. violations_status tells you which. high_risk_flag_lifetime is derived from HHSC's own published counts and is available either way.

Which risk score should I use? deficiency_count_total / high_risk_flag_lifetime for a complete, always-available picture, and deficiency_count_2y / high_risk_flag when recency matters more than completeness.

How do I get alerts for newly licensed daycares? Set mode to new_operations and schedule the actor. The first run for a given filter combination seeds a baseline and emits the full roster with is_new_operation: null; every later run emits only operations that were absent from the baseline.

Does a minimum capacity filter drop anything unexpected? Only in the sense that it keeps more than you might expect: operations with no published capacity are retained and marked kept_unknown_capacity rather than treated as capacity 0.

Pricing

Pay per result: you are charged only for the provider records actually emitted. A run that fails a drift assertion emits nothing and bills nothing.

Other lead feeds from the same catalogue for the same buyer: insurance, food-service, curriculum, staffing and POS sellers, and franchise or M&A scouts. The Where both cover column lists only the places both actors actually serve (see each actor's own Coverage table).

ActorWhat it adds for youExample workflowWhere both cover
Liquor License New Openings TrackerA second vertical for the same outbound motion: bars and restaurants caught at the licence-application stage, typically 60-90 days before openingInsurance and food-service sellers already working childcare leads can add pre-opening hospitality leads in the same statesTX, NY, CA, WA, CT
City Business License LeadsEvery newly licensed business in five cities, with NAICS codes and phone where the city publishes themRun the same outbound campaign against all new local businesses, not just licensed childcareNew York City, Los Angeles and San Francisco (CA), Seattle (WA)
Parcel Owner LookupThe owner of record and owner mailing address of the building a program operates fromFranchise or M&A scouting: for a Hartford centre, find out whether the operator owns its building or leases it, and who the landlord isCT, MA, VT (statewide), NY (statewide incl. NYC), Philadelphia (PA), Houston (Harris County, TX)
KYB Company VerifierA registry verification (found / not found / not checked) of the provider's business entityBefore onboarding a new daycare as a customer, confirm its legal entity (licensee_name where the state publishes one, e.g. PA; otherwise operation_name) is a registered entity in the stateNY, PA, CT; DE (Delaware business-licence list only, not the corporate registry)
Secretary of State Business MonitorFormation date, status and registered agent for the provider's entitySearch the provider's business name to see how long the entity has existed and who its registered agent isNY, PA, CT; DE (business-licence roster)

Verified inputs that populate every field

A few fields are legitimately null on a typical daycare run because Texas only publishes them for certain operation types. Each has a verified live input, so nothing here is a permanently empty column:

FieldNull on the default run becauseInput that populates it (verified live 2026-08-01)
programmatic_services, treatment_servicesResidential operations only (4.1% / 3.4% of the roster){"operationType": "General Residential Operation"} - 25/25 rows populated, e.g. "Child Care" / "Emotional Disorders"
is_new_operationRoster mode never compares against a baseline{"mode": "new_operations"} on the second run for a filter scope
deficiency_count_2y, high_risk_flag, recent_deficiency_datesincludeCompliance was false, or the join did not answer{"includeCompliance": true} - and violations_status says which case you are in
open_foster_homesOnly meaningful for child-placing and residential operations{"operationType": "Child Placing Agency"}

Measured on the actor's own default input (Harris County, Licensed Center, 100 rows): phone 99%, administrator_director_name 77%, email 44%, website 29%. Harris County licensed centers publish email less often than the statewide average of 56.6% - both numbers are given so neither is a surprise.