SourceFinch Verified · Building Permits

County Well Permits

Recent records from County Well Permits on data.montgomerycountymd.gov: up to 1,000 rows with stable identifiers for change monitoring. Contact columns are excluded.

Monitor this sourceAPI, CLI, SDK and MCP

What changedNo changes in 7 days

At a glance

Jurisdiction
data.montgomerycountymd.gov
Publisher updates
Updated by the publisher; typically daily or weekly
Recommended schedule
Daily for your monitor; SourceFinch verifies the recipe daily
Records per run
1,000 in the latest run
Record key
id
Acquired from
Open data portal: https://data.montgomerycountymd.gov/resource/vddw-tec2.json?$select=permit_no,application_type,work_type,added_date,issued_date,expired_date,status,building_area,description,st_no,st_name&$limit=1000&$where=issued_date IS NOT NULL&$order=issued_date DESC
Recipe
v1.0.0, approved November 17, 2026
Version notes
First Verified version generated 2026-11-17 from batch backlog.
Verified since
November 17, 2026
Last green run
November 17, 2026
Changes, last 7 days
0 · see what changed

What the data contains

Open data published on data.montgomerycountymd.gov as “County Well Permits”. Each daily run reads up to 1,000 rows through the portal's SODA API, naming only non-contact columns. A monitor reports new and changed rows inside the cohort. Leaving the cohort does not establish deletion. SourceFinch is independent of the publisher.

Fields and types

Every record has these fields. The key field id identifies a record across runs, so changes are reported field by field.

FieldTypeDescription
idkeystringPublisher field `permit_no`. The record key.
application_typestring, nullablePublisher field `application_type`.
work_typestring, nullablePublisher field `work_type`.
added_datedatetime, nullablePublisher field `added_date`.
issued_datedatetime, nullablePublisher field `issued_date`.
expired_datedatetime, nullablePublisher field `expired_date`.
statusstring, nullablePublisher field `status`.
building_areastring, nullablePublisher field `building_area`.
descriptionstring, nullablePublisher field `description`.
st_nostring, nullablePublisher field `st_no`.
st_namestring, nullablePublisher field `st_name`.

Sample output

The first 5 of 1,000 records from SourceFinch's own run on November 17, 2026, exactly as delivered.

