Nova Scotia Power

Nova Scotia Power Incorporated (NSPI) is the investor-owned, vertically integrated regulated electric utility serving roughly half a million customers across Nova Scotia, Canada. A subsidiary of Halifax-based Emera Inc., it owns generation, transmission and distribution and is regulated by the Nova Scotia Energy and Regulatory Boards Tribunal (formerly the NSUARB). It sits at the retail end of the value chain as a franchise monopoly rather than a competitor in an open market — Nova Scotia has no wholesale market equivalent to IESO or AESO. Its API posture is the sharpest mandate-versus-implementation split in Canadian energy: section 4F of the Electricity Act, added by Bill 145 (SNS 2022, c. 12), legally required NSPI to implement the NAESB ESPI standard and be certified by the Green Button Alliance to BOTH "Connect My Data" and "Download My Data" on or before April 1, 2023. As of July 2026 the Green Button Alliance lists NSPI as certified to ESPI v3.3 for Download My Data only, with Connect My Data certification still "planned", and NSPI's own site states the Green Button Marketplace "is currently closed" to third-party applications. There is no developer portal, no published OpenAPI, no OAuth registration and no documented consumer data API — greenbutton.nspower.ca is live but every path redirects to a SAML customer login. By contrast NSPI is genuinely open on market and system data: its OASIS site publishes hourly net energy flow reports as anonymously downloadable CSV going back to 2012. Open market data, closed consumer data, and a statutory mandate whose API half is three years past its deadline.

Nova Scotia Power is profiled on the APIs.io network. Tagged areas include Energy, Canada, Utilities, Electricity, and Energy Retailer.

Nova Scotia Power’s developer surface includes authentication, developer portal, documentation, legal docs, support, engineering blog, product news, and 27 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

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

0 APIs

Energy Canada Utilities Electricity Energy Retailer Green Button Smart Metering Grid Renewables Solar EV Charging Energy Markets Regulations

Kin Score

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

Composite quality — 19.7/100 · emerging

Contract Quality 0.0 / 21

Developer Ergonomics 6.5 / 17

Access Clarity 3.6 / 17

Operational Transparency 0.0 / 11

Contract Governance 1.9 / 10

Discoverability 4.2 / 9

Regulatory Posture 2.8 / 15

Agent readiness — 5/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 4 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 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 could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

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/nova-scotia-power/"><img src="https://apis.io/badge/nova-scotia-power/card.svg" alt="Nova Scotia Power 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):

Machine-Readable Contract +18 pts — api_specs includes an OpenAPI document
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
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0

11 more unmet checks in the Agent Readiness table above.

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

Contract Quality scores 0.0 — up to +25.0 composite points
Access Clarity scores 21.1 — up to +15.8 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/nova-scotia-power/apis.yml: open an issue on github.com/api-evangelist/nova-scotia-power 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 →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
EV Charging (charging, roaming, e-mobility)	covered	18.5 (thin)	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 1

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

Security Posture 2

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

Nova Scotia Power Authentication

saml2 · 1 scheme

SECURITY

Nova Scotia Power Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Get Started 2

Portal, sign-up, and the first successful call

Portal

Portal

CustomerPortal

CustomerPortal

Documentation 3

Reference material describing how the API behaves

Documentation

Documentation

Documentation

Documentation

Documentation

Documentation

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

LLMsTxt

Design & Contract 3

Pagination, idempotency, versioning, errors, and events

Conventions

Conventions

Conformance

Conformance

Lifecycle

Lifecycle

Access & Security 3

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Authentication

Authentication

Authentication

Authentication

Operate 1

Status, limits, changes, and where to get help

Support

Support

Commercial 3

Pricing, plans, and the legal terms of use

Legal

Legal

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 5

The organization behind the API

Website

About

Blog

News

Careers

Other 13

Properties that don't map to a standard resource type

GreenButton

OpenData

OpenData

OpenData

OpenData

OpenData

OpenData

OpenData

OpenData

Regulatory

Regulation

Standard

OutageMap

Scroll for all 13

Source (apis.yml)

