# EPCOR

**Canonical:** https://apis.io/providers/epcor/  
**Website:** https://www.epcor.com/  
**APIs profiled:** 2

EPCOR Utilities Inc. is a municipally owned Canadian utility headquartered in Edmonton, Alberta, wholly owned by the City of Edmonton, that builds and operates electricity distribution and transmission, water and wastewater, and natural gas distribution systems across Alberta, Ontario and British Columbia in Canada and in Arizona, New Mexico and Texas in the United States. In its Alberta home market it is both a wires company for Edmonton and, through EPCOR Energy Alberta, a regulated-rate electricity retailer, sitting at the distribution-and-retail end of the value chain rather than in generation (generation was spun out as Capital Power in 2009). EPCOR runs no developer programme: epcor.com publishes no developer portal, no API documentation, no OpenAPI and no llms.txt, and the developer., developers., api., docs. and data. subdomains do not resolve. It nonetheless operates two real programmatic surfaces. The first is compelled: the Green Button Download My Data and Connect My Data service its three Ontario service areas - natural gas in the Aylmer area and electricity in the Collingwood and Kincardine areas - must run under Ontario's energy data regulation (O. Reg. 633/21), delivered behind a customer login and a third-party vendor registration portal, with EPCOR stating Green Button Alliance certification but publishing no base URI, no ESPI version and no technical contract. The second is accidental and entirely open: a public ArcGIS Online organization (owner epcor_outages) whose 36 production feature services - Edmonton power outage areas, Canadian water main breaks, water infrastructure projects, scheduled field events, and the outage and service-area layers for fourteen EPCOR Water USA districts in Arizona and New Mexico - answer anonymous ArcGIS REST queries with live data. EPCOR documents none of it, licenses none of it and announces none of it. The result is a utility that is open where a province compelled it, open where nobody noticed, and closed everywhere it would count as a product; wholesale market and system data still comes from AESO and IESO, not from EPCOR.

## Kin Score — 42.9 / 100 (developing)

Scored 2026-08-20 under rubric 0.12.0. Trend: flat (+0.0 from 42.9).

| Facet | Score |
|---|---|
| Discoverability | 77.8 |
| Contract Quality | 57.3 |
| Governance | 18.2 |
| Contract Governance | 18.2 |
| Operational Transparency | 15.8 |
| Developer Ergonomics | 30.4 |
| Commercial Clarity | 21.1 |
| Access Clarity | 21.1 |

Regulatory layer — **Energy & Utilities**: 60.8 (matched via tags).

## Agent readiness — 40.6 (agent-ready)

| Dimension | Value |
|---|---|
| Spec Presence | yes |
| Agentic Access | derived |
| Reversibility Documented | na |
| MCP Server | no |
| Auth Clarity | yes |
| Idempotency | na |
| Error Semantics | documented |
| OpenAPI Examples | no |
| Rate Limit Signal | no |
| Event Surface Described | no |
| Agent Skills | derived |
| Well Known Catalog | yes |
| Consent Identity | no |
| Agent Card | no |
| Dry Run Mode | na |

## APIs (2)

- **EPCOR Ontario Green Button (Download My Data / Connect My Data)** — The Green Button energy-data service EPCOR operates for its three Ontario service areas (Aylmer-area natural gas, Collingwood-area and Kincardine-area electricity) to satisfy On...
- **EPCOR Public Outage and Service Area Feature Services (ArcGIS REST)** — EPCOR's undocumented but fully public geospatial data surface. Its outage map at outages.epcor.com loads its endpoints from a configuration file that points at a publicly shared...

## Agentic access (1)

- **Epcor Agentic Access** — 115 operations

## Security (2)

- **Epcor Authentication** — none/delegated-consent · 4 schemes
- **Epcor Domain Security** — TLSv1.3 · HSTS · DNSSEC · DMARC

## Tags

Energy, Canada, Utilities, Electricity, Natural Gas, Water, Green Button, Smart Metering, Grid, Ontario, Alberta, Outages, Geospatial, Open Data

---

Profiled by [API Evangelist](https://apievangelist.com) and published on [APIs.io](https://apis.io/providers/epcor/). Scores are computed from the provider's own public artifacts under a published rubric.