EPCOR

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.

EPCOR publishes 7 APIs on the APIs.io network, including Boundaries API, Catalog API, Infrastructure API, and 4 more. Tagged areas include Energy, Canada, Utilities, Electricity, and Natural Gas.

EPCOR’s developer surface includes authentication, developer portal, support, engineering blog, and 24 more developer resources.

🌐 Visit website 📡 Source on GitHub

36.4/100 thin ▬ flat Agent 26/100 agent aware saas Full breakdown ↓
scored 2026-09-08 · rubric v0.20.0

1 APIs

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

Kin Score

Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0

Composite quality — 36.4/100 · thin

Contract Quality 4.2 / 21

Developer Ergonomics 6.8 / 17

Access Clarity 5.8 / 17

Operational Transparency 1.7 / 11

Contract Governance 1.9 / 10

Discoverability 5.7 / 9

Regulatory Posture 8.6 / 15

Agent readiness — 26/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 6 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 9 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 7 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 4 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Regulatory Posture applies to this provider. Its tags matched the Energy & Utilities regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics does not apply to this provider. The published contracts declare no write operations, and a read-only API cannot create-or-update. The facet is excluded from this provider's denominator entirely — not scored zero. A reference or data API is not deficient for being unable to upsert.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/epcor: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 8

Individual APIs this provider publishes, each with its own machine-readable definition.

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 Boundaries API

Municipal boundary reference layers.

EPCOR Catalog API

Service directory.

EPCOR Infrastructure API

Water infrastructure construction projects.

EPCOR Power Outages API

Edmonton electricity distribution outages (active, planned and point features).

EPCOR Service Areas API

EPCOR Water USA service area boundaries.

EPCOR Us Water Outages API

EPCOR Water USA district outage points (Arizona and New Mexico).

EPCOR Water Outages API

Canadian water outages, main breaks and field events.

Scroll for all 8

Open Collections 1

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

EPCOR Public Outage and Service Area Feature Services (ArcGIS REST)

OPEN COLLECTION

JSON Schema 1

Standalone JSON Schema definitions for this provider's data models.

EPCOR public feature layer attributes

0 properties

JSON SCHEMA

Examples 6

Example request and response payloads for these APIs.

Epcor Arcgis Error Responses

5 fields

EXAMPLE

Epcor Arcgis Service Directory

2 fields

EXAMPLE

Epcor Outage Map Config

1 fields

EXAMPLE

Epcor Power Outage Areas Geojson

3 fields

EXAMPLE

Epcor Power Outage Areas Query

10 fields

EXAMPLE

Epcor Water Canada Outages Query

8 fields

EXAMPLE

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Epcor Authentication

none/delegated-consent · 4 schemes

SECURITY

Epcor Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Epcor Agentic Access

115 operations

115 operations · 0 acting

AGENTIC

Resources

Get Started 1

Portal, sign-up, and the first successful call

Portal

Portal

Agent Surfaces 6

MCP servers, agent skills, and machine-readable catalogs

AgentSkill

AgentSkill

AgentSkill

AgenticAccess

LLMsTxt

AgentSkill

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Conventions

ErrorCatalog

Lifecycle

Conformance

DataModel

Build 1

SDKs, sample code, and the tooling you integrate with

Packages

Packages

Access & Security 2

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Authentication

Authentication

Operate 2

Status, limits, changes, and where to get help

StatusPage

StatusPage

Support

Support

Commercial 2

Pricing, plans, and the legal terms of use

PrivacyPolicy

PrivacyPolicy

TermsOfService

TermsOfService

Company 9

The organization behind the API

Website

Website

Website

Website

Website

Website

LinkedIn

Twitter

Facebook

Instagram

Blog

About

Scroll for all 9

Source (apis.yml)

aid: epcor
url: https://raw.githubusercontent.com/api-evangelist/epcor/refs/heads/main/apis.yml
name: EPCOR
kind: company
description: '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.'
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - security
  generated: '2026-09-03'
  method: derived
image: https://www.epcor.com/content/dam/epcor/images/dm-images/logos-and-icons/epcor-logo.png
tags:
- Energy
- Canada
- Utilities
- Electricity
- Natural Gas
- Water
- Green Button
- Smart Metering
- Grid
- Ontario
- Alberta
- Outages
- Geospatial
- Open Data
created: '2026-07-27'
modified: '2026-07-27'
specificationVersion: '0.23'
apis:
- aid: epcor:epcor-ontario-green-button
  name: EPCOR Ontario Green Button (Download My Data / Connect My Data)
  description: 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 Ontario's O. Reg. 633/21. Download My Data lets an authenticated
    EPCOR customer download usage and billing data in an industry-standard XML format from the Green Button portal; Connect
    My Data ("Data Shares") lets a customer authorize a registered third-party vendor to receive energy usage data, billing
    data and/or account information on an ongoing basis via security tokens, with revocation from the portal's Data Shares
    tab. EPCOR states it has been certified by the Green Button Alliance. EPCOR publishes no technical documentation, no base
    URI, no ESPI/NAESB version reference and no machine-readable contract for this interface - a third party must apply through
    the vendor onboarding portal, and the customer-facing portal redirects every path to a login, so no endpoint could be
    verified anonymously. Not offered in EPCOR's Alberta or US service areas.
  humanURL: https://www.epcor.com/ca/en/on/collingwood-area/account/manage-account/green-button.html
  tags:
  - Energy
  - Green Button
  - Consumer Data
  - Electricity
  - Natural Gas
  - Ontario
  properties:
  - type: Documentation
    url: https://www.epcor.com/ca/en/on/collingwood-area/account/manage-account/green-button.html
  - type: Documentation
    url: https://www.epcor.com/ca/en/on/aylmer-area/account/manage-account/green-button.html
  - type: Documentation
    url: https://www.epcor.com/ca/en/on/kincardine-area/account/manage-account/green-button.html
  - type: Portal
    url: https://epcorgas.savagedata.com/
  - type: Registration
    url: https://epcorgasonboarding.savagedata.com/
  - type: Standard
    url: https://www.greenbuttonalliance.org/
  - type: Regulation
    url: https://www.oeb.ca/consumer-information-and-protection/green-button
  - type: AgentSkill
    url: skills/epcor-request-ontario-green-button-data.md
