PAID — Public Access Information Dividend · A Quigley Group initiative · Full disclosurePaid by bots$0.0000· 0 views
Policy Research Paper · 73 Sources

Charging for the Bots

How New York Municipalities Can Lawfully Establish Paid Access Programs for Automated Web Crawlers Harvesting Public Data

A grounded policy research paper for municipal officials. Every factual and legal claim is cited to a source logged in the citation registry. Where the law is unclear, the text flags it as an open question.

~25,500 words
Length
73
Sources cited
26 + 5 appendices
Sections
New York (primary)
Jurisdiction
Municipal officials
Audience
August 14, 2026
Date
Important — Not Legal Advice

This document is informational policy research prepared for discussion. It is not legal advice and does not create an attorney-client relationship. Every factual and legal claim is cited to a source logged in the citation registry using the [S-NNN] identifier. Where the law is unclear, the text flags it as an open question requiring review by qualified municipal counsel. Municipal officials must consult their own attorney and the NY Committee on Open Government (COOG) before adopting any ordinance or fee program described here.


New York municipalities publish vast amounts of public information on their websites — meeting minutes, budgets, property records, permits, contracts, and notices. Under the NY Freedom of Information Law (FOIL), any person can request copies of these records at low statutory fees ($0.25 per page for paper copies, or the actual cost of reproduction for electronic records) S-011, S-202. But the same information is also being harvested at high volume by automated software programs — “bots,” “crawlers,” or “scrapers” — that visit municipal websites at machine speed, downloading thousands or hundreds of thousands of pages, consuming server capacity and bandwidth, and reselling or monetizing the data for commercial purposes. Industry research indicates that bots account for approximately 53% of all web activity, and “bad bots” alone make up roughly 40% of all traffic S-116.

This paper examines whether and how a New York municipality can lawfully establish a paid automated-access program — a registered, key-based, rate-limited system (typically an API, or Application Programming Interface) through which commercial bots pay a fee tied to the actual cost of providing that access, while residents, journalists, and researchers continue to access the same public information for free through the regular website and through FOIL.

The research finds:

  1. A municipality likely has the legal authority to adopt a local law creating such a program, under NY’s home rule provisions (NY Constitution Article IX; Municipal Home Rule Law § 10) S-002, S-012. The program would be a voluntary, alternative, premium channel that supplements — and does not replace — free public website access and free FOIL access S-011.
  2. The critical legal distinction is between a FOIL request (a formal, written demand for records that triggers statutory deadlines and fee caps) and passive website access (reading already-published information). A bot crawling a public website is not, by that act alone, making a FOIL request S-011.
  3. There is a “public access floor” the municipality cannot go below. A municipality cannot eliminate free public access to records that FOIL requires be available, nor charge more than FOIL permits for records obtained through FOIL S-011, S-202.
  4. Fees should be structured as cost recovery, not revenue generation. Every government fee statute examined — federal FOIA S-001, S-201, NY FOIL S-011, S-202, the federal PACER court-records system S-204, S-205, and the E-Government Act of 2002 S-016 — is built on a cost-recovery standard.
  5. The technical tools exist and are affordable. Cloudflare offers free bot management S-110. AWS WAF Bot Control starts at $10/month S-115. Open-source API gateways like Kong provide authentication, rate limiting, and usage logging at no software cost S-106.
  6. Realistic revenue is modest. A small/medium NY municipality (population 25,000–150,000) should expect, conservatively, $500–$75,000/year in gross revenue, with net revenue likely $0–$40,000/year after program costs.
  7. The data must be cleaned and structured first. A paid automated-access tier only makes sense after the municipality has inventoried its data, converted it to machine-readable formats (CSV, JSON, GeoJSON — not PDFs), published it with metadata, and established reliable update cadences S-301.
  8. Several significant legal questions remain unresolved and require review by qualified municipal counsel before any ordinance is enacted S-011, S-015.

