# Renovara

> Renovara connects Claude or ChatGPT to Australian electricity (National Electricity Market) and east coast gas market data from AEMO, through an MCP server at https://mcp.renovara.co/mcp, with an analyst guide that tells the model how to query each table. Tables are refreshed daily. 30-day free trial with no card; setup takes about five minutes. Organisations can also query the same tables from their own code and AI agents with the Renovara SQL API: read-only DuckDB SQL over HTTPS at https://sql.api.renovara.co/v1.

Renovara is a data service, not a dashboard: the user keeps their own AI assistant and asks questions in plain English; the assistant writes and runs SQL against Renovara and shows its working. Market timestamps are AEST (UTC+10, no daylight saving). Western Australian markets are not included. Answers are information, not financial advice.

## Key pages

- [How Renovara works](https://renovara.co/how-renovara-works): the service in full, the data catalogue, refresh, access, limits and example questions
- [Connect your AI](https://renovara.co/connect-ai): adding the connector in Claude or ChatGPT
- [Pricing](https://renovara.co/pricing): subscription and the free trial
- [Sign up](https://renovara.co/signup): start the 30-day free trial
- [Renovara SQL API](https://renovara.co/sql-api): the enterprise plan for an organisation's own software and agents, and its 30-day trial
- [How Renovara SQL works](https://renovara.co/how-renovara-sql-works): the SQL API documentation: endpoints, authentication, statements, DuckDB SQL, limits, errors and tables (markdown: https://renovara.co/how-renovara-sql-works.md)
- [SQL API documentation in one file](https://renovara.co/llms-full.txt): the same documentation as plain markdown
- [NEMWeb for enterprise](https://renovara.co/nemweb-enterprise): the data as a Databricks share for teams
- [Terms of service](https://renovara.co/terms-of-service)
- [Privacy policy](https://renovara.co/renovara-privacy-policy)

## Renovara SQL API

Read-only SQL over the tables below from your own code and agents, for organisations that serve many clients and systems.

- Base URL: https://sql.api.renovara.co/v1. `GET https://sql.api.renovara.co/v1/` needs no credentials and says what the service is, the dialect, how to sign in and where everything else is.
- The API's own description: OpenAPI 3.1 at https://sql.api.renovara.co/v1/openapi.json.
- No credentials needed for the knowledge routes: `/guide?domain=nem` (or `gas`), the analyst guide; `/tables`; `/tables/{table}`, a table's columns and their meaning; `/reference?path=...`.
- Authentication: OAuth 2.0 client credentials. Exchange the client ID and secret for an access token with scope `renovara-sql/query`; it lasts 60 minutes, so cache it for its hour. Sign-in metadata at https://sql.api.renovara.co/v1/.well-known/oauth-protected-resource.
- Statements: `POST /statements` with `{"sql": "SELECT ..."}` waits up to 25 seconds; a slower statement returns an ID to poll with `GET /statements/{statement_id}`.
- Dialect: DuckDB, not Databricks SQL. One read-only SELECT per statement. Market timestamps carry no time zone (plain TIMESTAMP, AEST wall-clock); `_UTC` columns are TIMESTAMP WITH TIME ZONE; "now" in market time is `CAST(current_timestamp AS TIMESTAMP) + INTERVAL 10 HOUR`. The guide lists the other differences.
- Fast queries: every time-series table starts with `SETTLEMENT_DAY`, an INTEGER yyyymmdd of its main timestamp's calendar date. Filter on it as well as the timestamp so the server skips whole files: for October, `SETTLEMENT_DAY BETWEEN 20261001 AND 20261101 AND SETTLEMENTDATE > '2026-10-01 00:00' AND SETTLEMENTDATE <= '2026-11-01 00:00'` (SETTLEMENTDATE marks the end of its interval).
- Python client: `pip install renovara-sql`.
- Credentials: a person starts a trial at https://renovara.co/sql-api and creates credentials at https://renovara.co/sql-api-credentials. An agent without credentials can ask for them for its person: `POST https://sql.api.renovara.co/v1/trial/requests` with the person's email returns a link for the person to approve at https://renovara.co/sql-api-approve, then poll `GET /trial/requests/{device_code}`.
- Documentation: https://renovara.co/how-renovara-sql-works.

## Data available

47 tables in `external_data.nemweb`, measured 2026-11-09.

### Electricity: prices, demand and dispatch

- Dispatch prices (`external_data.nemweb.silver_dispatchis_reports_dispatch_price`): Regional energy and frequency control (FCAS) prices for every five-minute interval.
- Regional dispatch summary (`external_data.nemweb.silver_dispatchis_reports_dispatch_regionsum`): Demand, generation, interchange and frequency control requirements per region, every five minutes.
- Price setter (`external_data.nemweb.silver_pricesetter_price_setter`): Which unit set each region's price in each five-minute interval.
- Unit output (SCADA) (`external_data.nemweb.silver_dispatch_scada_dispatch_unit_scada`): Measured output in MW of each dispatchable unit at the start of every interval.
- Unit dispatch targets (`external_data.nemweb.silver_next_day_dispatch_dispatch_unit_solution`): Each unit's dispatch target and frequency control enablement, every five minutes.
- Bid tracking (`external_data.nemweb.silver_next_day_dispatch_dispatch_offertrk`): Which bid or offer each unit was dispatched against, every five minutes.
- Interconnector flows (`external_data.nemweb.silver_dispatchis_reports_dispatch_interconnectorres`): Flow, losses and limits on each interconnector, every five minutes.
- Inter-regional flows (`external_data.nemweb.silver_dispatchis_reports_dispatch_interconnection`): Flows and losses between regions, every five minutes.
- Local price adjustments (`external_data.nemweb.silver_dispatchis_reports_dispatch_local_price`): Local pricing offsets at each unit's connection point, every five minutes.
- Dispatch run summary (`external_data.nemweb.silver_dispatchis_reports_dispatch_case_solution`): One row per dispatch run, including interventions and solution status.
- Operational demand (`external_data.nemweb.silver_operational_demand_actual_operational_demand_actual`): Measured operational demand per region, every half hour.
- Rooftop solar (estimated actual) (`external_data.nemweb.silver_rooftop_pv_actual_rooftop_actual`): AEMO's estimate of rooftop solar output per region, every half hour.

### Electricity: forecasts

- Rooftop solar forecast (`external_data.nemweb.silver_rooftop_pv_forecast_rooftop_forecast`): AEMO's half-hourly rooftop solar forecast per region, up to eight days ahead.
- Five-minute predispatch, regions (`external_data.nemweb.silver_p5_reports_p5min_regionsolution`): Projected regional prices and demand for the next hour, in five-minute steps.
- Five-minute predispatch, interconnectors (`external_data.nemweb.silver_p5_reports_p5min_interconnectorsoln`): Projected interconnector flows for the next hour.
- Five-minute predispatch, local prices (`external_data.nemweb.silver_p5_reports_p5min_local_price`): Projected local price adjustments for the next hour.
- Predispatch prices (`external_data.nemweb.silver_predispatchis_reports_predispatch_region_prices`): Projected regional prices by half hour from each predispatch run.
- Predispatch regional solution (`external_data.nemweb.silver_predispatchis_reports_predispatch_region_solution`): Projected regional demand, generation and reserves from each predispatch run.
- Predispatch interconnectors (`external_data.nemweb.silver_predispatchis_reports_predispatch_interconnector_soln`): Projected interconnector flows and losses from each predispatch run.
- Predispatch local prices (`external_data.nemweb.silver_predispatchis_reports_predispatch_local_price`): Projected local price adjustments from each predispatch run.

### Electricity: constraints and losses

- Binding constraints (`external_data.nemweb.silver_dispatchis_reports_dispatch_constraint`): Binding and inter-regional constraints in each dispatch run, with their marginal values.
- Constraint catalogue (`external_data.nemweb.silver___gencondata`): The generic constraints AEMO uses, with their descriptions.
- Constraint sets (`external_data.nemweb.silver___genconset`): Which constraints belong to each constraint set.
- Constraint factors, connection points (`external_data.nemweb.silver___spdcpc`): The factor each constraint applies to each connection point.
- Constraint factors, regions (`external_data.nemweb.silver___spdrc`): The factor each constraint applies to regional generation and load.
- Marginal loss factors (`external_data.nemweb.silver_marginal_loss_factors_daily_mlf`): Marginal loss factors by connection point, by effective date and version.

### Electricity: registration and reference

- Unit details (`external_data.nemweb.silver___participant_registration_dudetailsummary`): Each dispatchable unit's region, connection point, type and loss factors over time.
- Units to gensets (`external_data.nemweb.silver___participant_registration_dualloc`): Which gensets make up each dispatchable unit, over time.
- Gensets (`external_data.nemweb.silver___participant_registration_genunits`): Every genset AEMO has registered, retired units included.
- Market participants (`external_data.nemweb.silver___participant_registration_participant`): Participant IDs, names and classes.
- Unit capacity history (`external_data.nemweb.silver___participant_registration_dudetail`): Each unit's registered and maximum capacity and storage over time.
- Stations (`external_data.nemweb.silver___participant_registration_station`): Every station AEMO has registered, with its name and address.
- Unit register (`external_data.nemweb.v_duid_registration`): One current row per unit, with its region, station, participant, type, fuel and capacity.
- Unit fuel (AEMO) (`external_data.nemweb.v_duid_fuel_aemo`): Fuel type for each unit, in AEMO's classification.
- Unit fuel (AER) (`external_data.nemweb.v_duid_fuel_aer`): Fuel type for each unit, in the Australian Energy Regulator's classification.

### Gas: AEMO Gas Bulletin Board

- Actual flows and storage (`external_data.nemweb.silver_gbb_actual_flow_storage`): Daily production, flows and storage by facility.
- Pipeline connection flows (`external_data.nemweb.silver_gbb_pipeline_connection_flow`): Daily flows at pipeline connection points.
- Nominations and forecasts (`external_data.nemweb.silver_gbb_nomination_forecast`): Facility nominations and forecasts for coming gas days.
- Short-term capacity outlook (`external_data.nemweb.silver_gbb_short_term_capacity_outlook`): Facility capacity for the coming days.
- Medium-term capacity outlook (`external_data.nemweb.silver_gbb_medium_term_capacity_outlook`): Planned capacity changes over the coming months.
- Linepack capacity adequacy (`external_data.nemweb.silver_gbb_linepack_capacity_adequacy`): Daily linepack and capacity adequacy status by pipeline.
- Linepack zones (`external_data.nemweb.silver_gbb_linepack_zones`): The pipeline segments linepack is reported for.
- Facilities (`external_data.nemweb.silver_gbb_facilities`): The Bulletin Board's register of facilities.
- Participants (`external_data.nemweb.silver_gbb_participants`): Bulletin Board participants.
- Basins (`external_data.nemweb.silver_gbb_basins`): Gas basins.
- Locations (`external_data.nemweb.silver_gbb_locations`): Bulletin Board locations.
- Nodes and connection points (`external_data.nemweb.silver_gbb_nodes_connection_points`): Pipeline nodes and connection points.

## Contact

- info@renovara.co