AEMO
AEMO, the Australian Energy Market Operator, is the independent system and market operator for Australia's electricity and gas systems — it dispatches and prices the National Electricity Market across Queensland, New South Wales, Victoria, South Australia and Tasmania every five minutes, runs the Wholesale Electricity Market and the Gas Bulletin Board in Western Australia, operates the Victorian gas declared wholesale market and the Gas Supply Hubs, maintains the MSATS metering registry and the national Distributed Energy Resources register, and publishes the Integrated System Plan. It sits at the centre of the value chain: it does not generate, network or retail energy, it clears the market and holds the settlement-grade metering data that every other participant depends on. Under the Consumer Data Right extended to energy, AEMO is the designated SECONDARY data holder and gateway — retailers are the primary data holders, and AEMO serves NMI standing data, distributed energy resource records and up to twenty-four months of interval meter data through mandated Consumer Data Standards endpoints. Its API posture splits cleanly in two, and the split is the whole story: the market-data half is genuinely, radically open — 103 live NEMWeb report directories plus 68 archive directories of dispatch, price, demand, bidding, constraint and settlement data downloadable by anyone with no key, no account and no licence, alongside anonymous JSON endpoints behind the public NEM dashboard; the participant and consumer half is completely closed — a public developer portal at dev.aemo.com.au catalogues 74 APIs and 771 operations that anyone may read, but every one of them requires registration as an AEMO market participant, a Participant ID, MSATS user rights and an AEMO-signed mutual-TLS client certificate, and the OpenAPI documents the portal exports publicly are empty shells that declare zero paths and point at internal hostnames.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles AEMO the way a machine reads it — 169 machine-readable artifacts across 76 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 — AEMO scores 58.2/100 (strong), with a separate agent-readiness read of 41/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 AEMO'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/aemo/"
title="AEMO on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/aemo.svg"
alt="AEMO Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/aemo/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/aemo/"
title="AEMO on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/aemo/card.svg"
alt="AEMO 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 AEMO
Each block below is one kind of artifact we hold for AEMO. 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 86
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.
AEMO NEM Data Dashboard API
The JSON API behind AEMO's public National Electricity Market data dashboard, and the closest thing AEMO operates to an open real-time market API. Confirmed live and fully anony...
AEMO NEMWeb Public Data Feed
NEMWeb is AEMO's open bulk-data channel for the National Electricity Market and the single largest genuinely open energy dataset in Australia. It is not a REST API — it is an an...
AEMO WA Market Data Public Feed
The Western Australian equivalent of NEMWeb, covering the Wholesale Electricity Market that AEMO operates separately from the NEM. Confirmed anonymous and live on 2026-07-27: GE...
AEMO B2 B Messaging Async API
Introduction
AEMO B2 B Messaging Pull API
The B2BMessagingPull API is a B2B SMP API used to send and receive B2B messages between the participants in a Pull messaging pattern. The messages will be queued in the e-Hub an...
AEMO B2 B Messaging Sync API
Introduction
AEMO B2 M Messaging Async API
Introduction
AEMO B2 M Messaging Pull API
Introduction
AEMO B2 M Messaging Sync API
Introduction
AEMO Balancing Reports v2.1 API
Balancing Reports v2.1
AEMO Balancing Reports v2.2 API
Balancing Reports v2.2
AEMO Balancing Reports v2.3 API
Balancing Reports v2.3
AEMO Balancing Reports v2.4 API
Balancing Reports v2.4
AEMO Balancing Reports v2.5 API
Balancing Reports v2.5
AEMO Balancing Reports v2 API
Balancing Reports v2
AEMO Balancing Submission v2 API
Balancing Submission v2
AEMO Bilateral/Stem Submission v1 API
Bilateral/Stem Submission v1
AEMO Blind Update API
Introduction
AEMO Capacity API
Capacity
AEMO Capacity Auction API
CapacityAuction
AEMO CDR API
Introduction
AEMO CDR Common API
CDR Common
AEMO Data Holder Customers API
Data Holder Customer endpoints
AEMO Data Holder Operations API
Data Holder Operations endpoints
AEMO DER Registration For Account Holders API
Introduction
AEMO DER Registration for NSPs API
Introduction
AEMO Distributed Energy Resources API
Distributed Energy Resource endpoints
AEMO EE Simulation Status Update API
Introduction
AEMO Electricity Service Points API
Electricity Service Point endpoints
AEMO Electricity Usage API
Electricity Usage endpoints
AEMO Enablement Instruction API
EnablementInstruction
AEMO Energy Account Balances API
Energy Account Balance endpoints
AEMO Energy Account Billing API
Energy Account Billing endpoints
AEMO Energy Accounts API
Energy Account endpoints
AEMO Energy Plans API
Energy Plan endpoints
AEMO GasBB Reporting Public Data API
This API is intended for AEMO's use only, used by AEMO web pages and is not supported for any other use. It can change at any time. See https://dev.aemo.com.au/ for information ...
AEMO Generator Recall API
The Generator Recall API is used by generators to send information about recall times into the Generator Recall web-based interface in the EMMS Markets Portal. The system will t...
AEMO Hub Message Management API
Introduction
AEMO Hub Message Management V2 API
Introduction
AEMO Identity Service(v2) API
Introduction
AEMO LFAS Reports v2 API
LFAS Reports v2
AEMO LFAS Submission v2 API
LFAS Submission v2
AEMO Market Reports v2 API
Market Reports v2
AEMO Meter Exemption API
The Meter Exemptions API enables registered Metering Coordinators (MCs) to create and manage metering exemptions within MSATS.
AEMO MT PASA Offers API
Introduction
AEMO NEM Dispatch Bidding API
Bidding Service Open API specification
AEMO OAUTH V1 API
oauth-v1
AEMO OIP API
OIP
AEMO Outage Management API
Outage Management
AEMO P2 P Messaging Sync API
Introduction
AEMO Pre-Balancing Reports v6 API
Pre-Balancing Reports v6
AEMO Pre-Balancing Reports v7.1 API
Pre-Balancing Reports v7.1
AEMO Pre-Balancing Reports v7 API
Pre-Balancing Reports v7
AEMO Pre-Balancing Reports v8 API
Pre-Balancing Reports v8
AEMO Prudentials API
This API supports the various operations performed on Prudentials dashboard
AEMO RCM Operations API
RCM Operations
AEMO Reallocations API
Introduction
AEMO Report API
Report
AEMO RTMS API
The WEM-Reform API for Real-Time Market submissions available to all Market Participants.
AEMO Self Forecast API
Introduction
AEMO Settlement Direct API
This API supports the various operations performed in Settlement Direct API
AEMO Submission API
Submission
AEMO System Management Reports v2.1 API
System Management Reports v2.1
AEMO System Management Reports v2.2 API
System Management Reports v2.2
AEMO System Management Reports v2.3 API
System Management Reports v2.3
AEMO System Management Reports v2.4 API
System Management Reports v2.4
AEMO System Management Reports v2.5 API
System Management Reports v2.5
AEMO System Management Reports v2.6 API
System Management Reports v2.6
AEMO System Management Reports v2 API
System Management Reports v2
AEMO TLS Certificate Mgmt v1 API
The TLS Certificate Management API allows authorised participants to self-manage their AEMO-signed TLS certificates. This API provides the following features:
AEMO Variable Parameter API
VariableParameter
AEMO WEM Attributes Report API
WEM Attributes Report
AEMO WEM DER Installation V2 API
Introduction
AEMO WEM DER NMI API
Introduction
AEMO WEMDE DispatchCase API
WEMDE DispatchCase
AEMO WEMDE DispatchCase V2 API
WEMDE DispatchCase V2
AEMO WEMDE DispatchInstruction API
WEMDE DispatchInstruction
AEMO WEMDE DispatchSolution API
WEMDE DispatchSolution
AEMO WEMDE DispatchSolution V2 API
WEMDE DispatchSolution V2
AEMO WEMDE DispatchSummary API
WEMDE DispatchSummary
AEMO WEMDE DSPDispatchInstruction API
WEMDE DSPDispatchInstruction
AEMO WEMDE NCESS API
WEMDE NCESS
AEMO WEMDE NotInServiceCapacity API
WEMDE NotInServiceCapacity
AEMO WEMDE ReferenceTradingPrice API
WEMDE ReferenceTradingPrice
AEMO WEMDE TradingDayReport API
WEMDE TradingDayReport
Scroll within the panel for all 86 ·
Open Collections 76
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).
WEM Attributes Report
OPEN COLLECTIONB2BMessagingAsync
OPEN COLLECTIONB2BMessagingPull
OPEN COLLECTIONB2BMessagingSync
OPEN COLLECTIONB2MMessagingAsync
OPEN COLLECTIONB2MMessagingPull
OPEN COLLECTIONB2MMessagingSync
OPEN COLLECTIONBalancing Reports v2.1
OPEN COLLECTIONBalancing Reports v2.2
OPEN COLLECTIONBalancing Reports v2.3
OPEN COLLECTIONBalancing Reports v2.4
OPEN COLLECTIONBalancing Reports v2.5
OPEN COLLECTIONBalancing Reports v2
OPEN COLLECTIONBalancing Submission v2
OPEN COLLECTIONNEMDispatchBidding
OPEN COLLECTIONBilateral/Stem Submission v1
OPEN COLLECTIONBlindUpdate
OPEN COLLECTIONCapacity
OPEN COLLECTIONCapacityAuction
OPEN COLLECTIONCDR Common
OPEN COLLECTIONCDR
OPEN COLLECTIONCDR Common API
OPEN COLLECTIONCDR Energy API
OPEN COLLECTIONDER Registration for NSPs
OPEN COLLECTIONDER Registration For Account Holders
OPEN COLLECTIONWEM DER Installation V2
OPEN COLLECTIONWEM DER NMI
OPEN COLLECTIONEE Simulation Status Update
OPEN COLLECTIONEnablementInstruction
OPEN COLLECTIONGasBB Reporting Public Data
OPEN COLLECTIONGeneratorRecall
OPEN COLLECTIONHubMessageManagement
OPEN COLLECTIONHubMessageManagementV2
OPEN COLLECTIONIdentityService(v2)
OPEN COLLECTIONLFAS Reports v2
OPEN COLLECTIONLFAS Submission v2
OPEN COLLECTIONMarket Reports v2
OPEN COLLECTIONMeterExemption
OPEN COLLECTIONMT PASA Offers
OPEN COLLECTIONoauth-v1
OPEN COLLECTIONOIP
OPEN COLLECTIONIntermittent Generation Availability Submissions
OPEN COLLECTIONOutage Management
OPEN COLLECTIONP2PMessagingSync
OPEN COLLECTIONPre-Balancing Reports v6
OPEN COLLECTIONPre-Balancing Reports v7.1
OPEN COLLECTIONPre-Balancing Reports v7
OPEN COLLECTIONPre-Balancing Reports v8
OPEN COLLECTIONPrudentials
OPEN COLLECTIONRCM Operations
OPEN COLLECTIONReallocations
OPEN COLLECTIONReport
OPEN COLLECTIONRTMS
OPEN COLLECTIONSelfForecast
OPEN COLLECTIONSettlement Direct
OPEN COLLECTIONSubmission
OPEN COLLECTIONSystem Management Reports v2.1
OPEN COLLECTIONSystem Management Reports v2.2
OPEN COLLECTIONSystem Management Reports v2.3
OPEN COLLECTIONSystem Management Reports v2.4
OPEN COLLECTIONSystem Management Reports v2.5
OPEN COLLECTIONSystem Management Reports v2.6
OPEN COLLECTIONSystem Management Reports v2
OPEN COLLECTIONTLS Certificate Mgmt v1
OPEN COLLECTIONVariableParameter
OPEN COLLECTIONWEMDE DispatchCase
OPEN COLLECTIONWEMDE DispatchCase V2
OPEN COLLECTIONWEMDE DispatchInstruction
OPEN COLLECTIONWEMDE DispatchSolution
OPEN COLLECTIONWEMDE DispatchSolution V2
OPEN COLLECTIONWEMDE DispatchSummary
OPEN COLLECTIONWEMDE DSPDispatchInstruction
OPEN COLLECTIONWEMDE NCESS
OPEN COLLECTIONWEMDE NotInServiceCapacity
OPEN COLLECTIONWEMDE ReferenceTradingPrice
OPEN COLLECTIONWEMDE TradingDayReport
OPEN COLLECTIONScroll within the panel for all 76 ·
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Aemo Rate Limits
RATE LIMITSEvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Aemo Ehub Events
ASYNCAPISecurity Posture 3
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.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
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 AEMO — 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 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 7
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 7 ·
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 8
Authentication, authorization, and security posture
Scroll within the panel for all 8 ·
Operate 7
Status, limits, changes, and where to get help
Scroll within the panel for all 7 ·
Commercial 2
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 12
Properties that don't map to a standard resource type
Scroll within the panel for all 12 ·
← All providers · Data indexed from github.com/api-evangelist/aemo · machine-readable index on apis.io
This is an independent, third-party profile of AEMO, 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.