Machine-readable feed: legistar_api — refreshed automatically each day. Note: CONFIRMED via two independent WebFetch passes of the live calendar (2026-06-15). Official source: NYC City Council Legislative Research Center (Legistar/InSite by Granicus), https://legistar.council.nyc.gov/Calendar.aspx — resolved successfully, 410 records across 5 pages, filterable by year/session/committee. All 7 upcoming meetings were read directly off that page and re-verified individually: the 6/24/2026 Education+Technology joint hearing confirmed at 1:00 PM Council Chambers; the 8/4/2026 Land Use hearing confirmed at 12:00 PM, 250 Broadway 8th Floor Hearing Room 1; the 9/15/2026 Oversight & Investigations/Education joint hearing 'Examining the Use of Screens in NYC Public Schools' confirmed; the 10/20/2026 Environmental Protection & Waterfronts hearing 12:00 PM confirmed; and the 11/19, 12/3, 12/17 Stated Meetings at 1:30 PM Council Chambers all confirmed. Machine-readable feed for a daily checker: the Legistar Web API, client code 'nyc', base https://webapi.legistar.com/v1/nyc/, Events endpoint with OData date filtering. NOTE: direct WebFetch of the API returned HTTP 403 (Granicus WAF blocking automated user-agents) from this environment; the API client code 'nyc' and date-filter pattern are documented by official NYC Council docs (council.nyc.gov/legislation/api) and Granicus (webapi.legistar.com/Help). A free API key is requested via a name/email form for full automated read access, and a custom User-Agent typically clears the WAF. feed_type 'legistar_api' is honest (the endpoint exists; only automated access from this IP/UA was blocked). Per-meeting iCalendar (.ics) and Excel/PDF/Word exports also exist on the InSite calendar but are per-item, not a single subscribable feed, so the Legistar API remains the recommended daily-check feed. Each calendar row links to a Meeting Details page with the posted PDF agenda. Committee schedules shift; confirm exact times/locations on the per-meeting detail page before relying on them. RE-VERIFIED 2026-07-10/11 (fresh discovery pass). Legistar API re-confirmed real-but-token-gated: curl https://webapi.legistar.com/v1/nyc/Events?$top=3 -> HTTP 403 'Token is required' — confirmed this is a genuine auth gate (not a generic WAF block) by contrast-testing the open mauicounty client, which returned HTTP 200 real JSON on the identical call pattern. council.nyc.gov/legislation/api/ (HTTP 200) confirms in its own text: "The Legistar Web API for New York City is now available for read access by the public… To get the access token, fill out the form below." Human calendar legistar.council.nyc.gov/Calendar.aspx re-confirmed live (HTTP 200), matching the existing verified upcoming-meeting rows below. NEW finding this pass: Legistar's schema structurally supports per-EventItem roll-call votes — proven via the OPEN mauicounty client (EventItems carry 'EventItemRollCallFlag':1, and GET /v1/mauicounty/EventItems/{id}/Votes returns real JSON, HTTP 200) — NYC almost certainly has the same schema but every NYC Legistar call is blocked pending the free token. NYC Open Data 'Legislation' dataset (Socrata uf8p-ervp) is real and unauthenticated (HTTP 200) but 'status' is free text (Committee/Enacted/etc), not a numeric vote tally. Recommended next step: request the free Legistar API key via council.nyc.gov/legislation/api/, then retest /v1/nyc/EventItems/{id}/Votes with the token. national/jurisdictions.json's ny-nyc entry already had the correct vendor=legistar/config.client=nyc (no placeholder to fix) — left untouched, this is a re-verification not a first wiring.