aid: nova-scotia-power
url: https://raw.githubusercontent.com/api-evangelist/nova-scotia-power/refs/heads/main/apis.yml
name: Nova Scotia Power
kind: company
description: 'Nova Scotia Power Incorporated (NSPI) is the investor-owned, vertically integrated regulated electric utility
  serving roughly half a million customers across Nova Scotia, Canada. A subsidiary of Halifax-based Emera Inc., it owns generation,
  transmission and distribution and is regulated by the Nova Scotia Energy and Regulatory Boards Tribunal (formerly the NSUARB).
  It sits at the retail end of the value chain as a franchise monopoly rather than a competitor in an open market — Nova Scotia
  has no wholesale market equivalent to IESO or AESO. Its API posture is the sharpest mandate-versus-implementation split
  in Canadian energy: section 4F of the Electricity Act, added by Bill 145 (SNS 2022, c. 12), legally required NSPI to implement
  the NAESB ESPI standard and be certified by the Green Button Alliance to BOTH "Connect My Data" and "Download My Data" on
  or before April 1, 2023. As of July 2026 the Green Button Alliance lists NSPI as certified to ESPI v3.3 for Download My
  Data only, with Connect My Data certification still "planned", and NSPI''s own site states the Green Button Marketplace
  "is currently closed" to third-party applications. There is no developer portal, no published OpenAPI, no OAuth registration
  and no documented consumer data API — greenbutton.nspower.ca is live but every path redirects to a SAML customer login.
  By contrast NSPI is genuinely open on market and system data: its OASIS site publishes hourly net energy flow reports as
  anonymously downloadable CSV going back to 2012. Open market data, closed consumer data, and a statutory mandate whose API
  half is three years past its deadline.'
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - security
  generated: '2026-11-06'
  method: derived
image: https://nspower.ca/images/default-source/default-album/brand/nsp-favicon.png
tags:
- Energy
- Canada
- Utilities
- Electricity
- Energy Retailer
- Green Button
- Smart Metering
- Grid
- Renewables
- Solar
- EV Charging
- Energy Markets
- Regulations
tags_raw:
- Energy
- Canada
- Utilities
- Electricity
- Energy Retailer
- Green Button
- Smart Metering
- Grid
- Renewables
- Solar
- EV Charging
- Energy Markets
- Regulation
created: '2026-07-27'
modified: '2026-07-27'
specificationVersion: '0.23'
apis: []
common:
- type: DomainSecurity
  url: security/nova-scotia-power-domain-security.yml
- type: Authentication
  url: authentication/nova-scotia-power-authentication.yml
- type: Conventions
  url: conventions/nova-scotia-power-conventions.yml
- type: Conformance
  url: conformance/nova-scotia-power-conformance.yml
- type: Lifecycle
  url: lifecycle/nova-scotia-power-lifecycle.yml
- type: LLMsTxt
  url: llms/nova-scotia-power-llms.txt
- type: Website
  url: https://www.nspower.ca/
- type: About
  url: https://www.nspower.ca/about-us/who-we-are
- type: GreenButton
  url: https://www.nspower.ca/cleanandgreen/innovation
- type: Portal
  url: https://greenbutton.nspower.ca/
- type: Authentication
  url: https://accounts.nspower.ca/
- type: CustomerPortal
  url: https://myaccount.nspower.ca/
- type: OpenData
  url: https://www.nspower.ca/oasis
- type: OpenData
  url: https://oasis.nspower.ca/
- type: Documentation
  url: https://www.nspower.ca/oasis/monthly-reports
- type: Documentation
  url: https://www.nspower.ca/oasis/system-reports-messages
- type: Documentation
  url: https://www.nspower.ca/oasis/distribution-hosting-capacity
- type: OpenData
  url: https://www.nspower.ca/oasis/forecasts-assessments
- type: OpenData
  url: https://www.nspower.ca/oasis/wholesale-market-documents
- type: OpenData
  url: https://www.nspower.ca/oasis/standards-codes
- type: OpenData
  url: https://www.nspower.ca/oasis/transmission-customer-procedures
- type: OpenData
  url: https://www.nspower.ca/oasis/generation-interconnection-procedures
- type: OpenData
  url: https://www.nspower.ca/oasis/regulatory-documents
- type: Regulatory
  url: https://www.nspower.ca/about-us/regulations/regulatory-initiatives
- type: Regulation
  url: https://nslegislature.ca/legc/bills/64th_1st/3rd_read/b145.htm
- type: Standard
  url: https://www.greenbuttonalliance.org/canadian-initiatives
- type: Legal
  url: https://www.nspower.ca/legal
- type: TermsOfService
  url: https://www.nspower.ca/legal
- type: PrivacyPolicy
  url: https://www.nspower.ca/privacy-statement
- type: Support
  url: https://www.nspower.ca/customer-service
- type: Blog
  url: https://www.nspower.ca/about-us/articles
- type: News
  url: https://www.nspower.ca/about-us/press-releases
- type: Careers
  url: https://www.nspower.ca/about-us/careers
- type: OutageMap
  url: https://outagemap.nspower.ca/
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

Nova Scotia Power API — frequently asked questions

How do I authenticate with the Nova Scotia Power API?

Nova Scotia Power uses bearer-token authentication (saml2 · 1 scheme). The details are profiled on APIs.io as Nova Scotia Power Authentication.

Is the Nova Scotia Power API ready for AI agents?

Nova Scotia Power has a Kin Score of 19.7 out of 100 (emerging) and an Agent Readiness score of 5.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/nova-scotia-power"

All providers

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

Every operation they expose

curl "https://apis.io/api/v1/providers/nova-scotia-power/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/nova-scotia-power/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.