Electricity North West

Electricity North West — rebranded SP Electricity North West in August 2025 after Iberdrola acquired it and folded it in alongside SP Energy Networks — is the regulated electricity distribution network operator for the North West of England, running roughly 13,000 km of overhead line and more than 44,000 km of underground cable from Cumbria to Manchester. It is a poles-and-wires business in the regulated middle of the United Kingdom value chain: it owns the meter point and the network, it earns a regulated revenue under Ofgem's RIIO-ED2 price control, and it never bills the household — the supplier does. Its API posture is a clean split and worth stating plainly. On the MARKET-DATA side it is genuinely API-native for a network operator: it runs an Opendatasoft-hosted open data portal at electricitynorthwest.opendatasoft.com carrying 146 datasets — embedded capacity register, DFES scenarios, LV headroom and peak demand, network capacity heatmaps, GSP connection queue, GIS conductor and substation layers — served through the documented Opendatasoft Explore REST API v2.1 (and legacy v2.0) with a real OpenAPI 3.0.3 contract, a DCAT-AP catalogue export, and an in-portal API console. 96 of those datasets are CC BY 4.0 and 8 are Open Government Licence v3.0, but 41 sit under a bespoke "SP ENW Shared Licence" rather than an open one. On the CONSUMER-DATA side there is nothing: the United Kingdom has no consumer energy data-portability right equivalent to Australia's Consumer Data Right, Great Britain's smart-meter mandate produced infrastructure (the licensed Smart DCC) rather than a data right, Green Button has no UK footprint, and Electricity North West publishes no customer usage or billing API of any kind. The obligation that actually binds it is Ofgem's Data Best Practice Guidance under the RIIO-ED2 digitalisation licence condition — an open-data duty, not a consumer data right — and the portal is a real, verifiable implementation of it. Note that the corporate site www.enwl.co.uk sits behind a Cloudflare managed challenge and returns HTTP 403 to every non-browser client, so no part of the main website is machine-readable.

Electricity North West publishes 2 API contracts indexed on the APIs.io network: Catalog API and Dataset API. Tagged areas include Energy, United Kingdom, Utilities, Electricity, and Grid.

The Electricity North West catalog on APIs.io includes 1 Spectral governance ruleset.

Electricity North West’s developer surface includes developer portal, documentation, API reference, getting-started guide, sandbox, developer console, signup flow, and 40 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

62.7/100 strong ▬ flat Agent 33/100 agent ready Heartbeat 61/100 alive saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

2 published contracts 3 Agent Skills

Energy United Kingdom Utilities Electricity Grid Distribution Network Open Data DER Renewables Energy Markets Smart Metering

Kin Score

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

Composite quality — 62.7/100 · strong

Contract Quality 12.7 / 21

Developer Ergonomics 13.2 / 17

Access Clarity 5.8 / 17

Operational Transparency 9.3 / 11

Contract Governance 1.9 / 10

Discoverability 6.2 / 9

Regulatory Posture 6.9 / 15

Agent readiness — 33/100 · agent ready

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

Rate-Limit Signaling 7 / 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 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 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/electricity-north-west/"><img src="https://apis.io/badge/electricity-north-west/card.svg" alt="Electricity North West 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
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document
Delegated User Identity +6 pts — a served discovery document listing authorization_code in grant_types_supported (served), else an oauth2 authorizationCode flow or openIdConnect declared in an OpenAPI (documented)
Typed Event Surface +6 pts — AsyncAPI document, OR webhooks/callbacks objects in the as-published OpenAPI, OR common[].type includes Webhooks

4 more unmet checks in the Agent Readiness table above.

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

