Hydro One website screenshot

Hydro One

Hydro One Limited (TSX: H) is Canada's largest electricity transmission and distribution service provider, transmitting and distributing electricity across Ontario — the province the company describes as "home to 38 per cent of Canada's population." It sits in the regulated wires tier of the value chain: it owns and operates the provincial transmission grid and a rural/regional distribution network serving roughly 1.5 million customers, while the Ontario market itself is operated by the IESO and rates are set by the Ontario Energy Board. Its API posture is defined entirely by regulation, not by product. Ontario Regulation 633/21 (Energy Data, under the Electricity Act, 1998) compels Ontario electricity and natural gas distributors to implement Green Button Download My Data (DMD) and Connect My Data (CMD) and to have those implementations certified by the Green Button Alliance. Hydro One publishes DMD as an authenticated XML export inside My Account, runs a live Green Button CMD OAuth 2.0 authorization surface at www.hydroone.com/green-button-cmd-home, and operates a published third-party vendor onboarding form and terms and conditions — but the CMD resource base URI, client credentials, and test accounts are issued privately during onboarding and are not published anywhere. There is no developer subdomain, no OpenAPI or Swagger definition, and no self-serve signup. The split is the finding: consumer energy data is available through a real, standards-based, mandated API that a developer can only reach by application and 90-day connectivity testing, while open grid and market data is entirely absent — Hydro One publishes no open data portal and no documented public system or outage API, leaving Ontario market data to the IESO.

Hydro One publishes 1 API on the APIs.io network. Tagged areas include Energy, Canada, Utilities, Electricity, and Grid.

Hydro One’s developer surface includes authentication, sandbox, documentation, getting-started guide, signup flow, support, product news, and 13 more developer resources.

29.8/100 thin ▬ flat Agent 9/100 agent aware Full breakdown ↓
scored 2026-08-20 · rubric v0.12.0
AccessFree
1 APIs
EnergyCanadaUtilitiesElectricityGridSmart MeteringGreen ButtonEnergy DataTransmissionDistribution

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-08-20 · rubric v0.12.0
Composite quality — 29.8/100 · thin
Contract Quality 0.0 / 21
Developer Ergonomics 7.7 / 17
Access Clarity 5.8 / 17
Operational Transparency 0.0 / 11
Contract Governance 1.9 / 10
Discoverability 5.7 / 9
Regulatory Posture 8.0 / 15
Agent readiness — 9/100 · agent aware
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 10
Documented Reversibility 0 / 6
MCP Server 0 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3
A2A Agent Card 0 / 8
Dry-Run / Simulate Mode 0 / 4
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.
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/. This rating is computed from github.com/api-evangelist/hydro-one: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

APIs 1

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

Hydro One Green Button Connect My Data (CMD)

Hydro One's Green Button Connect My Data implementation, mandated by Ontario Regulation 633/21. A registered third-party vendor obtains an OAuth 2.0 authorization code after the...

Security Posture 2

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

Hydro One Authentication

oauth2/mutualTLS · 2 schemes

SECURITY

Hydro One Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Hydro One Scopes

OAuth 2.0 · no documented scopes

0 scopes

SCOPES

Resources

Get Started 3

Portal, sign-up, and the first successful call

Documentation 1

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

Access & Security 3

Authentication, authorization, and security posture

Operate 1

Status, limits, changes, and where to get help

Commercial 3

Pricing, plans, and the legal terms of use

Company 4

The organization behind the API

Other 1

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
aid: hydro-one
url: https://raw.githubusercontent.com/api-evangelist/hydro-one/refs/heads/main/apis.yml
name: Hydro One
kind: company
description: 'Hydro One Limited (TSX: H) is Canada''s largest electricity transmission and distribution service provider,
  transmitting and distributing electricity across Ontario — the province the company describes as "home to 38 per cent of
  Canada''s population." It sits in the regulated wires tier of the value chain: it owns and operates the provincial transmission
  grid and a rural/regional distribution network serving roughly 1.5 million customers, while the Ontario market itself is
  operated by the IESO and rates are set by the Ontario Energy Board. Its API posture is defined entirely by regulation, not
  by product. Ontario Regulation 633/21 (Energy Data, under the Electricity Act, 1998) compels Ontario electricity and natural
  gas distributors to implement Green Button Download My Data (DMD) and Connect My Data (CMD) and to have those implementations
  certified by the Green Button Alliance. Hydro One publishes DMD as an authenticated XML export inside My Account, runs a
  live Green Button CMD OAuth 2.0 authorization surface at www.hydroone.com/green-button-cmd-home, and operates a published
  third-party vendor onboarding form and terms and conditions — but the CMD resource base URI, client credentials, and test
  accounts are issued privately during onboarding and are not published anywhere. There is no developer subdomain, no OpenAPI
  or Swagger definition, and no self-serve signup. The split is the finding: consumer energy data is available through a real,
  standards-based, mandated API that a developer can only reach by application and 90-day connectivity testing, while open
  grid and market data is entirely absent — Hydro One publishes no open data portal and no documented public system or outage
  API, leaving Ontario market data to the IESO.'
