SaskPower
SaskPower — the Saskatchewan Power Corporation — is the Crown corporation that owns and runs essentially the whole electricity value chain in the province of Saskatchewan, Canada. Established in 1929 as the Saskatchewan Power Commission and continued as the Saskatchewan Power Corporation in 1949 under The Power Corporation Act, it is owned by the provincial government through Crown Investments Corporation and reports to a Minister Responsible rather than to shareholders. It generates, transmits, distributes and retails power to more than 550,000 customers across roughly 652,000 square kilometres on more than 160,000 kilometres of line, from a fleet of coal, natural gas, hydro, wind and solar facilities totalling about 5,437 MW. Unlike Ontario or Alberta there is no competitive wholesale market operator sitting beside it — SaskPower is generator, wires company and retailer at once. Its API posture is the exact inverse of a regulated open-banking-style utility: no consumer energy data mandate applies to it at all. Saskatchewan has no Green Button regulation (Ontario and Nova Scotia do), Canada has no national energy consumer data right, and the Green Button Alliance states plainly that it has no information about any Green Button deployment in Saskatchewan. Smart meter usage data is visible only to the account holder inside MySaskPower behind an Azure AD B2C login; there is no consented third-party data-sharing API, no ESPI/Green Button surface, and no accreditation scheme. What SaskPower does publish — and publishes wide open, anonymously, with no key, no signup and no rate limit — is grid and system data: a live JSON feed of provincial system demand, generation by fuel type, net interchange and historical peak demand behind the public "Where Your Power Comes From" page, a second JSON feed listing current outages by service region, an RSS feed of planned outages, and two KML feeds driving the outage and smart-meter installation maps. None of it is documented as an API, versioned, or covered by a developer program: the former SaskPower ESB developer portal at api-info.saskpower.com no longer resolves, and api.saskpower.com is a live TIBCO/Mashery gateway that answers every public path with ERR_596_SERVICE_NOT_FOUND. Open market data, closed consumer data, and no published door for a developer to knock on.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles SaskPower the way a machine reads it — 11 machine-readable artifacts across 5 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
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. From those artifacts we compute the Kin Score — SaskPower scores 20.2/100 (emerging), with a separate agent-readiness read of 7/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from SaskPower's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/saskpower/"
title="SaskPower on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/saskpower.svg"
alt="SaskPower Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/saskpower/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/saskpower/"
title="SaskPower on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/saskpower/card.svg"
alt="SaskPower Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile SaskPower
Each block below is one kind of artifact we hold for SaskPower. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 5
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
SaskPower Power Use Dashboard Data
The undocumented JSON endpoint behind SaskPower's public "Where Your Power Comes From" page. A single anonymous GET — no key, no signup, no referer check — returns the province'...
SaskPower Planned Outages RSS Feed
A genuinely published, anonymous RSS 2.0 feed of SaskPower's planned power outages, opened by the visible "RSS feed" link on the Outages Planned for Necessary Maintenance page. ...
SaskPower Live Outage JSON Feed
The undocumented JSON endpoint behind SaskPower's public outage map, found in the markup of the Outage Map and Updates page alongside the KML reference and fetched anonymously w...
SaskPower Outage Map KML Feed
The KML data feed behind SaskPower's public outage map, referenced directly in the markup of the Outage Map and Updates page and served anonymously from the outagemap.saskpower....
SaskPower Smart Meter Installation Map KML Feed
The KML data feed behind SaskPower's Smart Meter Installation Map, requested by the site's own SP.scripts.js bundle and served anonymously from the Sitecore content handler. It ...
JSON Schema 2
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
SaskPower Live Outage JSON Feed
JSON SCHEMASaskPower Power Use Dashboard Data
JSON SCHEMAExamples 2
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for SaskPower — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 2
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 4
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 2
Status, limits, changes, and where to get help
Commercial 5
Pricing, plans, and the legal terms of use
Company 4
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/saskpower · machine-readable index on apis.io
This is an independent, third-party profile of SaskPower, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.