Red Energy
Red Energy Pty Ltd (ABN 60 107 479 372) is an Australian electricity and gas retailer, wholly owned by Snowy Hydro Ltd, that supplies more than a million residential and business customers across New South Wales, Victoria, Queensland, South Australia and the ACT from a Richmond, Victoria base. It sits on the retail end of the National Electricity Market value chain: Snowy Hydro generates, the distribution network businesses own the poles and wires, AEMO operates the market and holds metering data, and Red Energy owns the customer, the tariff and the bill. Its API posture is entirely a product of statute rather than product strategy. Red Energy publishes no developer portal, no self-serve API programme and no proprietary specification - developer., api., docs. and data. subdomains do not resolve, and redenergy.com.au itself sits behind a Cloudflare bot challenge that returns HTTP 403 to any non-browser client. What it does have is a real, verified Consumer Data Right implementation: it is a designated CDR energy data holder listed on the CDR Register with the public base URI https://public.cdr.redenergy.com.au, which serves the Consumer Data Standards discovery endpoints live with correct x-v version negotiation, while 1,705 Red Energy branded plans are published anonymously through the Australian Energy Regulator's Energy Made Easy CDR host. The split is the story - open, standardised, anonymous product reference data on one side, and consumer usage, billing and account data available only to accredited CDR data recipients with the customer's consent on the other, with nothing at all in between.
Red Energy publishes 9 APIs on the APIs.io network, including Data Holder Customers API, Data Holder Operations API, Distributed Energy Resources API, and 6 more. Tagged areas include Energy, Australia, Utilities, Electricity, and Gas.
Red Energy’s developer surface includes authentication, changelog, code examples, status page, documentation, API reference, support, and 35 more developer resources.
Kin Score
APIs 9
Individual APIs this provider publishes, each with its own machine-readable definition.
Red Energy Data Holder Customers API
Data Holder Customer endpoints
Red Energy Data Holder Operations API
Data Holder Operations endpoints
Red Energy Distributed Energy Resources API
Distributed Energy Resource endpoints
Red Energy Electricity Service Points API
Electricity Service Point endpoints
Red Energy Electricity Usage API
Electricity Usage endpoints
Red Energy Energy Account Balances API
Energy Account Balance endpoints
Red Energy Energy Account Billing API
Energy Account Billing endpoints
Red Energy Energy Accounts API
Energy Account endpoints
Red Energy Energy Plans API
Energy Plan endpoints
Scroll for all 9
Open Collections 2
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
CDR Common API
OPEN COLLECTIONCDR Energy API
OPEN COLLECTIONArazzo Workflows 1
Multi-step API workflows described with the Arazzo specification.
Compare Red Energy tariff plans
Check that Red Energy's CDR implementation is available, then list its published electricity plans and pull the full tariff detail for one of them. Every step is unauthenticated...
ARAZZORate Limits 1
Documented rate limits and quota policies.
Red Energy Rate Limits
RATE LIMITSExamples 7
Example request and response payloads for these APIs.
Scroll for all 7
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
Recommended x-agentic-access execution contracts for AI agents.
Resources
Get Started 3
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 7
MCP servers, agent skills, and machine-readable catalogs
Scroll for all 7
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Operate 8
Status, limits, changes, and where to get help
Scroll for all 8
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 4
Properties that don't map to a standard resource type
Source (apis.yml)
Work with this as data
Every provider here is available over the APIs.io API and to AI agents over MCP.