- aid: epcor:epcor-boundaries-api
  name: EPCOR Boundaries API
  description: Municipal boundary reference layers.
  humanURL: https://www.epcor.com/ca/en/on/collingwood-area/account/manage-account/green-button.html
  baseURL: https://services6.arcgis.com/Ji2rusuWXDFSqNsP/ArcGIS/rest/services
  tags:
  - Boundaries
  tags_raw:
  - boundaries
  properties:
  - type: OpenAPI
    url: openapi/epcor-boundaries-api-openapi.yml
  - type: JSONSchema
    url: json-schema/epcor-outage-features.schema.json
  - type: Examples
    url: examples/epcor-power-outage-areas-query.json
  - type: Examples
    url: examples/epcor-arcgis-service-directory.json
  - type: Examples
    url: examples/epcor-water-canada-outages-query.json
  - type: Portal
    url: https://outages.epcor.com/
  - type: Standard
    url: https://developers.arcgis.com/rest/services-reference/enterprise/query-feature-service-layer/
- aid: epcor:epcor-catalog-api
  name: EPCOR Catalog API
  description: Service directory.
  humanURL: https://www.epcor.com/ca/en/on/collingwood-area/account/manage-account/green-button.html
  baseURL: https://services6.arcgis.com/Ji2rusuWXDFSqNsP/ArcGIS/rest/services
  tags:
  - Catalog
  tags_raw:
  - catalog
  properties:
  - type: OpenAPI
    url: openapi/epcor-catalog-api-openapi.yml
  - type: JSONSchema
    url: json-schema/epcor-outage-features.schema.json
  - type: Examples
    url: examples/epcor-power-outage-areas-query.json
  - type: Examples
    url: examples/epcor-arcgis-service-directory.json
  - type: Examples
    url: examples/epcor-water-canada-outages-query.json
  - type: Portal
    url: https://outages.epcor.com/
  - type: Standard
    url: https://developers.arcgis.com/rest/services-reference/enterprise/query-feature-service-layer/
- aid: epcor:epcor-infrastructure-api
  name: EPCOR Infrastructure API
  description: Water infrastructure construction projects.
  humanURL: https://www.epcor.com/ca/en/on/collingwood-area/account/manage-account/green-button.html
  baseURL: https://services6.arcgis.com/Ji2rusuWXDFSqNsP/ArcGIS/rest/services
  tags:
  - Infrastructure
  tags_raw:
  - infrastructure
  properties:
  - type: OpenAPI
    url: openapi/epcor-infrastructure-api-openapi.yml
  - type: JSONSchema
    url: json-schema/epcor-outage-features.schema.json
  - type: Examples
    url: examples/epcor-power-outage-areas-query.json
  - type: Examples
    url: examples/epcor-arcgis-service-directory.json
  - type: Examples
    url: examples/epcor-water-canada-outages-query.json
  - type: Portal
    url: https://outages.epcor.com/
  - type: Standard
    url: https://developers.arcgis.com/rest/services-reference/enterprise/query-feature-service-layer/
- aid: epcor:epcor-power-outages-api
  name: EPCOR Power Outages API
  description: Edmonton electricity distribution outages (active, planned and point features).
  humanURL: https://www.epcor.com/ca/en/on/collingwood-area/account/manage-account/green-button.html
  baseURL: https://services6.arcgis.com/Ji2rusuWXDFSqNsP/ArcGIS/rest/services
  tags:
  - power-outages
  properties:
  - type: OpenAPI
    url: openapi/epcor-power-outages-api-openapi.yml
  - type: JSONSchema
    url: json-schema/epcor-outage-features.schema.json
  - type: Examples
    url: examples/epcor-power-outage-areas-query.json
  - type: Examples
    url: examples/epcor-arcgis-service-directory.json
  - type: Examples
    url: examples/epcor-water-canada-outages-query.json
  - type: Portal
    url: https://outages.epcor.com/
  - type: Standard
    url: https://developers.arcgis.com/rest/services-reference/enterprise/query-feature-service-layer/
