The North American Electric Reliability Corporation (NERC) is the not-for-profit international regulatory authority certified by FERC in July 2006 as the Electric Reliability Organization under Section 215 of the Federal Power Act, added by the Energy Policy Act of 2005. From offices in Washington, DC and Atlanta, and working through six Regional Entities (MRO, NPCC, RF, SERC, Texas RE, WECC), NERC develops and enforces the mandatory Reliability Standards, including the CIP cyber security standards, that govern the bulk power system across the contiguous United States, all of Canada, and a portion of Baja California, Mexico. It registers and certifies the entities that operate that system, monitors and enforces compliance, runs the Electricity Information Sharing and Analysis Center (E-ISAC), and collects mandatory industry performance data through Rules of Procedure Section 1600 data requests into GADS, TADS, DADS and MIDAS. NERC sits at the top of the North American bulk-power value chain, above the ISOs/RTOs, transmission owners and generator owners it registers, and entirely above the retail utility-to-customer relationship. Its API posture is the plainest in this series. NERC publishes NO developer API, NO OpenAPI, NO SDK, NO developer portal and NO open data portal. A site search of nerc.com for the term API on 2026-07-27 returned zero matching documents. NERC is a MANDATOR of energy data, not a publisher of it. The obligation it imposes is to SUBMIT data upward to NERC, and the data submitted is explicitly confidential under Rules of Procedure Section 1500. What NERC does publish anonymously is documents: reliability assessments, the State of Reliability report, aggregated GADS/TADS statistics, Power BI dashboards and the public NERC Compliance Registry Matrix spreadsheet of every registered entity. Everything machine-facing, including the ERO Portal, Align, the Secure Evidence Locker, CORES, the GADS/TADS data stores and the E-ISAC portal, is behind an approved account. No Green Button, no ESPI, no consumer data right, and no consumer usage or billing API exists anywhere in NERC's surface, because retail customer data is outside its reach entirely. NERC is a regulator whose peer FERC publishes a documented public API and whose neighbour EIA publishes one of the best government APIs anywhere, while NERC itself publishes none.
NERC is profiled on the APIs.io network. Tagged areas include Energy, United States, Canada, Electricity, and Grid.
NERC’s developer surface includes developer portal, documentation, support, engineering blog, YouTube channel, authentication, and 22 more developer resources.
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/nerc/"><img src="https://apis.io/badge/nerc/card.svg" alt="NERC 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):
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
10 more unmet checks in the Agent Readiness table above.
Kin Score — facets with the most composite points still available (weight × headroom):
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.
aid: nerc
url: https://raw.githubusercontent.com/api-evangelist/nerc/refs/heads/main/apis.yml
name: NERC
kind: company
description: 'The North American Electric Reliability Corporation (NERC) is the not-for-profit international regulatory authority
certified by FERC in July 2006 as the Electric Reliability Organization under Section 215 of the Federal Power Act, added
by the Energy Policy Act of 2005. From offices in Washington, DC and Atlanta, and working through six Regional Entities
(MRO, NPCC, RF, SERC, Texas RE, WECC), NERC develops and enforces the mandatory Reliability Standards, including the CIP
cyber security standards, that govern the bulk power system across the contiguous United States, all of Canada, and a portion
of Baja California, Mexico. It registers and certifies the entities that operate that system, monitors and enforces compliance,
runs the Electricity Information Sharing and Analysis Center (E-ISAC), and collects mandatory industry performance data
through Rules of Procedure Section 1600 data requests into GADS, TADS, DADS and MIDAS. NERC sits at the top of the North
American bulk-power value chain, above the ISOs/RTOs, transmission owners and generator owners it registers, and entirely
above the retail utility-to-customer relationship. Its API posture is the plainest in this series. NERC publishes NO developer
API, NO OpenAPI, NO SDK, NO developer portal and NO open data portal. A site search of nerc.com for the term API on 2026-07-27
returned zero matching documents. NERC is a MANDATOR of energy data, not a publisher of it. The obligation it imposes is
to SUBMIT data upward to NERC, and the data submitted is explicitly confidential under Rules of Procedure Section 1500.
What NERC does publish anonymously is documents: reliability assessments, the State of Reliability report, aggregated GADS/TADS
statistics, Power BI dashboards and the public NERC Compliance Registry Matrix spreadsheet of every registered entity. Everything
machine-facing, including the ERO Portal, Align, the Secure Evidence Locker, CORES, the GADS/TADS data stores and the E-ISAC
portal, is behind an approved account. No Green Button, no ESPI, no consumer data right, and no consumer usage or billing
API exists anywhere in NERC''s surface, because retail customer data is outside its reach entirely. NERC is a regulator
whose peer FERC publishes a documented public API and whose neighbour EIA publishes one of the best government APIs anywhere,
while NERC itself publishes none.'
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
- security
generated: '2026-11-06'
method: derived
image: https://www.nerc.com/globalassets/nerc-logo.png
tags:
- Energy
- United States
- Canada
- Electricity
- Grid
- Regulator
- Government
- Reliability
- Bulk Power System
- Critical Infrastructure
- Cybersecurity
- Energy Markets
- Compliance
tags_raw:
- Energy
- United States
- Canada
- Electricity
- Grid
- Regulator
- Government
- Reliability
- Bulk Power System
- Critical Infrastructure
- Cyber Security
- Energy Markets
- Compliance
created: '2026-07-27'
modified: '2026-07-27'
specificationVersion: '0.23'
apis: []
common:
- type: Website
url: https://www.nerc.com/
- type: Portal
url: https://eroportal.nerc.net/
name: ERO Portal - account registration and access requests for NERC data stores and applications. Not a developer portal.
- type: Documentation
url: https://www.nerc.com/standards/reliability-standards
name: Reliability Standards (web and PDF only, no machine-readable contract)
- type: Documentation
url: https://www.nerc.com/programs/registration/compliance-registry-files
name: Compliance Registry Files - the public register of registered entities
- type: DataCatalog
url: https://www.nerc.com/globalassets/programs/registration/compliance-registry-files/nerc_compliance_registry_matrix_excel.xlsx
name: NERC Compliance Registry Matrix (XLSX, anonymous download, no API)
- type: Documentation
url: https://www.nerc.com/programs/reliability-assessment--performance-analysis/generating-availability-data-system
name: Generating Availability Data System (GADS) - mandatory submission, confidential data, aggregated statistics published
as PDF only
- type: Documentation
url: https://www.nerc.com/programs/reliability-assessment--performance-analysis/transmission-availability-data-system
name: Transmission Availability Data System (TADS) - Power BI dashboards, no data API
- type: Documentation
url: https://www.nerc.com/applications/align-and-secure-evidence-locker-sel
name: Align and Secure Evidence Locker (CMEP compliance platform, gated)
- type: Documentation
url: https://www.nerc.com/applications/centralized-organization-registration-ero-system-cores-technology-project
name: Centralized Organization Registration ERO System (CORES), gated
- type: Documentation
url: https://www.nerc.com/applications/nerc-data-stores--extranet-sites
name: NERC Data Stores and Extranet Sites (ERO Portal account required)
- type: Support
url: https://support.nerc.net/
- type: Blog
url: https://www.nerc.com/newsroom
- type: PrivacyPolicy
url: https://www.nerc.com/legal-privacy-policy
- type: TermsOfService
url: https://www.nerc.com/terms-of-use-policy
- type: LinkedIn
url: https://www.linkedin.com/company/north-american-electric-reliability-corporation/
- type: Twitter
url: https://twitter.com/NERC_Official
- type: YouTube
url: https://www.youtube.com/@NERCOfficial
- type: Website
url: https://www.eisac.com/
name: Electricity Information Sharing and Analysis Center (E-ISAC) - membership-gated Salesforce Experience Cloud portal
- type: Website
url: https://www.nercalerts.com/index.php
name: NERC Alerts system
- type: Roadmap
url: https://www.nerc.com/standards/reliability-standards-under-development
name: Reliability Standards Under Development - the forward work plan for NERC's standards, backed by the multi-year Reliability
Standards Development Plan (2026-2028 edition posted August 2025). A standards roadmap, not an API roadmap.
- type: WellKnown
url: well-known/nerc-well-known.yml
name: Discovery-surface index across every NERC-operated host. Only real hit is the E-ISAC OpenID Connect discovery document;
www.nerc.com serves no /.well-known document at all.
- type: OpenIDConnect
url: well-known/nerc-eisac-openid-configuration.json
name: E-ISAC OpenID Connect discovery document (https://www.eisac.com/.well-known/openid-configuration), captured verbatim.
Salesforce Experience Cloud issuer metadata; protected resources are membership-gated.
- type: ContentSignal
url: well-known/nerc-robots.txt
name: 'Cloudflare-managed Content Signals declaration captured verbatim: search=yes, ai-train=no, use=reference, with explicit
Disallow blocks for GPTBot, ClaudeBot, Google-Extended, CCBot, Amazonbot, Applebot-Extended, Bytespider and meta-externalagent.'
- type: Authentication
url: authentication/nerc-authentication.yml
name: Probed authentication profile. No API keys, no developer credentials, no machine-to-machine grant anywhere; interactive
login only, plus the E-ISAC OAuth2/OIDC issuer.
- type: OAuthScopes
url: scopes/nerc-scopes.yml
name: The 36 OAuth scopes advertised by the E-ISAC issuer (Salesforce platform scope set). NERC publishes no scope reference
of its own.
- type: Conformance
url: conformance/nerc-conformance.yml
name: Standards conformance with evidence - OIDC discovery and Content Signals conform; OpenAPI, AsyncAPI, GraphQL, security.txt,
RFC 9457, data.json, apis.json and llms.txt do not exist.
- type: DomainSecurity
url: security/nerc-domain-security.yml
name: TLS/HSTS/DNSSEC/CAA/SPF/DMARC probe results for nerc.com, nerc.net and eisac.com.
- type: LLMsTxt
url: llms/nerc-llms.txt
name: Generated llms.txt - NERC publishes none (/llms.txt returns HTTP 404).
maintainers:
- FN: Kin Lane
email: kin@apievangelist.com
NERC API — frequently asked questions
How do I authenticate with the NERC API?
NERC documents its authentication (none/oauth2/openIdConnect · 0 schemes). The details are profiled on APIs.io as Nerc Authentication.
Is the NERC API ready for AI agents?
NERC has a Kin Score of 20.6 out of 100 (emerging) and an Agent Readiness score of 12.9 (agent-aware), scored by API Evangelist on 2026-11-06.
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.
Kin Score
How this is scored →
It updates itself when the score changes. Paste this where you link to your API docs: