Alectra Utilities

Alectra Utilities Corporation is Ontario's second-largest municipally owned electricity distributor and one of the largest local distribution companies (LDCs) in Canada, serving roughly one million customers across seventeen communities in the Greater Toronto and Hamilton Area and the Golden Horseshoe — Alliston, Aurora, Barrie, Beeton, Bradford West Gwillimbury, Brampton, Guelph, Hamilton, Markham, Mississauga, Penetanguishene, Richmond Hill, Rockwood, St. Catharines, Thornton, Tottenham and Vaughan. It also bills water and wastewater/stormwater on behalf of several of those municipalities, and runs the GRE&T Centre for grid innovation. It sits squarely in the wires and metering layer of the Canadian value chain: it does not generate, it does not operate the market (the IESO does), and it is owned by its municipal shareholders rather than by investors — the Crown/municipal ownership pattern that dominates Canadian electricity. Its API posture exists only because a regulator created it. Ontario Regulation 633/21 (Energy Data) requires every Ontario electric and gas utility to implement Green Button Download My Data and Connect My Data to the NAESB REQ.21 ESPI v3.3 standard and to obtain Green Button Alliance certification, with an implementation deadline of 1 November 2023. Alectra publishes a Green Button page displaying GBA Certified DMD and CMD marks, a Green Button Connect My Data Terms and Conditions of Access and Use citing O. Reg. 633/21 by name, a live customer Green Button portal, and a live third-party registration and onboarding site — all three hosted by its data custodian vendor, Savage Data Systems, not by Alectra. What Alectra does not publish is any of the things that would let an outsider verify the implementation: there is no developer portal, no API documentation, no base URI, no OpenAPI, no scopes and no OAuth metadata anywhere on alectrautilities.com or on the portal host. developer., developers., docs. and data.alectrautilities.com do not resolve; /developers, /api, /docs, /data, /openapi.json and /swagger.json all return HTTP 404. Every path on the Green Button portal — including a deliberately invented control path — HTTP 302 redirects to a customer sign-in, so no endpoint could be confirmed. The resulting split is the finding: a mandated consumer-data API that a third party can reach only by completing an application and being approved, and zero open market or grid data of any kind, because in Ontario that layer belongs to the IESO and the OEB rather than to the distributor.

Alectra Utilities 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, Utilities, Electricity, and Ontario.

The Alectra Utilities catalog on APIs.io includes 1 Spectral governance ruleset.

Alectra Utilities’ developer surface includes documentation, developer portal, support, engineering blog, and 16 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

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

AccessSelf serve

1 published contract 3 Agent Skills

Energy Canada Utilities Electricity Ontario Green Button Smart Metering Energy Data GridMunicipal UtilityESPI

Kin Score

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

Composite quality — 29.4/100 · thin

Contract Quality 2.4 / 21

Developer Ergonomics 6.8 / 17

Access Clarity 5.8 / 17

Operational Transparency 0.0 / 11

Contract Governance 1.9 / 10

Discoverability 5.5 / 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/alectra-utilities/"><img src="https://apis.io/badge/alectra-utilities/card.svg" alt="Alectra Utilities 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 34.2 — up to +13.2 composite points
Operational Transparency scores 0.0 — up to +13.0 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/alectra-utilities/apis.yml: open an issue on github.com/api-evangelist/alectra-utilities 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.

Alectra Utilities Application Information API

Application Information endpoints

Alectra Utilities Authorization API

Authorization endpoints

Alectra Utilities Batch API

Batch data transfer endpoints

Alectra Utilities 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 3

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

Pull a Green Button bulk transfer from Alectra's data custodian

AGENT SKILL

Read an authorised Alectra customer's Green Button usage data

AGENT SKILL

Verify your third-party registration with Alectra's Green Button data custodian

AGENT SKILL

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Alectra Utilities 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.

Alectra Utilities Green Button Espi Overlay

4 actions · update · alectra-utilities-green-button-espi-openapi.json

DERIVED

Security Posture 2

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

Alectra Utilities Authentication

oauth2 · 1 scheme

SECURITY

Alectra Utilities Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Alectra Utilities Scopes

OAuth 2.0 · no documented scopes

0 scopes

SCOPES

Resources

Get Started 1

Portal, sign-up, and the first successful call

Portal

Portal

Documentation 1

Reference material describing how the API behaves

Documentation

Documentation

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

X-MCPServerCandidate

X-MCPServerCandidate

LLMsTxt

LLMsTxt

AgentSkill

AgentSkill

Design & Contract 2

Pagination, idempotency, versioning, errors, and events

Conformance

Conformance

Lifecycle

Lifecycle

Build 1

SDKs, sample code, and the tooling you integrate with

Packages

Packages

Access & Security 1

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Operate 2

Status, limits, changes, and where to get help

Support

Support

Contact

Contact

Commercial 2

Pricing, plans, and the legal terms of use

PrivacyPolicy

PrivacyPolicy

TermsOfService

TermsOfService

Company 5

The organization behind the API

Website

Blog

BlogRSS

Newsletter

LinkedIn

Other 2

Properties that don't map to a standard resource type

Overlay

Overlay

Registration

Registration

Source (apis.yml)

aid: alectra-utilities
url: https://raw.githubusercontent.com/api-evangelist/alectra-utilities/refs/heads/main/apis.yml
name: Alectra Utilities
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
- Utilities
- Electricity
- Ontario
- Green Button
- Smart Metering
- Energy Data
- Grid
- Municipal Utility
- ESPI
created: '2026-07-27'
modified: '2026-07-27'
specificationVersion: '0.23'
description: 'Alectra Utilities Corporation is Ontario''s second-largest municipally owned electricity distributor and one
  of the largest local distribution companies (LDCs) in Canada, serving roughly one million customers across seventeen communities
  in the Greater Toronto and Hamilton Area and the Golden Horseshoe — Alliston, Aurora, Barrie, Beeton, Bradford West Gwillimbury,
  Brampton, Guelph, Hamilton, Markham, Mississauga, Penetanguishene, Richmond Hill, Rockwood, St. Catharines, Thornton, Tottenham
  and Vaughan. It also bills water and wastewater/stormwater on behalf of several of those municipalities, and runs the GRE&T
  Centre for grid innovation. It sits squarely in the wires and metering layer of the Canadian value chain: it does not generate,
  it does not operate the market (the IESO does), and it is owned by its municipal shareholders rather than by investors —
  the Crown/municipal ownership pattern that dominates Canadian electricity. Its API posture exists only because a regulator
  created it. Ontario Regulation 633/21 (Energy Data) requires every Ontario electric and gas utility to implement Green Button
  Download My Data and Connect My Data to the NAESB REQ.21 ESPI v3.3 standard and to obtain Green Button Alliance certification,
  with an implementation deadline of 1 November 2023. Alectra publishes a Green Button page displaying GBA Certified DMD and
  CMD marks, a Green Button Connect My Data Terms and Conditions of Access and Use citing O. Reg. 633/21 by name, a live customer
  Green Button portal, and a live third-party registration and onboarding site — all three hosted by its data custodian vendor,
  Savage Data Systems, not by Alectra. What Alectra does not publish is any of the things that would let an outsider verify
  the implementation: there is no developer portal, no API documentation, no base URI, no OpenAPI, no scopes and no OAuth
  metadata anywhere on alectrautilities.com or on the portal host. developer., developers., docs. and data.alectrautilities.com
  do not resolve; /developers, /api, /docs, /data, /openapi.json and /swagger.json all return HTTP 404. Every path on the
  Green Button portal — including a deliberately invented control path — HTTP 302 redirects to a customer sign-in, so no endpoint
  could be confirmed. The resulting split is the finding: a mandated consumer-data API that a third party can reach only by
  completing an application and being approved, and zero open market or grid data of any kind, because in Ontario that layer
  belongs to the IESO and the OEB rather than to the distributor.'
