Childcare Compliance Data Infrastructure
The API for childcare licensing, inspections, and safety signals.
Turn fragmented state records into source-linked facility profiles, explainable risk scores, and alerts your product can act on.
Try CribScore in 60 seconds
Inspect
Open a facility to see its safety score breakdown, inspection history, and source provenance.
Search to pick a facility →Compare
Select two or more facilities to compare scores, trends, and violation counts side by side.
Open compare →Most childcare compliance data is public. Almost none of it is product-ready.
State licensing records are spread across incompatible systems, inconsistent formats, and changing portals. Teams that need childcare safety data still end up doing manual checks, copy-pasting records, and re-verifying the same providers again and again.
- • Different schema in every state
- • No single source for change tracking
- • Hard to compare providers consistently
- • No alerting when a watched provider changes
A normalized layer on top of fragmented state data
CribScore turns state licensing and inspection records into structured, explainable outputs your team can search, score, monitor, and integrate.
Facility profiles
Canonical provider records with license status, provider details, location, capacity, and source links.
Inspection history
Normalized inspection timelines with underlying violations and correction details.
Explainable safety signals
Scores and flags backed by visible factors, not black-box logic.
Historical change tracking
See what changed, when it changed, and whether a provider is improving or declining.
Watchlists and alerts
Track important providers and get notified via API when new violations or status changes appear.
API and exports
Use the data through API calls, bulk exports, and workflow-friendly delivery.
How the product fits into a workflow
- 1. Ingest and normalize official state data.
- 2. Attach provenance, history, and explainable scoring.
- 3. Expose facility records through API, watchlists, and exports.
- 4. Trigger action when something changes.
What the CribScore means
CribScore is a 0-100 compliance risk signal computed from official state licensing and inspection records. It is not a safety guarantee or a replacement for your own judgment.
- Higher score
- Fewer recent violations, active license, recent inspections.
- Lower score
- More or more severe recent violations, lapsed license, or stale inspections.
- Explainable
- Every score includes a breakdown showing exactly which factors drove it: violation counts by severity, inspection recency, license status, and correction discounts. See it live on any facility detail page.
State licensing records remain the authoritative source. CribScore organizes and scores them — it does not replace them.
Built for teams that need more than a webpage
- Benefits platforms: Add official safety and licensing context to provider recommendations.
- Insurance and underwriting: Use repeatable facility compliance inputs in risk review workflows.
- Relocation and mobility: Help families evaluate childcare options with official inspection context.
- Parent-facing apps: Embed licensing and violation data without building a 50-state normalization layer yourself.
- Agents: Give AI systems typed answers instead of making them parse inconsistent state websites.
Designed for trust, not just convenience
Every meaningful output should show where it came from, when it was refreshed, and what changed. Trust is the product.
- Source-linked records — each search result links to the official state record.
- Visible last refresh timestamps — open any facility from search to see provenance and refresh time.
- Launch-state honesty — which states are live and how we prioritize coverage.
- Explainable scoring factors — breakdown panels on every facility detail page.
- Historical event trail — inspections and score history on facility pages.
What customers actually get
Canonical facility ID, license status, last inspection date, violation summary, score and drivers, source URLs, and last refresh timestamp — structured for workflows and agents.
{
"id": "550e8400-e29b-41d4-a716-446655440000",
"name": "Example Childcare Center",
"state_code": "CA",
"license_status": "active",
"last_inspection_date": "2025-02-14",
"violation_count_12mo": 2,
"safety_score": 87.4,
"safety_score_trend": "stable",
"safety_score_breakdown": {
"version": "v1.1",
"final_score": 87.4,
"violation_penalty": 4.2,
"inspection_recency_label": "within_12mo",
"top_penalty_drivers": []
},
"source_url": "https://example-state.gov/licensing/record/…",
"last_scraped_at": "2025-03-20T08:00:00Z"
}FAQ
- Is this a daycare marketplace?
- No. This is infrastructure for teams that need official childcare compliance data inside a workflow or product.
- How is this different from a childcare directory?
- Directories help people browse. We provide structured access, explainable scoring, historical tracking, and alerts that teams can integrate into real workflows.
- Which states are supported first?
- We launch with a small set of strong states and prioritize reliability over superficial national coverage.
- Do you verify the underlying state records?
- We do not replace the source authority. We normalize, organize, track, and expose official records with clear provenance so customers can trust and audit what they are using.
- Can this power internal workflows as well as customer-facing products?
- Yes. The same data can support underwriting, provider review, recommendation systems, compliance monitoring, and agent workflows.
- Will there be an API?
- Yes. The API is the core product. Any interface is secondary to structured delivery.
Need childcare compliance data inside your product?
If your team is still manually checking state portals, we should talk.