The Intercept frames the $2.5M quote as a strategic abuse of the 'reasonable fees' provision in Oregon's public records law. They argue departments across Oregon and nationally are using escalating fees to make lawful records requests economically infeasible, effectively nullifying sunshine laws without technically violating them.
Draws a parallel between this fee tactic and software industry patterns like surprise overage billing and 'contact sales' gatekeeping. Argues the mechanism is identical: when you can't block a request outright, you price it out of reach so the stated policy remains 'yes' while the effective policy becomes 'no'.
Notes that Salem Reporter is a four-person nonprofit whose entire annual budget is roughly 1/25th of the quoted fee. Even though courts can intervene in fee disputes, litigation costs money and years — resources that small accountability journalism outlets simply don't have, which is precisely why the tactic works.
Highlights that Oregon's law, like most state sunshine statutes and federal FOIA, leaves the definition of 'reasonable' fees largely to the agency being asked for records. This self-regulation creates an obvious conflict of interest where the entity that wants to withhold information gets to set the price for releasing it.
The Keizer Police Department in Oregon told the independent news site Salem Reporter it would cost $2,546,000 to fulfill a public records request about a single officer. The request, filed under Oregon's public records law, sought documents related to misconduct complaints and internal affairs findings about one named officer. The department's math: thousands of hours of attorney review time, line-by-line redaction, and administrative overhead — billed back to the requester at government rates.
For context: Salem Reporter is a small nonprofit newsroom. The quoted fee is roughly 25 times its entire annual budget. The outlet is not going to pay it. Nobody was supposed to. That's the point of the number.
Oregon's public records law, like most state sunshine statutes and the federal FOIA, permits agencies to charge "reasonable" fees for the labor of producing records. What counts as reasonable is largely left to the agency itself. Courts can intervene, but litigating a fee dispute costs money and years — resources a four-person newsroom doesn't have. The Intercept's reporting notes this isn't an isolated Keizer quirk: departments across Oregon and nationally have been quoting five-, six-, and now seven-figure fees for records that, a decade ago, would have been produced for a few hundred dollars in copying costs.
This is a story about access control via pricing, and it should feel familiar to anyone who has ever designed an API.
When you can't block a request outright — because the law says you have to honor it — you make the request economically infeasible. Rate limits with surprise overage billing. Enterprise-only endpoints. "Contact sales" where there used to be a docs page. The pattern is the same whether it's a police department or a SaaS vendor sunsetting a free tier: the stated policy is still "yes," but the effective policy is "no, and prove we're wrong in court."
The shift matters because transparency law was architected on an assumption that no longer holds: that agencies have a baseline interest in cooperating, and fees exist to recover marginal cost. Strip that assumption and the whole structure inverts. Fees become the primary gatekeeping mechanism, and the agency has unilateral authority to set them. Attorney review time at $400/hour, applied to "every page" of a thousand-page email thread, generates arbitrary numbers on demand. There is no technical cap. There is no SLA.
The Reporters Committee for Freedom of the Press has tracked this trend for years, and the pattern is consistent across red and blue states. In 2024, a Washington State police department quoted $300,000 for body-camera footage. Massachusetts agencies have billed newsrooms for "segregation of exempt material" at rates that assume a human attorney reads every byte. The federal government is marginally better only because FOIA has a fee-waiver provision for journalists — a provision Oregon's law notably lacks teeth to enforce.
The community reaction on Hacker News (230 points, heavy comment thread) landed on the obvious engineering critique: the costs are fabricated. Redaction at scale is a solved problem. Open-source tools like `docquery`, Microsoft's Presidio, and purpose-built civic-tech projects like MuckRock's DocumentCloud can run named-entity recognition and PII masking over tens of thousands of pages in hours, not years. The $2.5M number assumes a workflow deliberately designed to be expensive. When an agency quotes a seven-figure fee for records that could be processed with a Python script and a GPU, the fee isn't a cost estimate — it's a policy statement.
If you're building anything that touches public-sector transparency — civic tech, open-data pipelines, journalism tools, policy research platforms — the threat model has shifted. The old assumption was that your pipeline would hit redaction walls and legal exemptions. The new assumption is that your pipeline will hit a paywall that your users cannot clear.
A few concrete implications:
Build for the fee-waiver fight, not just the records fight. The chokepoint in transparency workflows is increasingly the invoice, not the production. Tooling that helps requesters document journalistic purpose, draft fee-waiver appeals, and track agency response patterns is more leveraged than another PDF scraper. MuckRock already does some of this; there's room for more.
Automate the cost-estimate review. When an agency quotes a fee, that quote almost always itemizes hours and rates. Those line items are frequently absurd on inspection — redaction labor that would require a single reviewer to work 60 hours a week for a year. A tool that parses fee quotes and flags implausible estimates against known benchmarks (pages/hour for redaction, standard hourly rates) would arm requesters with concrete evidence for appeals.
Treat redaction tooling as a public good. The strongest argument against inflated fees is a working demonstration that the labor is unnecessary. If your team builds redaction, NER, or document-review tools, publishing them with permissive licenses and running public demos against real agency documents forces the question into the open. Agencies have a harder time billing $2.5M for work that an undergraduate can do in a weekend with the right open-source stack.
Watch the state-law variance. Oregon's law lacks a meaningful fee-waiver standard; California's is better; Florida's used to be best and is being eroded. If you ship a product to civic-tech users across states, the fee landscape is now a first-class input to your UX, not a legal footnote.
The Salem Reporter story is going to get cited for years, not because $2.5M is uniquely egregious but because it's a clean teaching example. The fee is so obviously disconnected from any real cost that it strips the pretense off the mechanism. Expect more newsrooms to publicize their fee quotes as a form of accountability journalism in itself — the number becomes the story. Expect agencies to respond by burying fee calculations in less reviewable formats. And expect the fight over transparency, in practice, to migrate from "what can we see" to "what does it cost to look." If you work on any part of the stack between a citizen and a government record, that's the terrain now.
Top 10 dev stories every morning at 8am UTC. AI-curated. Retro terminal HTML email.