The city/county inspection datasets in this cluster (NYC 43nn-pn8j, Chicago 4ijn-s7e5, SF tvy3-wexg, King County f29f-zza5, Austin ecmv-9xxi) all run on Socrata and share SoQL syntax, but use different field names for the same concept: outcome is grade in NYC, results in Chicago, facility_rating_status in SF, inspection_result in King County, and score-only (no letter grade) in Austin
Filter by date range with $where=inspection_date between '2026-01-01T00:00:00' and '2026-06-30T23:59:59' using SoQL floating_timestamp literals (no timezone suffix)
Register a free account and application token separately on each city's own Socrata domain - a data.cityofnewyork.us token does not work against data.cityofchicago.org - and send it via the X-App-Token header
Without a token, anonymous requests share a low per-IP throttling pool and return HTTP 429 when exceeded; use $limit and $offset to page through large result sets
Known gotchas
Column-name drift between cities (grade vs results vs facility_rating_status vs inspection_result) means filter code written for one city's dataset throws a query.soql.no-such-column error if reused unmodified against another city's dataset
$where date comparisons require the SoQL floating_timestamp format with no trailing 'Z' or UTC offset; passing an ISO string with a timezone suffix causes a parse error on most of these datasets
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?