apis:
- aid: alectra-utilities:alectra-utilities-applicationinformation-api
  name: Alectra Utilities Application Information API
  description: Application Information endpoints
  humanURL: https://alectrautilities.com/green-button-connect-my-data-terms-and-conditions-access-and-use
  tags:
  - ApplicationInformation
  properties:
  - type: OpenAPI
    url: openapi/alectra-utilities-applicationinformation-api-openapi.yml
  - type: Authentication
    url: authentication/alectra-utilities-authentication.yml
  - type: OAuthScopes
    url: scopes/alectra-utilities-scopes.yml
  - type: Conventions
    url: conventions/alectra-utilities-conventions.yml
  - type: ErrorCatalog
    url: errors/alectra-utilities-problem-types.yml
  - type: DataModel
    url: data-model/alectra-utilities-data-model.yml
  - type: Documentation
    url: https://alectrautilities.com/green-button
  - type: Documentation
    url: https://alectrautilities.com/green-button-connect-my-data-terms-and-conditions-access-and-use
  - type: PrivacyPolicy
    url: https://alectrautilities.com/green-button-privacy-policy
  - type: Registration
    url: https://alectrautilitiesonboarding.savagedata.com/
  - type: Portal
    url: https://alectrautilitiesgbportal.savagedata.com/
  - type: Documentation
    url: https://www.greenbuttondata.org/cmd.html
  - type: Documentation
    url: https://www.greenbuttonalliance.org/certification
- aid: alectra-utilities:alectra-utilities-authorization-api
  name: Alectra Utilities Authorization API
  description: Authorization endpoints
  humanURL: https://alectrautilities.com/green-button-connect-my-data-terms-and-conditions-access-and-use
  tags:
  - Authorization
  properties:
  - type: OpenAPI
    url: openapi/alectra-utilities-authorization-api-openapi.yml
  - type: Authentication
    url: authentication/alectra-utilities-authentication.yml
  - type: OAuthScopes
    url: scopes/alectra-utilities-scopes.yml
  - type: Conventions
    url: conventions/alectra-utilities-conventions.yml
  - type: ErrorCatalog
    url: errors/alectra-utilities-problem-types.yml
  - type: DataModel
    url: data-model/alectra-utilities-data-model.yml
  - type: Documentation
    url: https://alectrautilities.com/green-button
  - type: Documentation
    url: https://alectrautilities.com/green-button-connect-my-data-terms-and-conditions-access-and-use
  - type: PrivacyPolicy
    url: https://alectrautilities.com/green-button-privacy-policy
  - type: Registration
    url: https://alectrautilitiesonboarding.savagedata.com/
  - type: Portal
    url: https://alectrautilitiesgbportal.savagedata.com/
  - type: Documentation
    url: https://www.greenbuttondata.org/cmd.html
  - type: Documentation
    url: https://www.greenbuttonalliance.org/certification
- aid: alectra-utilities:alectra-utilities-batch-api
  name: Alectra Utilities Batch API
  description: Batch data transfer endpoints
  humanURL: https://alectrautilities.com/green-button-connect-my-data-terms-and-conditions-access-and-use
  tags:
  - Batch
  properties:
  - type: OpenAPI
    url: openapi/alectra-utilities-batch-api-openapi.yml
  - type: Authentication
    url: authentication/alectra-utilities-authentication.yml
  - type: OAuthScopes
    url: scopes/alectra-utilities-scopes.yml
  - type: Conventions
    url: conventions/alectra-utilities-conventions.yml
  - type: ErrorCatalog
    url: errors/alectra-utilities-problem-types.yml
  - type: DataModel
    url: data-model/alectra-utilities-data-model.yml
  - type: Documentation
    url: https://alectrautilities.com/green-button
  - type: Documentation
    url: https://alectrautilities.com/green-button-connect-my-data-terms-and-conditions-access-and-use
  - type: PrivacyPolicy
    url: https://alectrautilities.com/green-button-privacy-policy
  - type: Registration
    url: https://alectrautilitiesonboarding.savagedata.com/
  - type: Portal
    url: https://alectrautilitiesgbportal.savagedata.com/
  - type: Documentation
    url: https://www.greenbuttondata.org/cmd.html
  - type: Documentation
    url: https://www.greenbuttonalliance.org/certification