This paper synthesizes legal, technical, economic, and data-organization research into a single coherent document. It is accompanied by standalone companion deliverables: a model ordinance, an implementation playbook, and a data organization guide. The recommended path is to start with cost recovery, a free resident tier, clean data first, and a phased rollout over approximately 12 months.


What the research found.

Eight findings ground the entire paper. Each is supported by cited sources and flagged where the law is unsettled.

Finding 01

A municipality likely has the legal authority

Under NY's home rule provisions (NY Constitution Article IX; Municipal Home Rule Law § 10), a municipality can adopt a local law creating a paid automated-access program — a voluntary, alternative, premium channel that supplements, and does not replace, free public website access and free FOIL access.

Finding 02

The critical legal distinction

A FOIL request is a formal, written demand for records triggering statutory deadlines and fee caps. Passive website access is simply reading already-published information. A bot crawling a public website is not, by that act alone, making a FOIL request.

Finding 03

There is a public access floor

A municipality cannot eliminate free public access to records that FOIL requires be available, nor charge more than FOIL permits for records obtained through FOIL. Any paid program must preserve the right of any person to walk into town hall or submit a written FOIL request.

Finding 04

Fees should be cost recovery, not revenue

Every government fee statute examined — federal FOIA, NY FOIL, the federal PACER court-records system, and the E-Government Act of 2002 — is built on a cost-recovery standard. PACER was successfully sued when its fees exceeded actual cost and revenue was diverted.

Finding 05

The technical tools exist and are affordable

Cloudflare offers free bot management on its free plan. AWS WAF Bot Control starts at $10/month. Open-source API gateways like Kong provide authentication, rate limiting, and usage logging at no software cost. Even AWS has productized AI traffic monetization directly.

Finding 06

Realistic revenue is modest

A small/medium NY municipality (population 25,000–150,000) should expect, conservatively, $500–$75,000/year in gross revenue, with net revenue likely $0–$40,000/year after program costs — enough to fund infrastructure and civic technology, not to balance a budget.

Finding 07

The data must be cleaned first

A paid automated-access tier only makes sense after the municipality has inventoried its data, converted it to machine-readable formats (CSV, JSON, GeoJSON — not PDFs), published it with metadata, and established reliable update cadences.

Finding 08

Several legal questions remain unresolved

Whether a bot crawling a public municipal website constitutes a FOIL request, whether FOIL preempts a municipal fee program, and whether First Amendment public-forum doctrine applies — all require review by qualified municipal counsel before any ordinance is enacted.


The full structure.

Part VIII: National Appendix

The complete research paper, in full.

The full 25,500-word paper is available as a single, navigable document with a sticky table of contents sidebar. Every section, every citation, every table — nothing omitted.

Read it section by section or jump straight to what matters to you — the legal framework, the economic models, the implementation playbook, or the model legislation overview.

Companion deliverables
  • Model Ordinance — two versions (cost-recovery & revenue) with plain-language commentary and a legal review checklist
  • Implementation Playbook — in-house vs. contractor vs. hybrid, RFP templates, staffing, procurement, budget worksheets
  • Data Organization Guide — formats, schemas, metadata, quality, governance, privacy review
  • Interactive Tools — revenue calculator, readiness self-assessment, ordinance selector

📖

If you’re an official

Start with the Abstract and Key Findings above. Then read Section 17 (the implementation decision) and the companion playbook. Don’t skip the not-legal-advice notice — this is research, not a finished answer.

⚖️

If you’re an attorney

Focus on Part II (Legal Ground Truth) and Appendix D (Open Legal Questions). Every citation uses the [S-NNN] identifier pointing to the source registry. Verify every statutory citation against official McKinney’s before reliance.

🔧

If you’re in IT

Part III (Technical Reality) covers the bot management, WAF, and API gateway stack with specific products, pricing, and configuration examples. Part V covers data formats, schemas, and the maturity roadmap.

Ready to dig in?

The full paper is one click away — 26 sections, 73 sources, all in one place.

Read the Full Paper →View Source Registry →