FieldRecord 1Record 2Record 3Record 4Record 5
id11746071174601117460611209111174030
application_typeCOUNTY WELL PERMITCOUNTY WELL PERMITCOUNTY WELL PERMITCOUNTY WELL PERMITCOUNTY WELL PERMIT
work_typeDRILLDRILLDRILLDRILLDRILL
added_date2026-10-14T02:10:36.0002026-10-14T02:10:38.0002026-10-14T02:10:15.0002025-06-11T03:06:49.0002026-10-08T12:10:37.000
issued_date2026-10-21T12:10:29.0002026-10-21T07:10:15.0002026-10-21T03:10:42.0002026-10-20T03:10:09.0002026-10-16T05:10:17.000
expired_date2027-10-21T12:10:29.0002027-10-21T07:10:15.0002027-10-21T03:10:42.0002027-10-20T03:10:09.0002027-10-16T12:10:00.000
statusIssuedIssuedIssuedIssuedIssued
building_area00000
descriptionThis permit is for closed loop geothermal well(s). See site plan for location(s). The Department of Permitting Services must be notified 24 hours before construction of well(s). The driller must notify any municipality for wells within that municipality or within one mile of its boundary. Well(s) to be sealed according to COMAR 26.04.04 standards and grouted from the bottom up in one continuous operation. Well(s) must be 10 feet from all underground utilities, storm water pipes, easements and right of ways and 50 feet from storm water structures. A mechanical permit is required to erect, install, enlarge, alter repair, remove, convert or replace a mechanical heating, ventilating and air conditioning system. It is recommended that the property owner record a drawing of all buried pipe locations and depths associated with the geothermal heating and cooling system. The property owner and the licensed driller have the responsibility to comply with Montgomery County and Maryland State regulations and laws concerning dust, noise, sediment control, and all other environmental issues. Drilling water containing drill cuttings and grout must not be discharged off-site into streams or storm drains; or onto the property of others.This permit is for closed loop geothermal well(s). See site plan for location(s). The Department of Permitting Services must be notified 24 hours before construction of well(s). The driller must notify any municipality for wells within that municipality or within one mile of its boundary. Well(s) to be sealed according to COMAR 26.04.04 standards and grouted from the bottom up in one continuous operation. Well(s) must be 10 feet from all underground utilities, storm water pipes, easements and right of ways and 50 feet from storm water structures. A mechanical permit is required to erect, install, enlarge, alter repair, remove, convert or replace a mechanical heating, ventilating and air conditioning system. It is recommended that the property owner record a drawing of all buried pipe locations and depths associated with the geothermal heating and cooling system. The property owner and the licensed driller have the responsibility to comply with Montgomery County and Maryland State regulations and laws concerning dust, noise, sediment control, and all other environmental issues. Drilling water containing drill cuttings and grout must not be discharged off-site into streams or storm drains; or onto the property of others.This permit is for closed loop geothermal well(s). See site plan for location(s). The Department of Permitting Services must be notified 24 hours before construction of well(s). The driller must notify any municipality for wells within that municipality or within one mile of its boundary. Well(s) to be sealed according to COMAR 26.04.04 standards and grouted from the bottom up in one continuous operation. Well(s) must be 10 feet from all underground utilities, storm water pipes, easements and right of ways and 50 feet from storm water structures. A mechanical permit is required to erect, install, enlarge, alter repair, remove, convert or replace a mechanical heating, ventilating and air conditioning system. It is recommended that the property owner record a drawing of all buried pipe locations and depths associated with the geothermal heating and cooling system. The property owner and the licensed driller have the responsibility to comply with Montgomery County and Maryland State regulations and laws concerning dust, noise, sediment control, and all other environmental issues. Drilling water containing drill cuttings and grout must not be discharged off-site into streams or storm drains; or onto the property of others.Well to be surveyed by a licensed surveyor as per COMCOR Chapter 27A. Any location change from theprimary well site must have WRITTEN approval by this department PRIOR to drilling. Well to be at least 100 feet from any septic system. Well to be pre-drilled and log submitted to this office prior to issuance of buildingpermit. Septic System Permit application required prior to issuance of building permit. House must be a minimum of 30 feet from approved well site(s).This permit is issued to drill a replacement well.  Replacement well shall be drilled at one of the approved locations shown on the attached plan.  Existing well to be properly abandoned and sealed in accordance with COMAR 26.04.04. Any location change from the approved well site(s) must have written approval by this Department prior to drilling. This property is in water category W-3; an exception shall be obtained by the property owner from Montgomery County Department of Environmental Protection.  
st_no2184118014218311100124710
st_namePARKLAND TRACEYELLOW ACREPARKLAND TRACEPICASSOFREDERICK
Sample as JSON
[
  {
    "id": "1174607",
    "st_no": "21841",
    "status": "Issued",
    "st_name": "PARKLAND TRACE",
    "work_type": "DRILL",
    "added_date": "2026-10-14T02:10:36.000",
    "description": "This permit is for closed loop geothermal well(s). See site plan for location(s). The Department of Permitting Services must be notified 24 hours before construction of well(s). The driller must notify any municipality for wells within that municipality or within one mile of its boundary. Well(s) to be sealed according to COMAR 26.04.04 standards and grouted from the bottom up in one continuous operation. Well(s) must be 10 feet from all underground utilities, storm water pipes, easements and right of ways and 50 feet from storm water structures. A mechanical permit is required to erect, install, enlarge, alter repair, remove, convert or replace a mechanical heating, ventilating and air conditioning system. It is recommended that the property owner record a drawing of all buried pipe locations and depths associated with the geothermal heating and cooling system. The property owner and the licensed driller have the responsibility to comply with Montgomery County and Maryland State regulations and laws concerning dust, noise, sediment control, and all other environmental issues. Drilling water containing drill cuttings and grout must not be discharged off-site into streams or storm drains; or onto the property of others.",
    "issued_date": "2026-10-21T12:10:29.000",
    "expired_date": "2027-10-21T12:10:29.000",
    "building_area": "0",
    "application_type": "COUNTY WELL PERMIT"
  },
  {
    "id": "1174601",
    "st_no": "18014",
    "status": "Issued",
    "st_name": "YELLOW ACRE",
    "work_type": "DRILL",
    "added_date": "2026-10-14T02:10:38.000",
    "description": "This permit is for closed loop geothermal well(s). See site plan for location(s). The Department of Permitting Services must be notified 24 hours before construction of well(s). The driller must notify any municipality for wells within that municipality or within one mile of its boundary. Well(s) to be sealed according to COMAR 26.04.04 standards and grouted from the bottom up in one continuous operation. Well(s) must be 10 feet from all underground utilities, storm water pipes, easements and right of ways and 50 feet from storm water structures. A mechanical permit is required to erect, install, enlarge, alter repair, remove, convert or replace a mechanical heating, ventilating and air conditioning system. It is recommended that the property owner record a drawing of all buried pipe locations and depths associated with the geothermal heating and cooling system. The property owner and the licensed driller have the responsibility to comply with Montgomery County and Maryland State regulations and laws concerning dust, noise, sediment control, and all other environmental issues. Drilling water containing drill cuttings and grout must not be discharged off-site into streams or storm drains; or onto the property of others.",
    "issued_date": "2026-10-21T07:10:15.000",
    "expired_date": "2027-10-21T07:10:15.000",
    "building_area": "0",
    "application_type": "COUNTY WELL PERMIT"
  },
  {
    "id": "1174606",
    "st_no": "21831",
    "status": "Issued",
    "st_name": "PARKLAND TRACE",
    "work_type": "DRILL",
    "added_date": "2026-10-14T02:10:15.000",
    "description": "This permit is for closed loop geothermal well(s). See site plan for location(s). The Department of Permitting Services must be notified 24 hours before construction of well(s). The driller must notify any municipality for wells within that municipality or within one mile of its boundary. Well(s) to be sealed according to COMAR 26.04.04 standards and grouted from the bottom up in one continuous operation. Well(s) must be 10 feet from all underground utilities, storm water pipes, easements and right of ways and 50 feet from storm water structures. A mechanical permit is required to erect, install, enlarge, alter repair, remove, convert or replace a mechanical heating, ventilating and air conditioning system. It is recommended that the property owner record a drawing of all buried pipe locations and depths associated with the geothermal heating and cooling system. The property owner and the licensed driller have the responsibility to comply with Montgomery County and Maryland State regulations and laws concerning dust, noise, sediment control, and all other environmental issues. Drilling water containing drill cuttings and grout must not be discharged off-site into streams or storm drains; or onto the property of others.",
    "issued_date": "2026-10-21T03:10:42.000",
    "expired_date": "2027-10-21T03:10:42.000",
    "building_area": "0",
    "application_type": "COUNTY WELL PERMIT"
  },
  {
    "id": "1120911",
    "st_no": "11001",
    "status": "Issued",
    "st_name": "PICASSO",
    "work_type": "DRILL",
    "added_date": "2025-06-11T03:06:49.000",
    "description": "Well to be surveyed by a licensed surveyor as per COMCOR Chapter 27A. Any location change from theprimary well site must have WRITTEN approval by this department PRIOR to drilling. Well to be at least 100 feet from any septic system. Well to be pre-drilled and log submitted to this office prior to issuance of buildingpermit. Septic System Permit application required prior to issuance of building permit. House must be a minimum of 30 feet from approved well site(s).",
    "issued_date": "2026-10-20T03:10:09.000",
    "expired_date": "2027-10-20T03:10:09.000",
    "building_area": "0",
    "application_type": "COUNTY WELL PERMIT"
  },
  {
    "id": "1174030",
    "st_no": "24710",
    "status": "Issued",
    "st_name": "FREDERICK",
    "work_type": "DRILL",
    "added_date": "2026-10-08T12:10:37.000",
    "description": "This permit is issued to drill a replacement well.  Replacement well shall be drilled at one of the approved locations shown on the attached plan.  Existing well to be properly abandoned and sealed in accordance with COMAR 26.04.04. Any location change from the approved well site(s) must have written approval by this Department prior to drilling. This property is in water category W-3; an exception shall be obtained by the property owner from Montgomery County Department of Environmental Protection.     ",
    "issued_date": "2026-10-16T05:10:17.000",
    "expired_date": "2027-10-16T12:10:00.000",
    "building_area": "0",
    "application_type": "COUNTY WELL PERMIT"
  }
]