- aid: epcor:epcor-service-areas-api
  name: EPCOR Service Areas API
  description: EPCOR Water USA service area boundaries.
  humanURL: https://www.epcor.com/ca/en/on/collingwood-area/account/manage-account/green-button.html
  baseURL: https://services6.arcgis.com/Ji2rusuWXDFSqNsP/ArcGIS/rest/services
  tags:
  - Service Areas
  tags_raw:
  - service-areas
  properties:
  - type: OpenAPI
    url: openapi/epcor-service-areas-api-openapi.yml
  - type: JSONSchema
    url: json-schema/epcor-outage-features.schema.json
  - type: Examples
    url: examples/epcor-power-outage-areas-query.json
  - type: Examples
    url: examples/epcor-arcgis-service-directory.json
  - type: Examples
    url: examples/epcor-water-canada-outages-query.json
  - type: Portal
    url: https://outages.epcor.com/
  - type: Standard
    url: https://developers.arcgis.com/rest/services-reference/enterprise/query-feature-service-layer/
- aid: epcor:epcor-us-water-outages-api
  name: EPCOR Us Water Outages API
  description: EPCOR Water USA district outage points (Arizona and New Mexico).
  humanURL: https://www.epcor.com/ca/en/on/collingwood-area/account/manage-account/green-button.html
  baseURL: https://services6.arcgis.com/Ji2rusuWXDFSqNsP/ArcGIS/rest/services
  tags:
  - us-water-outages
  properties:
  - type: OpenAPI
    url: openapi/epcor-us-water-outages-api-openapi.yml
  - type: JSONSchema
    url: json-schema/epcor-outage-features.schema.json
  - type: Examples
    url: examples/epcor-power-outage-areas-query.json
  - type: Examples
    url: examples/epcor-arcgis-service-directory.json
  - type: Examples
    url: examples/epcor-water-canada-outages-query.json
  - type: Portal
    url: https://outages.epcor.com/
  - type: Standard
    url: https://developers.arcgis.com/rest/services-reference/enterprise/query-feature-service-layer/
- aid: epcor:epcor-water-outages-api
  name: EPCOR Water Outages API
  description: Canadian water outages, main breaks and field events.
  humanURL: https://www.epcor.com/ca/en/on/collingwood-area/account/manage-account/green-button.html
  baseURL: https://services6.arcgis.com/Ji2rusuWXDFSqNsP/ArcGIS/rest/services
  tags:
  - water-outages
  properties:
  - type: OpenAPI
    url: openapi/epcor-water-outages-api-openapi.yml
  - type: JSONSchema
    url: json-schema/epcor-outage-features.schema.json
  - type: Examples
    url: examples/epcor-power-outage-areas-query.json
  - type: Examples
    url: examples/epcor-arcgis-service-directory.json
  - type: Examples
    url: examples/epcor-water-canada-outages-query.json
  - type: Portal
    url: https://outages.epcor.com/
  - type: Standard
    url: https://developers.arcgis.com/rest/services-reference/enterprise/query-feature-service-layer/
common:
- type: AgentSkill
  url: skills/epcor-check-edmonton-power-outages.md
- type: AgentSkill
  url: skills/epcor-track-water-outages-and-projects.md
- type: AgentSkill
  url: skills/epcor-map-us-water-districts.md
- type: AgenticAccess
  url: agentic-access/epcor-agentic-access.yml
- type: DomainSecurity
  url: security/epcor-domain-security.yml
- type: Authentication
  url: authentication/epcor-authentication.yml
- type: Conventions
  url: conventions/epcor-conventions.yml
- type: ErrorCatalog
  url: errors/epcor-problem-types.yml
- type: Lifecycle
  url: lifecycle/epcor-lifecycle.yml
- type: Conformance
  url: conformance/epcor-conformance.yml
- type: DataModel
  url: data-model/epcor-data-model.yml
- type: Packages
  url: packages/epcor-packages.yml
- type: LLMsTxt
  url: llms/epcor-llms.txt
- type: AgentSkill
  url: skills/_index.yml
- type: Website
  url: https://www.epcor.com/
- type: Website
  url: https://www.epcor.com/ca/en.html
- type: Website
  url: https://www.epcor.com/us/en.html
- type: LinkedIn
  url: https://www.linkedin.com/company/epcor
- type: Twitter
  url: https://twitter.com/epcor
- type: Facebook
  url: https://www.facebook.com/epcor
- type: Instagram
  url: https://www.instagram.com/epcor
- type: Portal
  url: https://customerportal.epcor.com/app/
- type: StatusPage
  url: https://outages.epcor.com/
- type: Support
  url: https://www.epcor.com/ca/en/ab/edmonton/contact-edmonton.html
- type: Blog
  url: https://www.epcor.com/ca/en/news.html
- type: PrivacyPolicy
  url: https://www.epcor.com/ca/en/about/policies/privacy-policy.html
- type: TermsOfService
  url: https://www.epcor.com/ca/en/about/policies/terms-of-use.html
- type: About
  url: https://www.epcor.com/Pages/about-epcor-ontario.aspx
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/epcor"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/epcor/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/epcor/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.