Facility safety · outcome guide

Export official inspection evidence without flattening local scoring systems.

Restaurant inspection grades, scores, violation language, and row grain vary by publisher. CivicDataForge normalizes the delivery shape while preserving the jurisdiction-specific fields and official source evidence needed to interpret each record.

Open the Restaurant Inspection Actor

1. Start with one row per jurisdiction

{
  "cities": ["nyc", "chicago", "austin"],
  "maxRecordsPerCity": 1
}

The supported keys are nyc, chicago, austin, cincinnati, boulder, montgomery, and king_county. A one-row probe confirms schema, source freshness, and record grain before a larger export.

2. Inspect meaning before comparing values

Preserve local semantics.

Do not rank a grade from one authority against a numeric score from another as if they share one national scale. Retain the jurisdiction, source field names, inspection date, violation detail, and source URL.

Read RUN-RECEIPT.

The receipt binds the requested jurisdictions, record cap, counts, source status, and evidence hashes. Use it to document exactly what the export covered.

3. Increase the cap only after the probe is healthy

{
  "cities": ["nyc", "chicago", "austin"],
  "maxRecordsPerCity": 250
}

The per-jurisdiction cap is bounded from 1 to 5,000. Export CSV or JSON through Apify after verifying that the probe contains the fields your portfolio process needs.

Use boundary: official inspection feeds can be delayed, corrected, incomplete, and published at different grains. This product supports facility research and monitoring; it does not replace the issuing health authority or create a universal safety grade.

Need a recurring handoff?

Use the partner route to define a buyer-owned CSV, webhook, API, or MCP delivery after the source and jurisdiction scope are accepted.