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). Its API posture is defined entirely by regulation and nothing else: epcor.com publishes no developer portal, no API documentation and no machine-readable contracts, and the developer., developers., api., docs. and data. subdomains do not resolve. The one programmatic consumer surface is the Green Button implementation its three Ontario service areas - natural gas in the Aylmer area and electricity in the Collingwood and Kincardine areas - are required to run under Ontario's energy data regulation (O. Reg. 633/21), delivered as Download My Data behind a customer login and Connect My Data behind a third-party vendor registration portal, with EPCOR stating Green Button Alliance certification. Its far larger unmandated Alberta business publishes no equivalent, and EPCOR publishes no open grid or market data of its own - Alberta system and market data comes from AESO, not from EPCOR. The result is a utility that is open exactly where a province compelled it and closed everywhere else, with consumer data gated and market data absent.
EPCOR is tracked in the API Evangelist network. This page is the human-readable profile that sits on top of the machine-readable index we maintain at apis.io.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
EPCOR is in the network as a tracked entity. We haven't yet indexed a public API surface for it — when one is published, the artifacts, score, and agent-readiness read will appear here automatically. The source repository is where that profile is built.
← All providers · Data indexed from github.com/api-evangelist/epcor · machine-readable index on apis.io