Evidence behind every value

  • Each run keeps the publisher's exact response, hashed with SHA-256. This sample came from a response with hash 3a1188e8c208c6288250b160ea04d14a67afb73dbf09b106a079818e91e37c1a.
  • Every value records where it came from in that response: a JSON Pointer into the retained capture.
  • Each run gets a signed manifest (Ed25519) timestamped by an RFC 3161 authority: this run's manifest hash is 039ebc13f83287dd0abb8370d8c09230018b1479199618448f7626dd2abe275c, timestamped November 17, 2026.
  • The compliance state at capture is recorded with the evidence: robots.txt hash and verdict, AI-preference signals, crawler identity and the usage rights below.
  • Download any run as an evidence bundle (WACZ) and check it offline, without trusting SourceFinch: sourcefinch verify-bundle run.wacz.

Terms posture and usage rights

Terms
Automated access permitted · publisher's terms
robots.txt
Allows this path · SHA-256 0891c16b56b3d1af…
AI-preference signals
None observed at review
Public record
Yes. Municipal/state open data portal dataset vddw-tec2 on data.montgomerycountymd.gov.
Reviewed
November 17, 2026; next review May 17, 2027
Licence basis
Publisher's terms of use
Commercial use
Allowed
Redistribution
Allowed
Attribution
Required (text below)