- aid: alectra-utilities:alectra-utilities-usagepoint-api
  name: Alectra Utilities Usage Point API
  description: Usage Point endpoints
  humanURL: https://alectrautilities.com/green-button-connect-my-data-terms-and-conditions-access-and-use
  tags:
  - UsagePoint
  properties:
  - type: OpenAPI
    url: openapi/alectra-utilities-usagepoint-api-openapi.yml
  - type: Authentication
    url: authentication/alectra-utilities-authentication.yml
  - type: OAuthScopes
    url: scopes/alectra-utilities-scopes.yml
  - type: Conventions
    url: conventions/alectra-utilities-conventions.yml
  - type: ErrorCatalog
    url: errors/alectra-utilities-problem-types.yml
  - type: DataModel
    url: data-model/alectra-utilities-data-model.yml
  - type: Documentation
    url: https://alectrautilities.com/green-button
  - type: Documentation
    url: https://alectrautilities.com/green-button-connect-my-data-terms-and-conditions-access-and-use
  - type: PrivacyPolicy
    url: https://alectrautilities.com/green-button-privacy-policy
  - type: Registration
    url: https://alectrautilitiesonboarding.savagedata.com/
  - type: Portal
    url: https://alectrautilitiesgbportal.savagedata.com/
  - type: Documentation
    url: https://www.greenbuttondata.org/cmd.html
  - type: Documentation
    url: https://www.greenbuttonalliance.org/certification
common:
- type: Overlay
  url: overlays/alectra-utilities-green-button-espi-overlay.yaml
- type: X-MCPServerCandidate
  url: mcp/alectra-utilities-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: DomainSecurity
  url: security/alectra-utilities-domain-security.yml
- type: Conformance
  url: conformance/alectra-utilities-conformance.yml
- type: Lifecycle
  url: lifecycle/alectra-utilities-lifecycle.yml
- type: Packages
  url: packages/alectra-utilities-packages.yml
- type: LLMsTxt
  url: llms/alectra-utilities-llms.txt
- type: AgentSkill
  url: skills/_index.yml
- type: Website
  url: https://alectrautilities.com/
- type: Documentation
  url: https://alectrautilities.com/green-button
- type: PrivacyPolicy
  url: https://alectrautilities.com/green-button-privacy-policy
- type: TermsOfService
  url: https://alectrautilities.com/green-button-connect-my-data-terms-and-conditions-access-and-use
- type: Registration
  url: https://alectrautilitiesonboarding.savagedata.com/
- type: Portal
  url: https://myalectra.alectrautilities.com/
- type: Support
  url: https://myalectra.alectrautilities.com/portal/#/Help/General%20Inquiry
- type: Blog
  url: https://www.alectra.com/news
- type: BlogRSS
  url: https://alectrautilities.com/rss.xml
- type: Newsletter
  url: https://alectrautilities.com/newsletter
- type: Contact
  url: https://alectrautilities.com/contact-us
- type: LinkedIn
  url: https://www.linkedin.com/company/alectra-utilities
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

Alectra Utilities API — frequently asked questions

Does Alectra Utilities have an API?

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

Is there an OpenAPI specification for the Alectra Utilities API?

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

How do I authenticate with the Alectra Utilities API?

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

Is the Alectra Utilities API ready for AI agents?

Alectra Utilities has a Kin Score of 29.4 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/alectra-utilities"

All providers

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

Every operation they expose

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

How their score was established

curl "https://apis.io/api/v1/providers/alectra-utilities/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.