accessModel:
  pricing: free
  onboarding: application-approval
  trial: false
  try_now: false
  public: false
  label: Free · Application and approval required
  confidence: high
  source:
  - documentation
  - terms
  generated: '2026-07-27'
  method: manual
image: https://www.hydroone.com/Style%20Library/H1/images/logo.svg
tags:
- Energy
- Canada
- Utilities
- Electricity
- Grid
- Smart Metering
- Green Button
- Energy Data
- Transmission
- Distribution
created: '2026-07-27'
modified: '2026-07-27'
specificationVersion: '0.23'
apis:
- aid: hydro-one:hydro-one-green-button-connect-my-data
  name: Hydro One Green Button Connect My Data (CMD)
  description: Hydro One's Green Button Connect My Data implementation, mandated by Ontario Regulation 633/21. A registered
    third-party vendor obtains an OAuth 2.0 authorization code after the customer authenticates with Hydro One and consents,
    then retrieves that customer's electricity usage and billing data as NAESB ESPI XML. The live authorization surface at
    https://www.hydroone.com/green-button-cmd-home was observed serving a real Green Button authorization request carrying
    ESPI function-block scope syntax (FB=1_3_4_5_13_15_16_31_37_39_51_53_54_55_56_57_58_59_60_64_65;historyLength=32148000)
    for a third-party redirect URI. Hydro One does not publish the CMD resource base URI, an OpenAPI definition, or any endpoint
    reference — Client ID, Client Secret, test accounts, and URI(s) are issued privately during vendor onboarding, followed
    by a 90-day connectivity test and an exchange of RSA 2048-bit certificates over TLS.
  humanURL: https://www.hydroone.com/saving-money-and-energy/green-button/third-party-apps
  tags:
  - Green Button
  - Connect My Data
  - ESPI
  - Energy Data
  - Authentication
  - Consumer Data
  tags_raw:
  - Green Button
  - Connect My Data
  - ESPI
  - Energy Data
  - OAuth2
  - Consumer Data
  properties:
  - type: Documentation
    url: https://www.hydroone.com/saving-money-and-energy/green-button
  - type: Documentation
    url: https://www.hydroone.com/saving-money-and-energy/green-button/third-party-apps
  - type: TermsOfService
    url: https://www.hydroone.com/saving-money-and-energy/green-button/third-party-terms-and-conditions
  - type: SignUp
    url: https://www.hydroone.com/saving-money-and-energy/green-button/third-party-onboarding-form
  - type: GettingStarted
    url: https://www.hydroone.com/saving-money-and-energy/green-button/third-party-apps
  - type: Authentication
    url: https://www.hydroone.com/green-button-cmd-home
  - type: Authentication
    url: authentication/hydro-one-authentication.yml
  - type: OAuthScopes
    url: scopes/hydro-one-scopes.yml
  - type: Sandbox
    url: sandbox/hydro-one-sandbox.yml
  - type: Regulation
    url: https://www.ontario.ca/laws/regulation/210633
  - type: Standard
    url: https://www.greenbuttonalliance.org/
  - type: Regulator
    url: https://www.oeb.ca/consumer-information-and-protection/green-button
common:
- type: DomainSecurity
  url: security/hydro-one-domain-security.yml
- type: Authentication
  url: authentication/hydro-one-authentication.yml
- type: OAuthScopes
  url: scopes/hydro-one-scopes.yml
- type: Conventions
  url: conventions/hydro-one-conventions.yml
- type: Conformance
  url: conformance/hydro-one-conformance.yml
- type: Lifecycle
  url: lifecycle/hydro-one-lifecycle.yml
- type: Sandbox
  url: sandbox/hydro-one-sandbox.yml
- type: LLMsTxt
  url: llms/hydro-one-llms.txt
- type: Website
  url: https://www.hydroone.com/
- type: About
  url: https://www.hydroone.com/about
- type: Documentation
  url: https://www.hydroone.com/saving-money-and-energy/green-button
- type: GettingStarted
  url: https://www.hydroone.com/saving-money-and-energy/green-button/third-party-apps
- type: SignUp
  url: https://www.hydroone.com/saving-money-and-energy/green-button/third-party-onboarding-form
- type: TermsOfService
  url: https://www.hydroone.com/saving-money-and-energy/green-button/third-party-terms-and-conditions
- type: TermsOfUse
  url: https://www.hydroone.com/terms-of-use
- type: PrivacyPolicy
  url: https://www.hydroone.com/privacy
- type: Support
  url: https://www.hydroone.com/contact
- type: News
  url: https://www.hydroone.com/newsroom
- type: LinkedIn
  url: https://www.linkedin.com/company/hydro-one
- type: Regulator
  url: https://www.oeb.ca/consumer-information-and-protection/green-button
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com