Access Clarity scores 34.2 — up to +13.2 composite points
Contract Quality scores 59.9 — up to +10.0 composite points
Contract Governance scores 18.2 — up to +9.8 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/electricity-north-west/apis.yml: open an issue on github.com/api-evangelist/electricity-north-west 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
Government and Open Data	standard	17.2 (thin)	-	-
Carbon Accounting Disclosure Standards (SBTi, PCAF, CDP, GHG Protocol)	standard	17.2 (thin)	-	-
UK G-Cloud Suppliers (UK public-sector cloud procurement)	standard	17.2 (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 2

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.

OpenAPI

measured — observed by APIs.io (published)

OAuth 2.0

measured — observed by APIs.io (declared)

APIs 2

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

Electricity North West Catalog API

API to enumerate datasets

Electricity North West Dataset API

API to work on records

Open Collections 2

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

Explore API

OPEN COLLECTION

Explore API

OPEN COLLECTION

Agent Skills 3

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

Bulk-export datasets and the catalogue

AGENT SKILL

Discover SP Electricity North West open datasets

AGENT SKILL

Query and aggregate network dataset records

AGENT SKILL

Electricity North West API pricing

Rate limits

Anonymous API calls (whole domain): 5000 requests per day
Per-dataset call quota: requests per day
Authenticated API calls: requests per day

Rate-limit details →

Rate Limits 1

Documented rate limits and quota policies.

Electricity North West Rate Limits

3 limits

RATE LIMITS

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Electricity North West API Rules

57 rules · 53 errors 2 warnings 2 info

SPECTRAL

OpenAPI Overlays 2

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.

Electricity North West Explore Api V2 0 Overlay

4 actions · update · electricity-north-west-explore-api-v2-0-openapi.json

DERIVED

Electricity North West Explore Api V2 1 Overlay

11 actions · update · electricity-north-west-explore-api-v2-1-openapi.json

DERIVED

Examples 6

Example request and response payloads for these APIs.

Electricity North West Catalog Facets License Example

2 fields

EXAMPLE

Electricity North West Forbidden Records Example

2 fields

EXAMPLE

Electricity North West Get Dataset Example

10 fields

EXAMPLE

Electricity North West List Datasets Example

2 fields

EXAMPLE

Electricity North West List Export Formats Example

1 fields

EXAMPLE

Electricity North West Odsql Error Example

2 fields

EXAMPLE

Security Posture 3

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

Electricity North West Authentication

apiKey/oauth2/cookie · 4 schemes

SECURITY

Electricity North West Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Electricity North West Vulnerability Disclosure

Hackerone · security.txt · contact published

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Electricity North West Scopes

1 scope · authorizationCode

1 scopes

SCOPES

Resources

Get Started 6

Portal, sign-up, and the first successful call

DeveloperPortal

Portal

GettingStarted

Sandbox

Console

SignUp

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

X-MCPServerCandidate

AgentSkill

LLMsTxt

WellKnown

Design & Contract 7

Pagination, idempotency, versioning, errors, and events

Conventions

Idempotency

ErrorCatalog

Lifecycle

DataModel

Conformance

Components

Scroll for all 7

Build 6

SDKs, sample code, and the tooling you integrate with

PostmanWorkspace

PostmanWorkspace

GitHubOrganization

Packages

SDKs

ToolCrosswalk

Examples

Access & Security 6

Authentication, authorization, and security posture

Authentication

OAuthScopes

SecurityTxt

DomainSecurity

VulnerabilityDisclosure

VulnerabilityDisclosure

Security

Security

Operate 5

Status, limits, changes, and where to get help

Support

RateLimits

StatusPage

Deprecation

ChangeLog

Commercial 2

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 3

The organization behind the API

Website

Website

Blog

Blog

LinkedIn

Other 6

Properties that don't map to a standard resource type

Overlay

Overlay

Registration

Data

Data

Regulator

Source (apis.yml)

aid: electricity-north-west
url: https://raw.githubusercontent.com/api-evangelist/electricity-north-west/refs/heads/main/apis.yml
name: Electricity North West
kind: company
description: 'Electricity North West — rebranded SP Electricity North West in August 2025 after Iberdrola acquired it and
  folded it in alongside SP Energy Networks — is the regulated electricity distribution network operator for the North West
  of England, running roughly 13,000 km of overhead line and more than 44,000 km of underground cable from Cumbria to Manchester.
  It is a poles-and-wires business in the regulated middle of the United Kingdom value chain: it owns the meter point and
  the network, it earns a regulated revenue under Ofgem''s RIIO-ED2 price control, and it never bills the household — the
  supplier does. Its API posture is a clean split and worth stating plainly. On the MARKET-DATA side it is genuinely API-native
  for a network operator: it runs an Opendatasoft-hosted open data portal at electricitynorthwest.opendatasoft.com carrying
  146 datasets — embedded capacity register, DFES scenarios, LV headroom and peak demand, network capacity heatmaps, GSP connection
  queue, GIS conductor and substation layers — served through the documented Opendatasoft Explore REST API v2.1 (and legacy
  v2.0) with a real OpenAPI 3.0.3 contract, a DCAT-AP catalogue export, and an in-portal API console. 96 of those datasets
  are CC BY 4.0 and 8 are Open Government Licence v3.0, but 41 sit under a bespoke "SP ENW Shared Licence" rather than an
  open one. On the CONSUMER-DATA side there is nothing: the United Kingdom has no consumer energy data-portability right equivalent
  to Australia''s Consumer Data Right, Great Britain''s smart-meter mandate produced infrastructure (the licensed Smart DCC)
  rather than a data right, Green Button has no UK footprint, and Electricity North West publishes no customer usage or billing
  API of any kind. The obligation that actually binds it is Ofgem''s Data Best Practice Guidance under the RIIO-ED2 digitalisation
  licence condition — an open-data duty, not a consumer data right — and the portal is a real, verifiable implementation of
  it. Note that the corporate site www.enwl.co.uk sits behind a Cloudflare managed challenge and returns HTTP 403 to every
  non-browser client, so no part of the main website is machine-readable.'
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
  - scopes
  - rate-limits
  - security
  - sandbox
  generated: '2026-11-06'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
tags:
- Energy
- United Kingdom
- Utilities
- Electricity
- Grid
- Distribution Network
- Open Data
- DER
- Renewables
- Energy Markets
- Smart Metering
created: '2026-07-27'
modified: '2026-07-27'
specificationVersion: '0.23'
apis:
- aid: electricity-north-west:electricity-north-west-catalog-api
  name: Electricity North West Catalog API
  description: API to enumerate datasets
  humanURL: https://electricitynorthwest.opendatasoft.com/api
  baseURL: https://electricitynorthwest.opendatasoft.com/api/explore/v2.1
  tags:
  - Catalog
  properties:
  - type: OpenAPI
    url: openapi/electricity-north-west-catalog-api-openapi.yml
  - type: APIReference
    url: https://electricitynorthwest.opendatasoft.com/api-console/explore/v2.1/
  - type: Documentation
    url: https://help.huwise.com/apis/ods-explore-v2/
  - type: Portal
    url: https://electricitynorthwest.opendatasoft.com/api
  - type: Data
    url: https://electricitynorthwest.opendatasoft.com/explore
- aid: electricity-north-west:electricity-north-west-dataset-api
  name: Electricity North West Dataset API
  description: API to work on records
  humanURL: https://electricitynorthwest.opendatasoft.com/api
  baseURL: https://electricitynorthwest.opendatasoft.com/api/explore/v2.1
  tags:
  - Datasets
  tags_raw:
  - Dataset
  properties:
  - type: OpenAPI
    url: openapi/electricity-north-west-dataset-api-openapi.yml
  - type: APIReference
    url: https://electricitynorthwest.opendatasoft.com/api-console/explore/v2.1/
  - type: Documentation
    url: https://help.huwise.com/apis/ods-explore-v2/
  - type: Portal
    url: https://electricitynorthwest.opendatasoft.com/api
  - type: Data
    url: https://electricitynorthwest.opendatasoft.com/explore
common:
- type: PostmanWorkspace
  url: https://www.postman.com/kinlaneapi/electricity-north-west/overview
- type: Overlay
  url: overlays/electricity-north-west-explore-api-v2-1-overlay.yaml
- type: Overlay
  url: overlays/electricity-north-west-explore-api-v2-0-overlay.yaml
- type: Website
  url: https://www.enwl.co.uk/
- type: DeveloperPortal
  url: https://electricitynorthwest.opendatasoft.com/api
- type: Portal
  url: https://electricitynorthwest.opendatasoft.com/
- type: Documentation
  url: https://electricitynorthwest.opendatasoft.com/api
- type: APIReference
  url: https://help.huwise.com/apis/ods-explore-v2/
- type: GettingStarted
  url: https://help.huwise.com/apis/ods-explore-v2/#section/Getting-Started
- type: Sandbox
  url: sandbox/electricity-north-west-sandbox.yml
- type: Console
  url: https://electricitynorthwest.opendatasoft.com/api-console/explore/v2.1/
- type: SignUp
  url: https://electricitynorthwest.opendatasoft.com/pages/registration_log_in/
- type: Registration
  url: https://electricitynorthwest.opendatasoft.com/pages/registration_log_in/
- type: Support
  url: mailto:dataportal@enwl.co.uk
- type: Blog
  url: https://news.enwl.co.uk/
- type: LinkedIn
  url: https://www.linkedin.com/company/electricity-north-west
- type: GitHubOrganization
  url: https://github.com/spenw-open-data
- type: TermsOfService
  url: https://www.enwl.co.uk/about-us/terms-and-conditions/
- type: PrivacyPolicy
  url: https://www.enwl.co.uk/misc/privacy-policy/
- type: Data
  url: https://electricitynorthwest.opendatasoft.com/explore
- type: Data
  url: https://electricitynorthwest.opendatasoft.com/api/explore/v2.1/catalog/exports/dcat
- type: Authentication
  url: authentication/electricity-north-west-authentication.yml
- type: OAuthScopes
  url: scopes/electricity-north-west-scopes.yml
- type: Conventions
  url: conventions/electricity-north-west-conventions.yml
- type: Idempotency
  url: conventions/electricity-north-west-conventions.yml
- type: RateLimits
  url: rate-limits/electricity-north-west-rate-limits.yml
- type: ErrorCatalog
  url: errors/electricity-north-west-problem-types.yml
- type: Lifecycle
  url: lifecycle/electricity-north-west-lifecycle.yml
- type: StatusPage
  url: https://status.huwise.com/
- type: Deprecation
  url: https://help.huwise.com/apis/ods-explore-v2/#section/Versioning/Deprecation-warnings
- type: ChangeLog
  url: changelog/electricity-north-west-changelog.yml
- type: DataModel
  url: data-model/electricity-north-west-data-model.yml
- type: Conformance
  url: conformance/electricity-north-west-conformance.yml
- type: Packages
  url: packages/electricity-north-west-packages.yml
- type: SDKs
  url: packages/electricity-north-west-packages.yml
- type: Components
  url: components/electricity-north-west-components.yml
- type: X-MCPServerCandidate
  url: mcp/electricity-north-west-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: ToolCrosswalk
  url: mcp/electricity-north-west-tool-crosswalk.yml
- type: AgentSkill
  url: skills/_index.yml
- type: Examples
  url: examples/_index.yml
- type: LLMsTxt
  url: llms/electricity-north-west-llms.txt
- type: WellKnown
  url: well-known/electricity-north-west-well-known.yml
- type: SecurityTxt
  url: well-known/electricity-north-west-security.txt
- type: DomainSecurity
  url: security/electricity-north-west-domain-security.yml
- type: VulnerabilityDisclosure
  url: security/electricity-north-west-vulnerability-disclosure.yml
- type: Security
  url: https://www.huwise.com/en/security/
- type: Regulator
  url: https://www.ofgem.gov.uk/sites/default/files/2024-10/Track_Changes_Data_Best_Practice_Guidance_v301728394292260.pdf
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

Electricity North West API — frequently asked questions

Does Electricity North West have an API?

Yes. APIs.io lists 2 APIs from Electricity North West, including Electricity North West Catalog API and Electricity North West Dataset API.

Is there an OpenAPI specification for the Electricity North West API?

Yes. APIs.io indexes 2 OpenAPI specifications for Electricity North West, each linked for download from this page.

How do I authenticate with the Electricity North West API?

Electricity North West uses bearer-token authentication (apiKey/oauth2/cookie · 4 schemes). The details are profiled on APIs.io as Electricity North West Authentication.

Is the Electricity North West API ready for AI agents?

Electricity North West has a Kin Score of 62.7 out of 100 (strong) and an Agent Readiness score of 33.0 (agent-ready), 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/electricity-north-west"

All providers

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

Every operation they expose

curl "https://apis.io/api/v1/providers/electricity-north-west/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/electricity-north-west/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.