Published on the data.montgomerycountymd.gov open data portal for public use. Anonymous SODA API access needs no key. Portal robots.txt typically allows /resource/ with a crawl delay. Contact-name columns are not requested by this recipe.

Montgomerycountymd open data (data.montgomerycountymd.gov). SourceFinch is independent of the publisher.

Usage rights travel with every record SourceFinch delivers (API, exports, webhooks and evidence bundles). They are our documented understanding of the publisher's stated terms, not legal advice.

Reliability

Runs, last 30 days
1
Green
100%
Failed
0
Median run time
6.1 s
Latest run
success, November 17, 2026

Measured on completed runs of this recipe version across SourceFinch, anonymized, within a rolling 30-day window. First successful observation: November 17, 2026. A new recipe has only the history collected since that date; this is not a 30-day uptime guarantee.

Use it

Every surface creates the same monitor from this Verified recipe. Monitors keep record history, report field-level changes and deliver by webhook, export or email. You confirm you have the right to collect the source (rights: true).

Console

Open this recipe in the console: it preserves the reviewed URL, fields and record key. Review the latest captured sample, confirm source rights, and choose a schedule before creating your monitor.

Portable recipe

Copy into the console's Import or share a recipe panel to customize fields, types and schedules. This configuration contains no captured records or workspace IDs.

{
  "schema": "sourcefinch/source@1",
  "name": "County Well Permits",
  "url": "https://data.montgomerycountymd.gov/resource/vddw-tec2.json?$select=permit_no,application_type,work_type,added_date,issued_date,expired_date,status,building_area,description,st_no,st_name&$limit=1000&$where=issued_date IS NOT NULL&$order=issued_date DESC",
  "recipe": {
    "mode": "http",
    "format": "json",
    "items": "[*]",
    "fields": {
      "id": "permit_no",
      "st_no": "st_no",
      "status": "status",
      "st_name": "st_name",
      "work_type": "work_type",
      "added_date": "added_date",
      "description": "description",
      "issued_date": "issued_date",
      "expired_date": "expired_date",
      "building_area": "building_area",
      "application_type": "application_type"
    },
    "required": [
      "id"
    ],
    "types": {
      "added_date": "datetime",
      "expired_date": "datetime",
      "issued_date": "datetime"
    }
  },
  "schedule": "daily",
  "key_field": "id"
}

