# EPCOR

> EPCOR Utilities Inc. is a municipally owned Canadian utility headquartered in Edmonton, Alberta, wholly owned by the City of Edmonton, operating electricity distribution and transmission, water and wastewater, and natural gas distribution across Alberta, Ontario and British Columbia, and water utilities in Arizona, New Mexico and Texas. EPCOR publishes no developer portal, no API documentation and no OpenAPI. It nonetheless exposes two real programmatic surfaces: a public ArcGIS Online organization whose production feature services (outages, water main breaks, water infrastructure projects, US service areas) are readable anonymously, and a regulator-compelled Green Button consumer-data interface in its three Ontario service areas that is gated behind customer login and vendor approval.

This file was generated by the API Evangelist enrichment pipeline on 2026-07-27. EPCOR publishes no llms.txt of its own (`/llms.txt` returns 404 on every EPCOR host).

## Machine-readable surface (anonymous, no key)

- [ArcGIS feature service folder](https://services6.arcgis.com/Ji2rusuWXDFSqNsP/ArcGIS/rest/services?f=json): EPCOR's public ArcGIS Online organization (owner `epcor_outages`), 36 production feature services plus their dev/test/ist/uat copies. Backs the outage map.
- [Derived OpenAPI 3.1](https://raw.githubusercontent.com/api-evangelist/epcor/refs/heads/main/openapi/epcor-outages-arcgis-openapi.yml): 115 read operations over 39 production layers, derived by API Evangelist from live ArcGIS metadata. Not published by EPCOR.
- [Derived JSON Schema](https://raw.githubusercontent.com/api-evangelist/epcor/refs/heads/main/json-schema/epcor-outage-features.schema.json): attribute schemas for all 39 layers.
- [Outage map config](https://outages.epcor.com/assets/config.json): the endpoint configuration the public map loads.

Key layers: `ocps_prod_av` (Edmonton active power outage areas), `ocps_prod_pl` (planned), `EPCor_Water_Outages_Prod` and `water_canada_outages_prod` (water main breaks), `Water_InfrastructureProjects_Prod` (capital projects), `UDF_Events_Prod` (scheduled field events), `usa_<district>_outages_prod` and `ServiceAreas_<district>_prod` (14 US water districts in Arizona and New Mexico).

## Gated surface (regulated consumer data)

- [Green Button - Collingwood area](https://www.epcor.com/ca/en/on/collingwood-area/account/manage-account/green-button.html): Download My Data and Connect My Data for Ontario electricity customers.
- [Green Button - Aylmer area](https://www.epcor.com/ca/en/on/aylmer-area/account/manage-account/green-button.html): natural gas.
- [Green Button - Kincardine area](https://www.epcor.com/ca/en/on/kincardine-area/account/manage-account/green-button.html): electricity.
- [Customer Green Button portal](https://epcorgas.savagedata.com/): login required, every path redirects to authentication.
- [Third-party vendor registration](https://epcorgasonboarding.savagedata.com/): application approval required. No API key, no public technical documentation, no published base URI or ESPI version.

## Human surfaces

- [EPCOR](https://www.epcor.com/): corporate site.
- [Outage map](https://outages.epcor.com/): the human render of the feature services above.
- [Customer portal](https://customerportal.epcor.com/app/): account login.
- [News and blog](https://www.epcor.com/ca/en/news.html)
- [Contact](https://www.epcor.com/ca/en/ab/edmonton/contact-edmonton.html)
- [Privacy policy](https://www.epcor.com/ca/en/about/policies/privacy-policy.html)
- [Terms of use](https://www.epcor.com/ca/en/about/policies/terms-of-use.html)

## Rules an agent must follow

- **No credential exists for reading the feature services.** Do not send a key or token.
- **Errors arrive as HTTP 200** with an `{"error": {...}}` body. Check the body, not the status line.
- **Outage date fields are free text**, local display strings with no year and no timezone ("Jul-27 5:30 PM"). Only the project, generic-event and UDF layers use typed epoch-millisecond dates.
- **Page with `resultRecordCount` (max 2000) and `resultOffset`** whenever `exceededTransferLimit` is true.
- **Do not invent Green Button endpoints.** EPCOR publishes no base URI, no ESPI/NAESB version, no OAuth metadata and no scope list. Access requires vendor approval plus per-customer consent.
- **Nothing here is licensed.** EPCOR publishes no terms of use, licence, attribution requirement, rate limit or SLA for the feature services.

## Artifacts in this repo

- [apis.yml](https://raw.githubusercontent.com/api-evangelist/epcor/refs/heads/main/apis.yml)
- [review.yml](https://raw.githubusercontent.com/api-evangelist/epcor/refs/heads/main/review.yml) - every URL probed with its HTTP status
- conventions/, errors/, authentication/, conformance/, lifecycle/, data-model/, security/, well-known/, packages/, skills/, examples/