For businesses and developers

Texas utility data, by ZIP code, inside your product

Give Utilify a Texas ZIP code or address and get back the providers listed for it for electricity, internet, gas, water, sewer and trash, with plan prices as last verified (not live prices). Use it as a REST API, import the OpenAPI spec, or connect an AI agent to the MCP server.

REST APIhttps://utilify.io/api
OpenAPI 3.1/openapi.json
MCP serverhttps://utilify.io/mcp
CoverageTexas only
Free accessRead-only, no key, 60 requests a minute per IP

What it is

Setting up utilities at a new Texas address means working out who serves it. Electricity depends on whether the address is in the competitive market or served by a city utility or co-op. Internet options vary from area to area. Gas, water, sewer and trash are usually local and change from one city to the next. Utilify brings that information together by ZIP code and returns it as structured JSON.

The same data is available three ways:

What you can build

Moving and relocation platforms

Show a customer the electricity, internet, gas, water, sewer and trash providers listed for their new Texas ZIP code, inside your own move flow, before move-in day.

Property management and proptech

Generate a utility setup list for each unit: who to contact for each service and what to arrange before the lease starts. Drop it into a move-in packet or a resident portal.

Real estate listings

Show the utility providers listed for a listing's ZIP code, as a starting point buyers and renters can check with each provider. Lookups are by ZIP code, not by street.

AI assistants and agents

Connect the MCP server and your assistant can answer “what utilities do I set up in this ZIP code?” with structured data instead of a web search.

Example

Who supplies electricity in downtown Austin?

curl "https://utilify.io/api/providers/search?address=78701&types=electricity"

The response, trimmed to fewer fields:

{
  "data": {
    "supported": true,
    "address": "78701",
    "zipCode": "78701",
    "providers": [
      {
        "providerName": "Austin Energy",
        "providerSlug": "austin-energy",
        "utilityType": "electricity",
        "website": "https://austinenergy.com",
        "cheapestPlan": {
          "name": "Residential Electric Service",
          "rate": "0.1130",
          "rateUnit": "per_kwh",
          "planType": "fixed"
        },
        "isDeregulated": false
      }
    ],
    "regulatedUtilities": [
      {
        "utilityType": "electricity",
        "utilityName": "Austin Energy",
        "utilityKind": "municipal",
        "website": "https://austinenergy.com",
        "note": "ZIP 78701 is outside the ERCOT customer-choice market. ..."
      }
    ],
    "searchedAt": "2026-11-17T12:32:32.042Z"
  }
}

Where the electricity market is not open to choice, as in Austin, the response says who the utility is and why, in regulatedUtilities, rather than listing plans that cannot be bought there.

Public endpoints

EndpointReturns
GET /api/providers/searchProviders listed for an address or ZIP, by utility type, with each provider's lowest-cost plan as last verified.
GET /api/providers/{slug}One provider's plans, prices as last verified, contract terms and fees.
POST /api/providers/compareTwo to five providers side by side at one address.
GET /api/checklistA move-in utility setup checklist for an address and move date.

Full parameters and response schemas are in the OpenAPI document.

Access

Read access is free and open: no sign-up and no key, limited to 60 requests a minute per IP address. For production use, request access below: an API key, the volume you need and support are agreed with each customer. Pricing is on request and depends on volume and use.

Free

Prototypes, small tools and personal agents.

  • Read-only endpoints and MCP read tools
  • No API key needed
  • 60 requests a minute per IP address

Free

Starter

A product going live with Texas users.

  • An API key for your product
  • Volume agreed with you
  • Email support

Pricing on request

Pro

Platforms with steady daily traffic.

  • An API key for your product
  • Volume agreed with you
  • Priority email support

Pricing on request

Enterprise

Large platforms and data partners.

  • Volume, terms and support agreed with you
  • A named contact

Pricing on request

Scope and data

Request access

Tell us what you are building. We read every request and reply by email.

A few sentences is plenty: who your users are and where the data would appear. Please leave out phone numbers; we reply by email.

We use these details only to reply to you. See our Privacy Policy.

Prefer email? Write to hello@utilify.io.