AESO
The Alberta Electric System Operator (AESO) is the independent, not-for-profit system and market operator for Alberta's electricity system — a statutory body created under Alberta's Electric Utilities Act that dispatches generation and operates the Alberta Interconnected Electric System twenty-four hours a day for roughly five million Albertans, plans the transmission system, administers grid connections, and runs Alberta's energy-only wholesale market including price settlement and market rules. It sits in the middle of the value chain: it does not own generation, wires or retail customers, it clears the pool, publishes the Pool Price, and holds the market-wide operational data every generator, retailer and trader in Alberta depends on. Its API posture is unusually clean for the sector and is the exact opposite of a compliance story — there is no mandate on AESO at all. Alberta has no Consumer Data Right, no Green Button regulation (that is Ontario's, by regulation, and Nova Scotia's), and no consumer energy-data obligation of any kind, and AESO holds no retail customer usage or billing data, so the consumer-data half of this sector simply does not exist here. What AESO publishes voluntarily is a genuinely open market-data surface in two layers: the legacy Energy Trading System report servlets at ets.aeso.ca, which return real CSV and HTML market reports — current supply and demand, pool price, system marginal price, daily averages, outages — anonymously with no key, no account and no licence click-through; and a modern Azure API Management gateway at apimgw.aeso.ca fronting fourteen documented JSON APIs whose full reference, operations, schemas and OpenAPI export can be read anonymously from the public developer portal, and whose keys are issued self-serve — email confirmation, subscribe to the single "AESO Public API" product, keys generated instantly, no approval step. Authentication is a single API-KEY request header (or a subscription-key query parameter). The one real friction is legal rather than technical: AESO's site terms permit non-commercial, personal or educational use only, and any other use requires written permission.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles AESO the way a machine reads it — 35 machine-readable artifacts across 14 APIs, 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 — AESO scores 42.9/100 (developing), with a separate agent-readiness read of 30/100 (agent ready). 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. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-10 · rubric v0.20.0
Put this on your own site. The badge is drawn live from AESO's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/aeso/"
title="AESO on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/aeso.svg"
alt="AESO Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/aeso/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/aeso/"
title="AESO on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/aeso/card.svg"
alt="AESO Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile AESO
Each block below is one kind of artifact we hold for AESO. 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 14
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.
AESO Energy Trading System (ETS) Public Reports
AESO's long-running Energy Trading System report servlets — the fully anonymous half of its data posture, and the reason market_data_open is true for AESO regardless of the API ...
AESO AIES Gen Capacity API
The AIESGenCapacity API from AESO — 1 operation(s) for aiesgencapacity.
AESO Assetlist API
The Assetlist API from AESO — 1 operation(s) for assetlist.
AESO Csd API
The Csd API from AESO — 2 operation(s) for csd.
AESO Interchange API
The Interchange API from AESO — 1 operation(s) for interchange.
AESO Load API
The Load API from AESO — 1 operation(s) for load.
AESO Load Outage Report API
The LoadOutageReport API from AESO — 1 operation(s) for loadoutagereport.
AESO Merit Order API
The MeritOrder API from AESO — 1 operation(s) for meritorder.
AESO Meteredvolume API
The Meteredvolume API from AESO — 1 operation(s) for meteredvolume.
AESO Operating Reserve Offer Control API
The OperatingReserveOfferControl API from AESO — 1 operation(s) for operatingreserveoffercontrol.
AESO Outage API
The Outage API from AESO — 1 operation(s) for outage.
AESO Poolparticipantlist API
The Poolparticipantlist API from AESO — 1 operation(s) for poolparticipantlist.
AESO Price API
The Price API from AESO — 3 operation(s) for price.
AESO Unit Commitment API
The UnitCommitment API from AESO — 1 operation(s) for unitcommitment.
Scroll within the panel for all 14 ·
Open Collections 14
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Actual Forecast Report
OPEN COLLECTIONAIES Gen Capacity API
OPEN COLLECTIONAsset List API
OPEN COLLECTIONCurrent Supply Demand
OPEN COLLECTIONCurrent Supply Demand
OPEN COLLECTIONEnergy Merit Order Report
OPEN COLLECTIONIntertie Public Reports
OPEN COLLECTIONLoad Outage Forecast API
OPEN COLLECTIONMetered Volume Report
OPEN COLLECTIONOperating Reserve Offer Control Report
OPEN COLLECTIONPool Participant API
OPEN COLLECTIONPool Price Report
OPEN COLLECTIONSystem Marginal Price Report
OPEN COLLECTIONUnit Commitment Data API
OPEN COLLECTIONScroll within the panel for all 14 ·
Arazzo Workflows 3
Real integrations are rarely a single call. Arazzo describes the multi-step sequences — auth, then create, then confirm — so both a human and an agent can follow the choreography, not just the endpoints.
Multi-step API workflows described with the Arazzo specification.
AESO asset drilldown
Resolve a pool participant into its fleet, read what those assets are generating right now, and pull their settlement-grade metered volumes.
ARAZZOAESO live market snapshot
Take one coherent reading of the Alberta market — supply and demand balance, live system marginal price, and today's completed settlement-hour pool prices.
ARAZZOAESO price formation trace
Reconstruct why Alberta's price cleared where it did — the offer stack, the units directed online, the outages that removed supply, and the resulting system marginal and pool pr...
ARAZZOPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Aeso Plans
PLANSSecurity Posture 2
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.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for AESO — 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 5
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 8
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 8 ·
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 4
Pricing, plans, and the legal terms of use
Company 4
The organization behind the API
Other 15
Properties that don't map to a standard resource type
Scroll within the panel for all 15 ·
← All providers · Data indexed from github.com/api-evangelist/aeso · machine-readable index on apis.io
This is an independent, third-party profile of AESO, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.