# NERC — 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 US Federal Power Act. Working from Washington, DC and Atlanta through six Regional Entities (MRO, NPCC, RF, SERC, Texas RE, WECC), it 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 part of Baja California, Mexico.

> API posture: NERC publishes NO developer API, NO OpenAPI or other machine-readable contract, 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 across 3,361 indexed pages. NERC is a MANDATOR of energy data, not a publisher of it — registered entities submit performance data upward into GADS, TADS, DADS and MIDAS under Rules of Procedure Section 1600, and that submitted data is confidential under Section 1500. What NERC publishes anonymously is documents: reliability assessments, the State of Reliability report, aggregated GADS/TADS statistics, Power BI dashboards, and the public Compliance Registry Matrix spreadsheet. Everything machine-facing — the ERO Portal, Align, the Secure Evidence Locker, CORES, the GADS/TADS data stores, the E-ISAC portal — is behind an approved account.

> This file is generated by API Evangelist from the NERC entry in the api-evangelist network. NERC does not publish an llms.txt of its own (https://www.nerc.com/llms.txt returns HTTP 404). NERC's robots.txt carries a Cloudflare Content Signals declaration — search=yes, ai-train=no, use=reference — and explicitly disallows Amazonbot, Applebot-Extended, Bytespider, CCBot, ClaudeBot, Google-Extended, GPTBot and meta-externalagent. Honour it.

## APIs

- None. `apis[]` in apis.yml is intentionally empty — no documented public API exists.
- Four real but undocumented JSON endpoints power nerc.com's own search UI (`/api/search`, `/api/search/events`, `/api/search/news`, `/api/search/terms`). They answer anonymously and were re-verified live on 2026-07-27, but they are internal Optimizely CMS routes with no documentation, no terms of programmatic use and no support. Recorded as probe evidence in review.yml; deliberately not promoted to APIs.

## Standards and programs

- [Reliability Standards](https://www.nerc.com/standards/reliability-standards): The mandatory, FERC-approved standards. Web and PDF only — no machine-readable representation of any standard.
- [Reliability Standards Under Development](https://www.nerc.com/standards/reliability-standards-under-development): Projects in flight, plus the multi-year Reliability Standards Development Plan.
- [Compliance Registry Files](https://www.nerc.com/programs/registration/compliance-registry-files): The public register of registered entities.
- [NERC Compliance Registry Matrix (XLSX)](https://www.nerc.com/globalassets/programs/registration/compliance-registry-files/nerc_compliance_registry_matrix_excel.xlsx): Anonymous download, 437KB spreadsheet — the closest thing to open data NERC publishes.
- [Generating Availability Data System (GADS)](https://www.nerc.com/programs/reliability-assessment--performance-analysis/generating-availability-data-system): Mandatory submission; confidential data; aggregated statistics published as PDF.
- [Transmission Availability Data System (TADS)](https://www.nerc.com/programs/reliability-assessment--performance-analysis/transmission-availability-data-system): Power BI dashboards, no data API.
- [Align and Secure Evidence Locker](https://www.nerc.com/applications/align-and-secure-evidence-locker-sel): The CMEP compliance platform. Gated.
- [CORES](https://www.nerc.com/applications/centralized-organization-registration-ero-system-cores-technology-project): Centralized Organization Registration ERO System. Gated.
- [NERC Data Stores and Extranet Sites](https://www.nerc.com/applications/nerc-data-stores--extranet-sites): Requires an ERO Portal account plus a per-store access request.
- [Security Guidelines](https://www.nerc.com/our-work/guidelines/security-guidelines): Published guidance from the Reliability and Security Technical Committee.

## Access and identity

- [ERO Portal](https://eroportal.nerc.net/): Account registration and per-application access requests. Interactive login with CAPTCHA. Not a developer portal.
- [E-ISAC](https://www.eisac.com/): Electricity Information Sharing and Analysis Center, operated by NERC on Salesforce Experience Cloud. Membership-gated.
- [E-ISAC OpenID Connect discovery](https://www.eisac.com/.well-known/openid-configuration): The only anonymous, machine-readable discovery document in NERC's estate — Salesforce platform issuer metadata, HTTP 200. Every resource behind it is gated (`/services/data/v62.0` returns HTTP 401).
- [NERC Alerts](https://www.nercalerts.com/index.php): Alert distribution system. Web only.
- No API keys, no client-credentials grant, no mTLS, no developer signup exists anywhere.

## API Evangelist artifacts

- [apis.yml](https://raw.githubusercontent.com/api-evangelist/nerc/refs/heads/main/apis.yml): The APIs.json index for NERC.
- [review.yml](https://raw.githubusercontent.com/api-evangelist/nerc/refs/heads/main/review.yml): Full probe log and the no-API finding, with HTTP statuses.
- [well-known/nerc-well-known.yml](https://raw.githubusercontent.com/api-evangelist/nerc/refs/heads/main/well-known/nerc-well-known.yml): Discovery-surface index across every NERC-operated host.
- [well-known/nerc-eisac-openid-configuration.json](https://raw.githubusercontent.com/api-evangelist/nerc/refs/heads/main/well-known/nerc-eisac-openid-configuration.json): The E-ISAC OIDC discovery document, captured verbatim.
- [well-known/nerc-robots.txt](https://raw.githubusercontent.com/api-evangelist/nerc/refs/heads/main/well-known/nerc-robots.txt): NERC's Content Signals / AI-crawler consent declaration, captured verbatim.
- [authentication/nerc-authentication.yml](https://raw.githubusercontent.com/api-evangelist/nerc/refs/heads/main/authentication/nerc-authentication.yml): Probed authentication profile for every NERC surface.
- [scopes/nerc-scopes.yml](https://raw.githubusercontent.com/api-evangelist/nerc/refs/heads/main/scopes/nerc-scopes.yml): The 36 OAuth scopes advertised by the E-ISAC issuer.
- [conformance/nerc-conformance.yml](https://raw.githubusercontent.com/api-evangelist/nerc/refs/heads/main/conformance/nerc-conformance.yml): Standards conformance, positive and negative, with evidence.
- [security/nerc-domain-security.yml](https://raw.githubusercontent.com/api-evangelist/nerc/refs/heads/main/security/nerc-domain-security.yml): TLS/HSTS/DNSSEC/CAA/SPF/DMARC probe results for nerc.com, nerc.net and eisac.com.

## Notes for agents

- Do not expect an API. Do not construct one. The correct integration path for NERC content is document retrieval from `www.nerc.com/globalassets/*` and the public registry spreadsheets.
- NERC's peers do publish APIs: FERC (the agency that certified NERC) runs a documented open data API at api.data.ferc.gov, and EIA publishes one of the best open government APIs anywhere. If you need programmatic North American electricity data, start there or with the ISOs/RTOs — not with NERC.
- Respect the Content Signals declaration in robots.txt: search=yes, ai-train=no, use=reference.

generated: 2026-07-27
method: generated
source: apis.yml + review.yml + live probes (no provider-published llms.txt exists)