Watermark.
All sites
Switch site 35 sites · 10 basins2 states Group by
OH Ohio 34
BOSC BOSC Lima Ottawa River · Lima, OH Building Under construction #1261 URB Urbana Mad River · Great Miami Live Investigating #1263 DEF Defiance Maumee mainstem Queued Investigating #1264 FIN Findlay Blanchard River Queued Investigating #1265 TOL Toledo Lucas Co WRRF Queued Investigating #1266 VWT Van Wert Town Creek · Little Auglaize Queued Investigating #1267 BRY Bryan Prairie Creek · Tiffin River Queued Investigating #1268 OTW Ottawa Blanchard River (lower) Queued Investigating #1269 SPR Springfield Mad River · Great Miami Queued Investigating #1270 XEN Xenia Little Miami Queued Investigating #1271 WPA Dayton · WPAFB Mad River · Great Miami Queued Investigating #1272 HAM Hamilton · Middletown Great Miami (lower) Queued Investigating #1273 TRP Troy · Piqua Great Miami (upper) Queued Investigating #1274 SID Sidney Great Miami · headwaters Queued Investigating #1275 GRV Greenville · Darke Co Stillwater · basin divide Queued Investigating #1276 WIL Wilmington Todd Fork · Little Miami Queued Investigating #1277 WUN West Union · Adams Co Ohio Brush Creek · Ohio River Queued Investigating #1278 NAL New Albany · Licking Scioto ↔ Muskingum divide Tracking Investigating #1279 COL Columbus Scioto · Olentangy Tracking Investigating #1280 CSH Coshocton Tuscarawas + Walhonding Tracking Investigating #1281 PIK Piketon Scioto River · PORTS Tracking Investigating #1282 SAN Sandusky · Perkins Twp Sandusky Bay · Lake Erie Tracking Investigating #1283 NWK Newark Licking River Tracking Investigating #1284 ZAN Zanesville Muskingum mainstem Tracking Investigating #1285 FRE Fremont · Clyde Lower Sandusky Tracking Investigating #1286 TIF Tiffin Sandusky (mid) Tracking Investigating #1287 BUC Bucyrus Sandusky headwaters Tracking Investigating #1288 CLE Cleveland Lower Cuyahoga Tracking Investigating #1289 AKR Akron Upper Cuyahoga · CVNP Tracking Investigating #1290 LRD Lordstown · Warren Upper Mahoning Tracking Investigating #1291 YNG Youngstown Mahoning mainstem Tracking Investigating #1292 LAN Lancaster Upper Hocking Tracking Investigating #1293 ATH Athens Lower Hocking Tracking Investigating #1294 LOG Logan Hocking Hills Tracking Investigating #1295
MAU Maumee Basin 8 sites
2MI The Two Miamis 9 sites
SE Southeastern Basins 10 sites
NE Northeast Basins 8 sites
Each site is a section of the Watermark platform — pivoted by basinstate. Live & building sites open; queued and tracking sites route to their coming-soon / watch page.
Switch site 35 sites · 10 basins2 states 35 open Group by

Each site is one Watermark investigation. The page color says what opens; the campus line is the build on the ground — two different clocks.

OH Ohio 34
BOSC BOSC Lima Ottawa River · Lima, OH Draft Under construction #1261 URB Urbana Mad River · Great Miami Open Investigating #1263 DEF Defiance Maumee mainstem Queued Investigating #1264 FIN Findlay Blanchard River Queued Investigating #1265 TOL Toledo Lucas Co WRRF Queued Investigating #1266 VWT Van Wert Town Creek · Little Auglaize Queued Investigating #1267 BRY Bryan Prairie Creek · Tiffin River Queued Investigating #1268 OTW Ottawa Blanchard River (lower) Queued Investigating #1269 SPR Springfield Mad River · Great Miami Queued Investigating #1270 XEN Xenia Little Miami Queued Investigating #1271 WPA Dayton · WPAFB Mad River · Great Miami Queued Investigating #1272 HAM Hamilton · Middletown Great Miami (lower) Queued Investigating #1273 TRP Troy · Piqua Great Miami (upper) Queued Investigating #1274 SID Sidney Great Miami · headwaters Queued Investigating #1275 GRV Greenville · Darke Co Stillwater · basin divide Queued Investigating #1276 WIL Wilmington Todd Fork · Little Miami Queued Investigating #1277 WUN West Union · Adams Co Ohio Brush Creek · Ohio River Queued Investigating #1278 NAL New Albany · Licking Scioto ↔ Muskingum divide Watching Investigating #1279 COL Columbus Scioto · Olentangy Watching Investigating #1280 CSH Coshocton Tuscarawas + Walhonding Watching Investigating #1281 PIK Piketon Scioto River · PORTS Watching Investigating #1282 SAN Sandusky · Perkins Twp Sandusky Bay · Lake Erie Watching Investigating #1283 NWK Newark Licking River Watching Investigating #1284 ZAN Zanesville Muskingum mainstem Watching Investigating #1285 FRE Fremont · Clyde Lower Sandusky Watching Investigating #1286 TIF Tiffin Sandusky (mid) Watching Investigating #1287 BUC Bucyrus Sandusky headwaters Watching Investigating #1288 CLE Cleveland Lower Cuyahoga Watching Investigating #1289 AKR Akron Upper Cuyahoga · CVNP Watching Investigating #1290 LRD Lordstown · Warren Upper Mahoning Watching Investigating #1291 YNG Youngstown Mahoning mainstem Watching Investigating #1292 LAN Lancaster Upper Hocking Watching Investigating #1293 ATH Athens Lower Hocking Watching Investigating #1294 LOG Logan Hocking Hills Watching Investigating #1295
MAU Maumee Basin 8 sites
2MI The Two Miamis 9 sites
SE Southeastern Basins 10 sites
NE Northeast Basins 8 sites
The page — what opens on Watermark Open · Draftfull record Queued · Watchingpreview page Restrictedrequest access
The campus — the build on the ground Investigating Confirmed Under construction Operational
MCP

Connect to the corpus

The Watermark Directory exposes a Model Context Protocol endpoint at https://watermark.directory/api/mcp. Connect Claude Desktop or any MCP-compatible client to search and interrogate the investigative record directly.

Claude Desktop setup

Add the following block to your claude_desktop_config.json (find it at ~/Library/Application Support/Claude/claude_desktop_config.json on macOS):

{
  "mcpServers": {
    "watermark-directory": {
      "url": "https://watermark.directory/api/mcp",
      "type": "http"
    }
  }
}

Restart Claude Desktop after saving. The watermark-directory server will appear in the MCP server list. No API key is required for the public tier.

Available tools

The public tier exposes 5 tools. All return evidentiary-tagged results — see evidentiary vocabulary below.

Tool Description Required params Example call
search_corpus Semantic + keyword search over the documentary corpus query

                  {"query": "NPDES permit violations", "site": "lima", "limit": 5}
                
get_timeline Dated events filterable by date range and category

                  {"since": "2015-01-01", "until": "2020-12-31", "category": "permit"}
                
get_entities Entity graph: parties, roles, parcels, and relationships

                  {"type": "company", "site": "fort-wayne"}
                
get_hypotheses Boom-origin hypothesis signals per site

                  {"site": "lima"}
                
get_documents Ingested source documents by collection

                  {"collection": "oepa", "site": "lima"}
                

Rate limits and budget

Tier Rate limit Daily output budget Auth
Public 60 requests / hour per IP 100k tokens / day (shared) None — open access
Keyed Higher limits 500k tokens / day (per key) Authorization: Bearer <token>

To request a keyed account, submit a tip or correction and mention your research use case. Keyed access is granted to journalists, researchers, and public-interest investigators.

Evidentiary vocabulary

Every result from the corpus carries an evidence tag. These tags encode how strongly the claim is grounded in the documentary record:

[verified]
Directly confirmed in a primary source document — a permit, a recorded deed, meeting minutes, a regulatory filing. The document is in the corpus and the claim is traceable to a specific page.
[inference]
Logically derived from verified facts but not explicitly stated in a source. A reasonable conclusion the record supports, not a claim a document makes directly.
[reference]
Sourced from a secondary or historical reference (published books, surveys, news) rather than a primary instrument. Accurate but one step removed from the primary record.
[open]
A question or gap the record has not yet resolved — an area where the corpus is incomplete or where the evidence is insufficient to draw a conclusion.

When a model queries this corpus, it should surface these tags in its reasoning and not assert [inference] claims with the same confidence as [verified] ones.

Auto-discovery

The endpoint publishes a /.well-known/mcp.json discovery document. MCP clients that support auto-discovery can find the server without manual configuration.