PUCT Texas Water & Sewer Service Areas API and MCP server

API access

Your AI client reaches PUCT Texas Water & Sewer Service Areas through one ParcelOps MCP endpoint, so there is no separate key to hold for it and no per-source client to write. Reaching it takes no credentials of your own.

What this source cannot tell you

• ⚠ Anything outside Texas (statewide). A request past that edge comes back empty rather than approximated.
• ⚠ A snapshot of certificated areas as currently amended. It carries no history: a decertified or amended boundary is replaced, not versioned.
• ⚠ Anything Public Utility Commission of Texas — Water and Sewer CCN Service Areas does not publish. ParcelOps returns this source as it stands and never fills a blank field from a different one.
• ⚠ No CCN polygon at a point does not mean no water or sewer service. Texas Water Code 13.242 lets a municipality serve inside its own corporate limits without a CCN, which is why downtown Austin returns zero water and zero sewer CCN.
• ⚠ PUCT directs users to read service areas together with CCN facility lines: some utilities are certificated only along a corridor and hold no bounded service-area polygon.
• ⚠ A CCN is a service obligation of record, not confirmation that a main, tap, or capacity exists at the parcel. Confirm availability and extension policy with the named utility.
• ⚠ STATUS may read "Pending Final Order Docket No. NNNNN" and can name more than one docket, meaning the boundary is contested and subject to change.
• ⚠ CCN_NO can be comma-joined and COUNTY is a comma-joined label that PUCT truncates for wide certificates. Neither is a join key; use ccnNumbers[] and counties[].
• ⚠ One utility commonly holds several polygons under one CCN number. Union the rows before reporting a footprint.
• ⚠ PUCT electric service-area layers (IOU, cooperative, municipal) are NOT exposed by this connector because of a Platts Master Service Agreement restriction in their metadata, so it cannot say which electric utility or ISO/RTO serves a point. That is a deliberate license deferral, not an absence of PUCT electric data.
• ⚠ PUCT metadata is internally inconsistent: the water layer description is a copy of the sewer text and reports a 2015 update date against a 2026-07-14 modified date. Layer contents are correct; the upstream prose is never echoed.
• ⚠ TWDB and several city, county, and vendor tenants republish copies of these layers with different counts and no sewer coverage. This connector reads only PUCT's own organization; do not blend counts across mirrors.

Methods (4)

A method is one call your agent can make against this source.

• queryCcnAtPoint

  read

  Who provides water or sewer at a Texas coordinate: the certificated utility or water company.

  What you must providelatitudelongitude

  Records returnedutility_service_area

  How to get more resultsnone

  Coordinate systemEPSG:4326

  FreshnessScheduled · every 3 months (source-level)
  Input schema

  {
    "type": "object",
    "properties": {
      "latitude": {
        "type": "number",
        "minimum": 25.5,
        "maximum": 36.7,
        "description": "WGS84 latitude inside Texas."
      },
      "longitude": {
        "type": "number",
        "minimum": -107,
        "maximum": -93.3,
        "description": "WGS84 longitude inside Texas (negative)."
      },
      "services": {
        "type": "array",
        "description": "Which CCN layers to read. Defaults to both water and sewer.",
        "minItems": 1,
        "maxItems": 2,
        "uniqueItems": true,
        "items": {
          "type": "string",
          "enum": [
            "water",
            "sewer"
          ]
        }
      }
    },
    "required": [
      "latitude",
      "longitude"
    ],
    "additionalProperties": false
  }

  • ⚠ Point-in-polygon at one coordinate. A parcel that straddles a boundary can have a different answer at its other corner.

  Zero rows means no certificated provider of record, not that nobody serves it.

• searchCcnByUtility

  read

  Find CCN service areas by utility name, certificate number, county, or docket status.

  What you must provideservice

  Records returnedutility_service_area

  How to get more resultsoffset (offsetField: offset, limitField: limit)

  Coordinate systemEPSG:4326

  FreshnessScheduled · every 3 months (source-level)
  Input schema

  {
    "type": "object",
    "properties": {
      "service": {
        "type": "string",
        "enum": [
          "water",
          "sewer"
        ],
        "description": "Which CCN layer to search."
      },
      "utilityName": {
        "type": "string",
        "maxLength": 100,
        "description": "Case-insensitive fragment of the certificated name or trade name."
      },
      "ccnNumber": {
        "type": "string",
        "pattern": "^[0-9A-Za-z]{4,12}$",
        "description": "Certificate number. Matches rows whose CCN_NO is comma-joined."
      },
      "county": {
        "type": "string",
        "maxLength": 60,
        "description": "County name; matched inside the comma-joined COUNTY label."
      },
      "status": {
        "type": "string",
        "enum": [
          "approved",
          "pending",
          "any"
        ],
        "description": "approved = Commission Approved; pending = awaiting a final order."
      },
      "limit": {
        "type": "integer",
        "minimum": 1,
        "maximum": 500
      },
      "offset": {
        "type": "integer",
        "minimum": 0,
        "maximum": 100000
      }
    },
    "required": [
      "service"
    ],
    "additionalProperties": false
  }

  One utility often holds several polygons under one CCN number.

• getCcnFacilityLinesNearPoint

  read

  Certificated water or sewer facility corridors within a few miles of a Texas coordinate.

  What you must providelatitudelongitude

  Records returnedutility_service_area

  How to get more resultsnone

  Coordinate systemEPSG:4326

  FreshnessScheduled · every 3 months (source-level)
  Input schema

  {
    "type": "object",
    "properties": {
      "latitude": {
        "type": "number",
        "minimum": 25.5,
        "maximum": 36.7,
        "description": "WGS84 latitude inside Texas."
      },
      "longitude": {
        "type": "number",
        "minimum": -107,
        "maximum": -93.3,
        "description": "WGS84 longitude inside Texas (negative)."
      },
      "radiusMiles": {
        "type": "number",
        "minimum": 0.1,
        "maximum": 25,
        "description": "Search radius in statute miles. Defaults to 2."
      },
      "services": {
        "type": "array",
        "description": "Which CCN layers to read. Defaults to both water and sewer.",
        "minItems": 1,
        "maxItems": 2,
        "uniqueItems": true,
        "items": {
          "type": "string",
          "enum": [
            "water",
            "sewer"
          ]
        }
      },
      "limit": {
        "type": "integer",
        "minimum": 1,
        "maximum": 200
      }
    },
    "required": [
      "latitude",
      "longitude"
    ],
    "additionalProperties": false
  }

  • ⚠ A facility line is a certificated corridor, not a mapped pipe, and proximity is not a connection point.

  Only 477 corridors exist statewide, so a zero here is the common case.

• getServiceInfo

  read

  Layer inventory, live record counts, field vocabulary, docket links, and coverage limits.

  FreshnessScheduled · every 3 months (source-level)
  Input schema

  {
    "type": "object",
    "properties": {},
    "required": [],
    "additionalProperties": false
  }

  Also names the electric layers this connector deliberately excludes.

Where this source is used

• Land research

  Parcel records, ground conditions, and what reaches the property line, for raw and rural land.

• Data center siting

  Power, water, transport, airspace, and hazard screening for a site before anyone signs anything.

• Which utility serves this property?
• What water system serves this address, and has it been in violation?