Hydro Ottawa

Hydro Ottawa Holding Inc. is a private corporation 100 percent owned by the City of Ottawa, and the parent of Hydro Ottawa Limited — the regulated local distribution company (LDC) that delivers electricity to roughly 372,000 customers in Ottawa and Casselman, Ontario — alongside Portage Power (Ontario's largest municipally-owned renewable generator, with run-of-river hydroelectric plants at Chaudière Falls and elsewhere in Ontario, Quebec and New York plus solar installations across Ottawa), Envari (energy solutions) and Hiboo Networks (fibre). It sits at the wires-and-meter end of the Canadian value chain: it does not run the market — that is IESO — and it is not a competitive retailer, it is the monopoly distributor that owns the smart meter, the interval data and the billing relationship. Its API posture exists because Ontario legislated it. Ontario Regulation 633/21 (Energy Data) under the Electricity Act, 1998 compels roughly sixty electricity and natural gas utilities in the province to implement Green Button Download My Data and Green Button Connect My Data to the NAESB REQ.21 ESPI v3.3 standard and to have those implementations certified by the Green Button Alliance — a province-level, standard-specific consumer data mandate with no Canadian national equivalent. Hydro Ottawa states on its own site that it offers both services free of charge and that third parties must complete its onboarding process and certify with the GBA. Two live surfaces back that up: a customer Green Button authorization portal at https://hydroottawa.savagedata.com/Connect/Authorize (HTTP 200) and an anonymously reachable third-party developer registration application at https://ottawaonboarding.savagedata.com/ (HTTP 200), both operated by the North Bay vendor Savage Data Systems. What could NOT be verified is the thing the mandate actually requires: no ESPI base URI is published anywhere, the vendor host is a catch-all Blazor SPA that returns HTTP 200 with identical HTML for every path including invented ones, no OpenID Connect discovery document is served anonymously, and no public Green Button Alliance certificate register listing Hydro Ottawa by name could be found. The mandate is recorded here as claimed-and-plausibly- operating, not as verified. Everything else is closed: hydroottawa.com returns 404 for /developers, /api, /docs, /data, /openapi.json and /swagger.json; developers.hydroottawa.com does not resolve and developersdev.hydroottawa.com answers HTTP 530 through Cloudflare; api.hydroottawa.com exists but returns 403 at root and 404 on every path; the github.com/hydroottawa organization has existed since 2015 with zero public repositories; and the City of Ottawa open data portal carries 682 datasets, none of them Hydro Ottawa's. The one genuinely open, anonymous, machine-readable feed carrying Hydro Ottawa data — live outage counts under the KUBRA StormCenter instance behind outages.hydroottawa.com — is undocumented vendor infrastructure that Hydro Ottawa does not publish as a product, and it is deliberately not listed as an API here. Hydro Ottawa is therefore a utility with a mandated consumer data API it does not document, and no open market data at all.

Hydro Ottawa publishes 4 API contracts indexed on the APIs.io network, including Application Information API, Authorization API, Batch API, and 1 more. Tagged areas include Energy, Canada, Ontario, Utilities, and Electricity.

The Hydro Ottawa catalog on APIs.io includes 1 Spectral governance ruleset.

Hydro Ottawa’s developer surface includes authentication, getting-started guide, signup flow, engineering blog, documentation, support, YouTube channel, and 23 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

26.5/100 thin ▬ flat Agent 27/100 agent aware Front door AI 1/6 silent Heartbeat 99/100 alive saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

AccessSelf serve

1 published contract 2 Agent Skills

Energy Canada Ontario Utilities Electricity Electricity Distribution Smart Metering Green Button ESPIMunicipal UtilityRenewables Hydroelectric Solar Demand Response Grid

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 26.5/100 · thin

Contract Quality 2.4 / 21

Developer Ergonomics 5.2 / 17

Access Clarity 3.6 / 17

Operational Transparency 2.0 / 11

Contract Governance 1.9 / 10

Discoverability 4.9 / 9

Regulatory Posture 5.2 / 15

Agent readiness — 27/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 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 0 / 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 6 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

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/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/hydro-ottawa/"><img src="https://apis.io/badge/hydro-ottawa/card.svg" alt="Hydro Ottawa on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document

5 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Quality scores 11.1 — up to +22.2 composite points
Access Clarity scores 21.1 — up to +15.8 composite points
Developer Ergonomics scores 30.4 — up to +13.9 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

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 the provider profile at artifacts.apis.io/hydro-ottawa/apis.yml: open an issue on github.com/api-evangelist/hydro-ottawa to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Standards implemented 3

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

Green Button

tagged — the provider's own APIs.json carries the standard as a tag; implementation not verified

OpenAPI

measured — observed by APIs.io (published)

OAuth 2.0

measured — observed by APIs.io (declared)

APIs 4

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

Hydro Ottawa Application Information API

Application Information endpoints

Hydro Ottawa Authorization API

Authorization endpoints

Hydro Ottawa Batch API

Batch data transfer endpoints

Hydro Ottawa Usage Point API

Usage Point endpoints

Open Collections 1

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

Green Button API Documentation

OPEN COLLECTION

Agent Skills 2

Packaged agent skills for driving this provider's APIs from an AI assistant.

Onboard as a Hydro Ottawa Green Button third party

AGENT SKILL

Retrieve a customer's Green Button usage data from Hydro Ottawa

AGENT SKILL

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Hydro Ottawa API Rules

62 rules · 60 errors 1 warnings 1 info

SPECTRAL

OpenAPI Overlays 1

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

Hydro Ottawa Green Button Espi Overlay

5 actions · update · hydro-ottawa-green-button-espi-openapi.yml

DERIVED

Security Posture 2

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

Hydro Ottawa Authentication

oauth2 · 1 scheme

SECURITY

Hydro Ottawa Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Hydro Ottawa Scopes

OAuth 2.0 · no documented scopes

0 scopes

SCOPES

Resources

Get Started 3

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

SignUp

SignUp

Documentation 1

Reference material describing how the API behaves

Documentation

Documentation

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

WellKnown

WellKnown

LLMsTxt

LLMsTxt

AgentSkill

AgentSkill

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Conformance

ErrorCatalog

Lifecycle

Conventions

DataModel

Build 2

SDKs, sample code, and the tooling you integrate with

Packages

Packages

GitHubOrganization

GitHubOrganization

Access & Security 3

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

OAuthScopes

OAuthScopes

Authentication

Authentication

Learn 1

Tutorials, courses, talks, and written guidance

YouTube

YouTube

Operate 2

Status, limits, changes, and where to get help

Support

Support

StatusPage

StatusPage

Commercial 2

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 6

The organization behind the API

Website

Website

Blog

BlogRSS

LinkedIn

Bluesky

Bluesky

Other 2

Properties that don't map to a standard resource type

Overlay

Overlay

Registration

Registration

Source (apis.yml)

aid: hydro-ottawa
url: https://raw.githubusercontent.com/api-evangelist/hydro-ottawa/refs/heads/main/apis.yml
name: Hydro Ottawa
kind: company
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  gated: none
  gated_source:
  - onboarding
  label: Self-serve signup
  confidence: low
  source:
  - authentication
  - security
  generated: '2026-11-06'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
tags:
- Energy
- Canada
- Ontario
- Utilities
- Electricity
- Electricity Distribution
- Smart Metering
- Green Button
- ESPI
- Municipal Utility
- Renewables
- Hydroelectric
- Solar
- Demand Response
- Grid
created: '2026-07-27'
modified: '2026-07-27'
specificationVersion: '0.23'
description: 'Hydro Ottawa Holding Inc. is a private corporation 100 percent owned by the City of Ottawa, and the parent of
  Hydro Ottawa Limited — the regulated local distribution company (LDC) that delivers electricity to roughly 372,000 customers
  in Ottawa and Casselman, Ontario — alongside Portage Power (Ontario''s largest municipally-owned renewable generator, with
  run-of-river hydroelectric plants at Chaudière Falls and elsewhere in Ontario, Quebec and New York plus solar installations
  across Ottawa), Envari (energy solutions) and Hiboo Networks (fibre). It sits at the wires-and-meter end of the Canadian
  value chain: it does not run the market — that is IESO — and it is not a competitive retailer, it is the monopoly distributor
  that owns the smart meter, the interval data and the billing relationship. Its API posture exists because Ontario legislated
  it. Ontario Regulation 633/21 (Energy Data) under the Electricity Act, 1998 compels roughly sixty electricity and natural
  gas utilities in the province to implement Green Button Download My Data and Green Button Connect My Data to the NAESB REQ.21
  ESPI v3.3 standard and to have those implementations certified by the Green Button Alliance — a province-level, standard-specific
  consumer data mandate with no Canadian national equivalent. Hydro Ottawa states on its own site that it offers both services
  free of charge and that third parties must complete its onboarding process and certify with the GBA. Two live surfaces back
  that up: a customer Green Button authorization portal at https://hydroottawa.savagedata.com/Connect/Authorize (HTTP 200)
  and an anonymously reachable third-party developer registration application at https://ottawaonboarding.savagedata.com/
  (HTTP 200), both operated by the North Bay vendor Savage Data Systems. What could NOT be verified is the thing the mandate
  actually requires: no ESPI base URI is published anywhere, the vendor host is a catch-all Blazor SPA that returns HTTP 200
  with identical HTML for every path including invented ones, no OpenID Connect discovery document is served anonymously,
  and no public Green Button Alliance certificate register listing Hydro Ottawa by name could be found. The mandate is recorded
  here as claimed-and-plausibly- operating, not as verified. Everything else is closed: hydroottawa.com returns 404 for /developers,
  /api, /docs, /data, /openapi.json and /swagger.json; developers.hydroottawa.com does not resolve and developersdev.hydroottawa.com
  answers HTTP 530 through Cloudflare; api.hydroottawa.com exists but returns 403 at root and 404 on every path; the github.com/hydroottawa
  organization has existed since 2015 with zero public repositories; and the City of Ottawa open data portal carries 682 datasets,
  none of them Hydro Ottawa''s. The one genuinely open, anonymous, machine-readable feed carrying Hydro Ottawa data — live
  outage counts under the KUBRA StormCenter instance behind outages.hydroottawa.com — is undocumented vendor infrastructure
  that Hydro Ottawa does not publish as a product, and it is deliberately not listed as an API here. Hydro Ottawa is therefore
  a utility with a mandated consumer data API it does not document, and no open market data at all.'
apis:
- aid: hydro-ottawa:hydro-ottawa-applicationinformation-api
  name: Hydro Ottawa Application Information API
  description: Application Information endpoints
  humanURL: https://hydroottawa.com/en/residential/rates-billing/track-your-usage/green-button
  tags:
  - ApplicationInformation
  properties:
  - type: OpenAPI
    url: openapi/hydro-ottawa-applicationinformation-api-openapi.yml
  - type: Documentation
    url: https://hydroottawa.com/en/residential/rates-billing/track-your-usage/green-button
  - type: Documentation
    url: https://hydroottawa.com/en/accounts-services/services/green-button/green-button-and-third-party-registration
  - type: Registration
    url: https://ottawaonboarding.savagedata.com/
  - type: Authentication
    url: https://hydroottawa.savagedata.com/Connect/Authorize
  - type: Certification
    url: https://www.greenbuttonalliance.org/testing
  - type: Documentation
    url: https://www.canlii.org/en/on/laws/regu/o-reg-633-21/latest/o-reg-633-21.html
  - type: Documentation
    url: https://www.oeb.ca/sites/default/files/OEB-Staff-Guidance-for-Implementation-of-Green-Button-20211101.pdf
- aid: hydro-ottawa:hydro-ottawa-authorization-api
  name: Hydro Ottawa Authorization API
  description: Authorization endpoints
  humanURL: https://hydroottawa.com/en/residential/rates-billing/track-your-usage/green-button
  tags:
  - Authorization
  properties:
  - type: OpenAPI
    url: openapi/hydro-ottawa-authorization-api-openapi.yml
  - type: Documentation
    url: https://hydroottawa.com/en/residential/rates-billing/track-your-usage/green-button
  - type: Documentation
    url: https://hydroottawa.com/en/accounts-services/services/green-button/green-button-and-third-party-registration
  - type: Registration
    url: https://ottawaonboarding.savagedata.com/
  - type: Authentication
    url: https://hydroottawa.savagedata.com/Connect/Authorize
  - type: Certification
    url: https://www.greenbuttonalliance.org/testing
  - type: Documentation
    url: https://www.canlii.org/en/on/laws/regu/o-reg-633-21/latest/o-reg-633-21.html
  - type: Documentation
    url: https://www.oeb.ca/sites/default/files/OEB-Staff-Guidance-for-Implementation-of-Green-Button-20211101.pdf
- aid: hydro-ottawa:hydro-ottawa-batch-api
  name: Hydro Ottawa Batch API
  description: Batch data transfer endpoints
  humanURL: https://hydroottawa.com/en/residential/rates-billing/track-your-usage/green-button
  tags:
  - Batch
  properties:
  - type: OpenAPI
    url: openapi/hydro-ottawa-batch-api-openapi.yml
  - type: Documentation
    url: https://hydroottawa.com/en/residential/rates-billing/track-your-usage/green-button
  - type: Documentation
    url: https://hydroottawa.com/en/accounts-services/services/green-button/green-button-and-third-party-registration
  - type: Registration
    url: https://ottawaonboarding.savagedata.com/
  - type: Authentication
    url: https://hydroottawa.savagedata.com/Connect/Authorize
  - type: Certification
    url: https://www.greenbuttonalliance.org/testing
  - type: Documentation
    url: https://www.canlii.org/en/on/laws/regu/o-reg-633-21/latest/o-reg-633-21.html
  - type: Documentation
    url: https://www.oeb.ca/sites/default/files/OEB-Staff-Guidance-for-Implementation-of-Green-Button-20211101.pdf
- aid: hydro-ottawa:hydro-ottawa-usagepoint-api
  name: Hydro Ottawa Usage Point API
  description: Usage Point endpoints
  humanURL: https://hydroottawa.com/en/residential/rates-billing/track-your-usage/green-button
  tags:
  - UsagePoint
  properties:
  - type: OpenAPI
    url: openapi/hydro-ottawa-usagepoint-api-openapi.yml
  - type: Documentation
    url: https://hydroottawa.com/en/residential/rates-billing/track-your-usage/green-button
  - type: Documentation
    url: https://hydroottawa.com/en/accounts-services/services/green-button/green-button-and-third-party-registration
  - type: Registration
    url: https://ottawaonboarding.savagedata.com/
  - type: Authentication
    url: https://hydroottawa.savagedata.com/Connect/Authorize
  - type: Certification
    url: https://www.greenbuttonalliance.org/testing
  - type: Documentation
    url: https://www.canlii.org/en/on/laws/regu/o-reg-633-21/latest/o-reg-633-21.html
  - type: Documentation
    url: https://www.oeb.ca/sites/default/files/OEB-Staff-Guidance-for-Implementation-of-Green-Button-20211101.pdf
common:
- type: Overlay
  url: overlays/hydro-ottawa-green-button-espi-overlay.yaml
- type: DomainSecurity
  url: security/hydro-ottawa-domain-security.yml
- type: OAuthScopes
  url: scopes/hydro-ottawa-scopes.yml
- type: Authentication
  url: authentication/hydro-ottawa-authentication.yml
- type: Packages
  url: packages/hydro-ottawa-packages.yml
- type: WellKnown
  url: well-known/hydro-ottawa-well-known.yml
- type: LLMsTxt
  url: llms/hydro-ottawa-llms.txt
- type: Conformance
  url: conformance/hydro-ottawa-conformance.yml
- type: ErrorCatalog
  url: errors/hydro-ottawa-problem-types.yml
- type: Lifecycle
  url: lifecycle/hydro-ottawa-lifecycle.yml
- type: Conventions
  url: conventions/hydro-ottawa-conventions.yml
- type: DataModel
  url: data-model/hydro-ottawa-data-model.yml
- type: AgentSkill
  url: skills/_index.yml
- type: Website
  url: https://hydroottawa.com/
- type: Website
  url: https://hydroottawagroup.com/
- type: DeveloperPortal
  url: https://ottawaonboarding.savagedata.com/
- type: GettingStarted
  url: https://hydroottawa.com/en/accounts-services/services/green-button/green-button-and-third-party-registration
- type: SignUp
  url: https://ottawaonboarding.savagedata.com/
- type: Blog
  url: https://hydroottawa.com/en/about-us/blogs-articles
- type: BlogRSS
  url: https://hydroottawa.com/en/rss.xml
- type: TermsOfService
  url: https://hydroottawa.com/en/about-us/policies-and-terms/terms-use
- type: PrivacyPolicy
  url: https://hydroottawa.com/en/about-us/policies-and-terms/privacy-notice
- type: Documentation
  url: https://hydroottawa.com/en/residential/rates-billing/track-your-usage/green-button
- type: Registration
  url: https://ottawaonboarding.savagedata.com/
- type: Support
  url: https://hydroottawa.com/en/faq
- type: StatusPage
  url: https://outages.hydroottawa.com/
- type: GitHubOrganization
  url: https://github.com/hydroottawa
- type: LinkedIn
  url: https://www.linkedin.com/company/hydro-ottawa
- type: Bluesky
  url: https://bsky.app/profile/hydroottawa.bsky.social
- type: YouTube
  url: https://www.youtube.com/user/hydroottawalimited/
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

Hydro Ottawa API — frequently asked questions

Does Hydro Ottawa have an API?

Yes. APIs.io lists 4 APIs from Hydro Ottawa, including Hydro Ottawa Application Information API, Hydro Ottawa Authorization API and Hydro Ottawa Batch API, and 1 more.

Is there an OpenAPI specification for the Hydro Ottawa API?

Yes. APIs.io indexes 4 OpenAPI specifications for Hydro Ottawa, each linked for download from this page.

How do I authenticate with the Hydro Ottawa API?

Hydro Ottawa documents its authentication (oauth2 · 1 scheme). The details are profiled on APIs.io as Hydro Ottawa Authentication.

Is the Hydro Ottawa API ready for AI agents?

Hydro Ottawa has a Kin Score of 26.5 out of 100 (thin) and an Agent Readiness score of 27.4 (agent-aware), scored by API Evangelist on 2026-11-06.

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/hydro-ottawa"

All providers

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

Every operation they expose

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

How their score was established

curl "https://apis.io/api/v1/providers/hydro-ottawa/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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.