Restaurant Inspection Scores & Violations (Official City Data) avatar

Restaurant Inspection Scores & Violations (Official City Data)

Pricing

Pay per usage

Go to Apify Store
Restaurant Inspection Scores & Violations (Official City Data)

Restaurant Inspection Scores & Violations (Official City Data)

Pricing

Pay per usage

Rating

0.0

(0)

Developer

Bryan

Bryan

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

2 days ago

Last modified

Share

Restaurant Inspection Evidence — 7 Official Jurisdictions

This Actor retrieves official restaurant and food-facility inspection records from seven government feeds and preserves each jurisdiction's meaning. It does not translate unlike scores into a fake national ranking.

Verified source coverage

Live one-record canaries ran on 2026-08-02 against every source:

JurisdictionOfficial datasetPortalNewest row observedFreshness
New York City, NY43nn-pn8jSocrata2026-07-30current
Chicago, IL4ijn-s7e5Socrata2026-07-31current
Austin, TXecmv-9xxiSocrata2026-05-22aging
Cincinnati, OHrg6p-b3h3Socrata2026-07-31current
Boulder County, COtuvj-xz3mSocrata2025-08-29stale
Montgomery County, MD46p5-g5naSocrata2024-10-03stale
King County, WAFeatureServer 0ArcGIS2024-03-30stale

current, aging, and stale describe the newest row returned by the bounded canary. They do not guess why a publisher has not posted newer records. This makes nominal coverage distinguishable from currently updating coverage.

Evidence contract

Every record includes:

  • stable record_key and content-based record_fingerprint;
  • published business and inspection identifiers where available;
  • facility type, risk, geocode, critical flag, violation code, and violation detail where published;
  • explicit score_direction and source_row_grain;
  • official source URL, dataset ID, portal, attribution, fetch time, and source status; and
  • the original source row in raw, with configured phone fields removed.

The Actor also writes RUN-RECEIPT to its default key-value store. The receipt contains requested jurisdictions, effective limits and filters, per-source counts, newest observed dates, freshness, errors, warnings, completeness, and a canonical SHA-256 receipt_hash.

Input

FieldMeaning
citiesAny subset of nyc, chicago, austin, cincinnati, boulder, montgomery, king_county.
businessNameContainsCase-insensitive establishment substring.
resultContainsJurisdiction-published result/grade substring; scores are never converted into grades.
since / untilInclusive YYYY-MM-DD inspection range.
maxRecordsPerCityNewest-first bound from 1 to 5,000 per jurisdiction.
socrataAppTokenOptional caller-owned Socrata app token, kept secret and sent only as X-App-Token.

Interpretation boundaries

  • NYC scores are lower-is-better; Austin scores are higher-is-better; other jurisdictions may publish no score or a source-specific score. Compare within a jurisdiction unless a qualified analyst defines a documented transformation.
  • Some feeds publish one row per inspection and others one row per violation. source_row_grain makes this explicit.
  • A stale feed is still factual historical data, but it is not described as current monitoring.
  • A bounded query is not a claim that the Actor enumerated every matching record.

Tests

npm test checks normalization, identity keys, stable fingerprints, date bounds, ArcGIS pagination, source receipts, and receipt hashing. npm run test:live performs a bounded official-source pull. node test_sources_live.mjs canaries all seven sources and prints their observed freshness.