PECO Energy
PECO Energy Company is the largest electric and natural gas utility in Pennsylvania, serving roughly 1.7 million electric and 553,000 natural gas customers across a 2,100-square-mile service territory in southeastern Pennsylvania. Headquartered in Philadelphia and a wholly owned subsidiary of Exelon Corporation, PECO operates a regulated transmission and distribution business that includes a fully deployed smart-meter network, an LNG storage facility in West Conshohocken, and a portfolio of energy-efficiency, demand response, and assistance programs marketed under the Smart Ideas brand. PECO does not publish a public developer portal or general-purpose API: its digital surface is delivered through the PECO web portal (peco.com / secure.peco.com), iOS and Android mobile apps, and an internal Exelon Utilities content / configuration API (eudapi.peco.com) that is not documented for third-party use. Customer-authorized programmatic access to interval energy usage is available through the customer-facing My Data / Energy Usage tools and, where supported via the Pennsylvania PUC EDI / data access framework, through third-party data aggregators (UtilityAPI, Arcadia, etc.) using customer credentials.
Index entry only — little beyond a description and a link, and nothing machine-readable enough for an agent to act on without a human reading the site first.
API Evangelist profiles PECO Energy the way a machine reads it — 2 machine-readable artifacts across 1 API, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — PECO Energy scores 8.0/100 (minimal), with a separate agent-readiness read of 0/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile PECO Energy
Each block below is one kind of artifact we hold for PECO Energy. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 1
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Exelon Utilities Content API (Internal)
Shared Exelon Utilities backend (eudapi.peco.com) referenced by the PECO web portal's runtime configuration at https://www.peco.com/api/GetConfig (which exposes baseUrl, content...
Security Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for PECO Energy — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 1
Portal, sign-up, and the first successful call
Access & Security 1
Authentication, authorization, and security posture
Company 2
The organization behind the API
Other 11
Properties that don't map to a standard resource type
Scroll within the panel for all 11 ·
← All providers · Data indexed from github.com/api-evangelist/peco-energy · machine-readable index on apis.io