source.json

The request body used by the API, CLI and SDK examples.

{
  "name": "County Well Permits",
  "url": "https://data.montgomerycountymd.gov/resource/vddw-tec2.json?$select=permit_no,application_type,work_type,added_date,issued_date,expired_date,status,building_area,description,st_no,st_name&$limit=1000&$where=issued_date IS NOT NULL&$order=issued_date DESC",
  "recipe": {
    "mode": "http",
    "format": "json",
    "items": "[*]",
    "fields": {
      "id": "permit_no",
      "st_no": "st_no",
      "status": "status",
      "st_name": "st_name",
      "work_type": "work_type",
      "added_date": "added_date",
      "description": "description",
      "issued_date": "issued_date",
      "expired_date": "expired_date",
      "building_area": "building_area",
      "application_type": "application_type"
    },
    "required": [
      "id"
    ],
    "types": {
      "added_date": "datetime",
      "issued_date": "datetime",
      "expired_date": "datetime"
    }
  },
  "key_field": "id",
  "schedule": "daily",
  "rights": true,
  "catalog": {
    "slug": "montgomerycountymd-county-well-permits",
    "version_id": "cc17bb59-4c5a-4931-ac1d-ff0714aea9d1"
  }
}

REST API

Create an API key under Console → API keys. Reference: /docs/api.

# the Verified entry (fields, recipe, sample, terms) as JSON
curl https://sourcefinch.com/v1/catalog/montgomerycountymd-county-well-permits -H "Authorization: Bearer $SOURCEFINCH_API_KEY"

# create the monitor from source.json (below)
curl -X POST https://sourcefinch.com/v1/sources \
  -H "Authorization: Bearer $SOURCEFINCH_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d @source.json

# then run it now (later runs follow the schedule)
curl -X POST https://sourcefinch.com/v1/sources/$SOURCE_ID/runs \
  -H "Authorization: Bearer $SOURCEFINCH_API_KEY" \
  -H "Idempotency-Key: $(uuidgen)"

CLI

The sourcefinch CLI is not on npm yet; see /docs/cli.

sourcefinch login
sourcefinch catalog get montgomerycountymd-county-well-permits --source-json > source.json
sourcefinch sources create --file source.json
sourcefinch runs create $SOURCE_ID --wait
sourcefinch records $SOURCE_ID

TypeScript SDK

The SDK is not on npm yet; see /docs/sdk.

import { SourceFinch } from "@sourcefinch/sdk";

const sf = new SourceFinch({ apiKey: process.env.SOURCEFINCH_API_KEY });
const entry = await sf.catalog.get("montgomerycountymd-county-well-permits");
const source = await sf.sources.create({
  catalog: { slug: entry.slug, version_id: entry.recipe.version_id },
  name: entry.name.slice(0, 100),
  url: entry.acquisition_path.endpoint,
  recipe: entry.recipe.definition,
  key_field: entry.recipe.key_field,
  schedule: entry.recipe.schedule,
  rights: true, // you confirm you have the right to collect this source
});
const run = await sf.runs.wait((await sf.runs.create(source.id)).id);
console.log(run.status);

MCP

Remote MCP server with OAuth; see /docs/mcp.

claude mcp add --transport http sourcefinch https://sourcefinch.com/mcp

# then ask your agent:
"Use SourceFinch to monitor County Well Permits: get_catalog_source montgomerycountymd-county-well-permits,
then create_source with its create_source_args (dry run first), then run_source."

Pricing

Each check is one run, whatever the number of records, and failed runs are free. On its default daily schedule this source uses about 30 runs a month, which fits the Free plan's 300 runs. It uses HTTP acquisition, so no browser runs are needed. See plans.

More from Montgomerycountymd open data and in building permits.

SourceFinch is independent and is not affiliated with or endorsed by Montgomerycountymd open data. This page describes county well permits as SourceFinch acquires it.