The Race — Building Democracy in the Age of AI. People race toward a shared finish line.
The Race
← Specific Events

United States / New York City

Scorecard

BetaNYC shows how civic groups can combine public-record access with citizen AI literacy

What happened

Alongside its October 5 Council testimony, BetaNYC documented existing civic AI resources. Its [public tools page](https://www.beta.nyc/featured-tools/ai-tools-for-nyc-democracy/) describes connectors for Council legislation, procurement notices, public spending, laws, service information and other public records. A connector uses the Model Context Protocol, a standard interface through which an assistant can request information from a specified source. Some connectors require free agency API keys; others do not. Availability is not an accuracy audit.

Its [AI 101 materials](https://www.beta.nyc/ai-101-class-materials/) serve **New Yorkers attending introductory classes**, including recordings and settings guidance for common assistants. The [testimony](https://www.beta.nyc/2026/10/05/council-ai-hearing-2026/) separately schedules an October 8 train-the-trainer session for **staff of community partner organizations in the Council’s AI Community Engagement initiative**. That audience is not all city employees. Future lessons and the paused fellowship are not delivered programmes; the specific funding and curriculum independence of this session were not established.

**Availability, license and chronology resolved.** BetaNYC’s public toolkit describes seven free civic-data connectors compatible with multiple assistant clients. The inspected Council connector’s README, MIT license and changelog confirm installation and copy/modify/distribute rights. Its initial release was **May 19, 2026**, MIT licensing May 22, and hybrid operation May 26; October 5 testimony/publicity is not a new launch. Current code includes unreleased 2.6.0 functions, which are not represented as packaged capability. The underlying government APIs already existed. Free keys, local indexing, storage, freshness, assistant-provider and output-accuracy dependencies remain. Other connectors’ exact first-release dates are not established here.

**Approved disposition October 6.** Scorecard **Dispersion +1; Leaning dispersion / Opens**, Lanes 6/5/7/1, for the available reusable, independently deployable multi-model interface to public information. Usage scale is not a prerequisite for recognizing this available capability; no claim of evaluated accuracy or new resident decision rights. Preserve May release history and October discovery/scoring dates. Current May–October Scorecard comparisons found no BetaNYC/Council-connector score. Individually scored, context only for TR-024; no supporting-count or numerical trend contribution. Add the public-data connector example to the existing interoperability/architectural-separability Policy Tool, not a duplicate project-specific tool. October 8 training remains prospective; check its actual delivery, audience, funding and governance October 9.

**Primary artifacts:** https://github.com/BetaNYC/nyc-council-mcp ; https://github.com/BetaNYC/nyc-council-mcp/blob/main/CHANGELOG.md ; https://github.com/BetaNYC/nyc-council-mcp/blob/main/LICENSE .

Potential direction of power

Leaning dispersion · Dispersion +1

Useful public records and people able to interpret them can create countervailing civic capacity. Putting an assistant over a dataset is not the same as giving residents a decision right. The intermediaries, source grounding and ability to question answers matter.

Window of contestability

Opens

Available MIT-licensed, multi-model civic-data connectors open a usable information interface without waiting for usage scale; they do not establish answer accuracy or new decision rights.

Supporting sources

  1. beta.nyc · Supporting source 1 ↗
  2. beta.nyc · Supporting source 2 ↗
  3. beta.nyc · Supporting source 3 ↗
  4. github.com · Supporting source 4 ↗
  5. github.com · Supporting source 5 ↗
  6. github.com · Supporting source 6 ↗

Research connections