BC Hydro
British Columbia Hydro and Power Authority (BC Hydro) is a provincial Crown corporation whose sole shareholder is the Province of British Columbia, and which states that it generates and delivers electricity to "95% of the population of B.C." and serves "over five million people." It is the vertically integrated end of the value chain in a market with no retail competition: BC Hydro owns the generation fleet (predominantly large hydroelectric), owns and operates the provincial transmission and distribution system, and is the monopoly retailer that bills the customer — all under rate regulation by the B.C. Utilities Commission (BCUC), not under any consumer data right. That regulatory fact drives the entire API posture. Ontario Regulation 633/21 compels Ontario distributors to implement Green Button Download My Data and Connect My Data; British Columbia has no equivalent, and no Canadian federal energy data mandate exists. BC Hydro has nonetheless adopted Green Button voluntarily — but only the file half of it. BC Hydro's own MyHydro billing pages state that a customer can "Download a CSV or Green Button XML file with your metered electricity use," available through the previous day and up to three years back. There is no Connect My Data, no OAuth authorization surface, no third-party vendor onboarding, and no published resource base URI: a third party cannot obtain a customer's usage data through any documented API, only the account holder can, by logging in and downloading a file. On the market-data side the picture is just as closed. There is no developer.bchydro.com, api.bchydro.com, data.bchydro.com or docs.bchydro.com (all DNS failures), no /developers, /api or /data path, no OpenAPI or Swagger definition anywhere, and no open data portal. Wholesale transmission information is posted to an OATI-hosted OASIS node that only registered transmission customers may use, and the BCUC-ordered transaction-data postings are documents rather than feeds. The single deliberate open-data artifact is one 2013 mapping layer published to the provincial BC Data Catalogue under the org "bc-hydro-and-power-authority." The finding is a utility that is closed on both axes: consumer data exists in a real standard but only as a human-initiated download behind a customer login, and grid/market data is either registration-gated or absent.
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 BC Hydro the way a machine reads it — 3 machine-readable artifacts, 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 — BC Hydro scores 15.1/100 (emerging), with a separate agent-readiness read of 3/100 (human only). 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-10 · rubric v0.20.0
Put this on your own site. The badge is drawn live from BC Hydro'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/bc-hydro/"
title="BC Hydro on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/bc-hydro.svg"
alt="BC Hydro Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/bc-hydro/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/bc-hydro/"
title="BC Hydro on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/bc-hydro/card.svg"
alt="BC Hydro 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 BC Hydro
Each block below is one kind of artifact we hold for BC Hydro. 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.
JSON Schema 1
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.
BC Hydro outage map feed record
JSON SCHEMASecurity 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 BC Hydro — 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.
Documentation 3
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 3
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 5
The organization behind the API
Other 5
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/bc-hydro · machine-readable index on apis.io
This is an independent, third-party profile of BC Hydro, 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.