# Renewable Vision energy data

> Saudi and regional energy data: registers, series, trackers, briefs; atlas layers need a member key.

- name: sa.com.renewablevision/renewable-vision
- version: 0.2.0
- connection class: R0 (autonomous)
- trust: 83/100 flags: no-repository
- quality: 75/100 (new)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/sa.com.renewablevision%2Frenewable-vision
- tools: https://api.protogrid.dev/v1/servers/sa.com.renewablevision%2Frenewable-vision/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "renewable-vision": {
      "type": "http",
      "url": "https://renewablevision.com.sa/api/mcp"
    }
  }
}
```


## Trust

- hygiene: 80
- liveness: 100
- freshness: 100
- provenance: 55
- drivers: +dns-namespace +website +reachable +uptime-100% +updated-4d-ago -no-repository
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 75/100 (new)

### protocol: 75 (weight 25)

- warn `protocol.modern`: newest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
- n/a `protocol.stateless`: only applies to 2026-07-28 servers
- pass `protocol.transport`: streamable HTTP
- n/a `protocol.list_ttl`: only applies to 2026-07-28 servers

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 75 (weight 30)

- pass `tools.descriptions`: every tool has a description
- warn `tools.description_length`: 2 tools have descriptions over 1,024 characters, which crowds the context
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 28 of 28 tools declare readOnlyHint or destructiveHint
- fail `tools.directory_hints`: no tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: list_briefs (idempotentHint); project_output_estimate (idempotentHint); gcc_emissions (idempotentHint); …
- warn `tools.token_cost`: about 8,206 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump
- pass `tools.hidden_text`: no hidden text in tool names, descriptions, schemas or annotations

### stability: n/a (weight 15)

- n/a `stability.changes`, `stability.rug_pull`, `stability.new_links`: tool history recorded for 3 of the 7 days needed

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 28, about 8,206 tokens to load them all
- tool set hash: c281c4935d9bff8c18837705145d6a01
- tools last changed: 2026-11-13T10:06:49.487Z
- badge: [![protogrid quality](https://protogrid.dev/badge/sa.com.renewablevision/renewable-vision.svg)](https://protogrid.dev/servers/sa.com.renewablevision/renewable-vision)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

- 2026-11-13 `tracker_summary` changed (description, inputSchema)
  - before: A tracker’s headline figures as its own page prints them, with the date they are true as of, read exactly as the site’s assistant reads them: projects and capacity by stage, and by country for the GCC and Regional Renewables Trackers. tracker: saudi-renewables (stages as the page counts them, the Principal Buyer’s register leading where it differs), gcc-renewables, regional-renewables, captive-solar, data-centres (Saudi: the 2024 baseline, the flagship records by status and the 2030 scenarios), ccus (capture Mt CO2 a year by stage), storage, hydrogen, water. For any other cut, aggregate_projects. Answers anyone.
  - after: A tracker’s headline figures as its own page prints them, with the date they are true as of, read exactly as the site’s assistant reads them: projects and capacity by stage, and by country for the GCC, Regional and World Renewables Trackers. tracker: saudi-renewables (stages as the page counts them, the Principal Buyer’s register leading where it differs), gcc-renewables, regional-renewables, world-renewables (the flagship projects of every other country), captive-solar, data-centres (Saudi: the 2024 baseline, the flagship records by status and the 2030 scenarios), ccus (capture Mt CO2 a year by stage), storage, hydrogen, water. For any other cut, aggregate_projects. Answers anyone.
- 2026-11-13 `aggregate_projects` changed (inputSchema)
- 2026-11-13 `find_projects` changed (description, inputSchema)
  - before: Search and filter the whole project index, the one the site’s assistant reads: the Saudi, captive, GCC and Regional Renewables Trackers, Saudi battery storage, the Saudi, GCC and Regional Data Centre Trackers, the CCUS tracker, the IEA hydrogen map and the Saudi water, AI and dedicated-systems registers. Filter by free text, place (a country, gcc, mena …), sector, technology, stage or a stage range, commercial operation date range, developer, or one tracker; or pass the /data/projects query string as filter. Returns the matching rows, each with its id, capacity in the unit its source states, stage, country, developers, commercial operation date, its page, its dataset page, the publication it rests on (sourceUrl) and the date it was read (asOf), plus the trackers the rows come from with their own as-of dates. Page with limit and offset. For counts and totals use aggregate_projects, which never sums MWh with MW; for one project’s full facts and every source use get_project. Free with membership, like the project index: it answers a request carrying a member’s API key and refuses one without, except when tracker is global-ccus or iea-hydrogen.
  - after: Search and filter the whole project index, the one the site’s assistant reads: the Saudi, captive, GCC, Regional and World Renewables Trackers, Saudi battery storage, the Saudi, GCC, Regional and World Data Centre Trackers, the CCUS tracker, the IEA hydrogen map and the Saudi water, AI and dedicated-systems registers. Filter by free text, place (a country, gcc, mena …), sector, technology, stage or a stage range, commercial operation date range, developer, or one tracker; or pass the /data/projects query string as filter. Returns the matching rows, each with its id, capacity in the unit its source states, stage, country, developers, commercial operation date, its page, its dataset page, the publication it rests on (sourceUrl) and the date it was read (asOf), plus the trackers the rows come from with their own as-of dates. Page with limit and offset. For counts and totals use aggregate_projects, which never sums MWh with MW; for one project’s full facts and every source use get_project. Free with membership, like the project index: it answers a request carrying a member’s API key and refuses one without, except when tracker is global-ccus or iea-hydrogen.
- 2026-11-13 `get_company` changed (description)
  - before: One developer or shareholder named in the Saudi Renewables Tracker, by the slug on its page (acwa-power, masdar, edf-renewables, saudi-aramco-power …; search_projects returns developers as published). Returns every project that names it with the equity share the developers publish, its capacity by stage (operational, construction, tendered) and by technology in MW, the capacity attributable by published equity share over the projects that publish one, and recent change-ledger entries across its projects. Spellings of one company (EDF and EDF Renewables; SAPCO, Aramco Power and Saudi Aramco Power) are read as one. Stage totals count each project’s whole capacity; never add them across companies. `coverage` lists the company’s Saudi captive and corporate projects, its GCC projects and its projects in the Regional Renewables Tracker, with capacity as each source states it; those are not in the stage totals. A company named only there (ENGIE, TAQA, DEWA …) is answered too.
  - after: One developer or shareholder named in the Saudi Renewables Tracker, by the slug on its page (acwa-power, masdar, edf-renewables, saudi-aramco-power …; search_projects returns developers as published). Returns every project that names it with the equity share the developers publish, its capacity by stage (operational, construction, tendered) and by technology in MW, the capacity attributable by published equity share over the projects that publish one, and recent change-ledger entries across its projects. Spellings of one company (EDF and EDF Renewables; SAPCO, Aramco Power and Saudi Aramco Power) are read as one. Stage totals count each project’s whole capacity; never add them across companies. `coverage` lists the company’s Saudi captive and corporate projects, its GCC projects and its projects in the Regional and World Renewables Trackers, with capacity as each source states it; those are not in the stage totals. A company named only there (ENGIE, TAQA, DEWA …) is answered too.
- 2026-11-13 `search_projects` changed (description, inputSchema)
  - before: Match a name, developer, country, region or city across the project trackers and return the matching rows with their capacities, largest first. dataset: renewables (Saudi renewable projects — technology, capacity MW, status operational|construction|tendered|announced, developers, LCOE), captive (Saudi captive and corporate solar: corporate PPAs, plants owned by the factory or farm they supply, plants built into water projects — capacity as the source states it, offtaker, arrangement, status operational|construction|contracted|tendered|announced|observed, sources), gcc (utility-scale solar, CSP, wind and battery projects of 50 MW or more in the UAE, Oman, Qatar, Kuwait and Bahrain — country as ISO code, capacity as stated, procurer, owners and developers, published tariff, the same statuses, sources), regional (the same kind of rows in the Middle East beyond the Gulf, Africa, the Caucasus, Central Asia and South and Southeast Asia — country as ISO code, wind-solar hybrids as technology hybrid, tariffs only in US cents/kWh), data-centres (Saudi data-centre records — lead, city, disclosed MW with its basis, investment), ccus (global carbon capture projects — developer, country, capture Mt/yr, sector), hydrogen (the IEA low-emission hydrogen map, mirrored as capacity by year, region and stage rather than as named projects). Omit dataset to search the renewables, captive, GCC, regional, data-centre and CCUS trackers at once. Capacity totals are summed only inside one dataset, in that dataset’s own unit; captive, GCC and regional capacity is MW as each source states it (MWac or MWp) and heat (MWth) is never added. The renewables, captive, gcc, regional and data-centres datasets are free with membership: they answer a request carrying a member’s API key, and refuse one without, as does a search with no dataset named; ccus and hydrogen answer anyone. For every other tracker in the project index (Saudi battery storage, the GCC and Regional Data Centre Trackers, the water, AI and dedicated-systems registers), filters by stage, technology or date, and counts or totals, use find_projects and aggregate_projects.
  - after: Match a name, developer, country, region or city across the project trackers and return the matching rows with their capacities, largest first. dataset: renewables (Saudi renewable projects — technology, capacity MW, status operational|construction|tendered|announced, developers, LCOE), captive (Saudi captive and corporate solar: corporate PPAs, plants owned by the factory or farm they supply, plants built into water projects — capacity as the source states it, offtaker, arrangement, status operational|construction|contracted|tendered|announced|observed, sources), gcc (utility-scale solar, CSP, wind and battery projects of 50 MW or more in the UAE, Oman, Qatar, Kuwait and Bahrain — country as ISO code, capacity as stated, procurer, owners and developers, published tariff, the same statuses, sources), regional (the same kind of rows in the Middle East beyond the Gulf, Africa, the Caucasus, Central Asia and South and Southeast Asia — country as ISO code, wind-solar hybrids as technology hybrid, tariffs only in US cents/kWh), world (the same row shape for the flagship projects of every other country — the US, Canada, Latin America, Europe, China, Japan, Korea, Australia and the rest: renewables of 1 GW or more and batteries of 300 MW or 1,000 MWh or more), data-centres (Saudi data-centre records — lead, city, disclosed MW with its basis, investment), ccus (global carbon capture projects — developer, country, capture Mt/yr, sector), hydrogen (the IEA low-emission hydrogen map, mirrored as capacity by year, region and stage rather than as named projects). Omit dataset to search the renewables, captive, GCC, regional, world, data-centre and CCUS trackers at once. Capacity totals are summed only inside one dataset, in that dataset’s own unit; captive, GCC, regional and world capacity is MW as each source states it (MWac or MWp) and heat (MWth) is never added. The renewables, captive, gcc, regional, world and data-centres datasets are free with membership: they answer a request carrying a member’s API key, and refuse one without, as does a search with no dataset named; ccus and hydrogen answer anyone. For every other tracker in the project index (Saudi battery storage, the GCC, Regional and World Data Centre Trackers, the water, AI and dedicated-systems registers), filters by stage, technology or date, and counts or totals, use find_projects and aggregate_projects.
- 2026-11-12 `tracker_summary` added
  - A tracker’s headline figures as its own page prints them, with the date they are true as of, read exactly as the site’s assistant reads them: projects and capacity by stage, and by country for the GCC and Regional Renewables Trackers. tracker: saudi-renewables (stages as the page counts them, the Principal Buyer’s register leading where it differs), gcc-renewables, regional-renewables, captive-solar, data-centres (Saudi: the 2024 baseline, the flagship records by status and the 2030 scenarios), ccus (capture Mt CO2 a year by stage), storage, hydrogen, water. For any other cut, aggregate_projects. Answers anyone.
- 2026-11-12 `get_project` added
  - Everything the site holds on one project, by its id from find_projects, search_projects or a project page (/data/projects/{id}), whichever tracker lists it: name, sector, technology, capacity as stated with any other ratings and what the figure covers, stage with the source’s own words, place (locality and region only, never coordinates), dated milestones (planned or actual), disclosed investment, published tariff or levelised cost, the companies and their roles and published shares, the owner’s sourced facts, and every publication the row was compiled from with the date it was read. asOf is the date the tracker last read the project. Answers anyone, as the project’s public page does.
- 2026-11-12 `aggregate_projects` added
  - Count projects, add up their stated capacity or their disclosed investment, grouped by country, place, stage, technology, sector, developer, year (of commercial operation) or source (tracker), optionally split by stage, technology, sector or country, over any filter find_projects takes. Computed by the same engine as the site’s assistant, so the figures equal the ones /assistant gives for the same question. The units rule: capacity is added within one family only, MW, MWp and MWac as each source states them, or one other unit alone (MWh, t/yr, m3/day); MWh is never added to MW and heat (MWth) never to electricity. Every answer says how many matching projects were not counted and why (no figure in the unit, a figure its source says must not be added up, no stated year), the method in words, the trackers it rests on with their pages, and the date the newest row was read. Answers anyone: these are aggregates, as the tracker pages print them; the rows themselves are find_projects.
- 2026-11-12 `find_projects` added
  - Search and filter the whole project index, the one the site’s assistant reads: the Saudi, captive, GCC and Regional Renewables Trackers, Saudi battery storage, the Saudi, GCC and Regional Data Centre Trackers, the CCUS tracker, the IEA hydrogen map and the Saudi water, AI and dedicated-systems registers. Filter by free text, place (a country, gcc, mena …), sector, technology, stage or a stage range, commercial operation date range, developer, or one tracker; or pass the /data/projects query string as filter. Returns the matching rows, each with its id, capacity in the unit its source states, stage, country, developers, commercial operation date, its page, its dataset page, the publication it rests on (sourceUrl) and the date it was read (asOf), plus the trackers the rows come from with their own as-of dates. Page with limit and offset. For counts and totals use aggregate_projects, which never sums MWh with MW; for one project’s full facts and every source use get_project. Free with membership, like the project index: it answers a request carrying a member’s API key and refuses one without, except when tracker is global-ccus or iea-hydrogen.
- 2026-11-12 `get_company` changed (description)
  - before: One developer or shareholder named in the Saudi Renewables Tracker, by the slug on its page (acwa-power, masdar, edf-renewables, saudi-aramco-power …; search_projects returns developers as published). Returns every project that names it with the equity share the developers publish, its capacity by stage (operational, construction, tendered) and by technology in MW, the capacity attributable by published equity share over the projects that publish one, and recent change-ledger entries across its projects. Spellings of one company (EDF and EDF Renewables; SAPCO, Aramco Power and Saudi Aramco Power) are read as one. Stage totals count each project’s whole capacity; never add them across companies. `coverage` lists the company’s Saudi captive and corporate projects and its GCC projects, with capacity as each source states it; those are not in the stage totals. A company named only there (ENGIE, TAQA, DEWA …) is answered too.
  - after: One developer or shareholder named in the Saudi Renewables Tracker, by the slug on its page (acwa-power, masdar, edf-renewables, saudi-aramco-power …; search_projects returns developers as published). Returns every project that names it with the equity share the developers publish, its capacity by stage (operational, construction, tendered) and by technology in MW, the capacity attributable by published equity share over the projects that publish one, and recent change-ledger entries across its projects. Spellings of one company (EDF and EDF Renewables; SAPCO, Aramco Power and Saudi Aramco Power) are read as one. Stage totals count each project’s whole capacity; never add them across companies. `coverage` lists the company’s Saudi captive and corporate projects, its GCC projects and its projects in the Regional Renewables Tracker, with capacity as each source states it; those are not in the stage totals. A company named only there (ENGIE, TAQA, DEWA …) is answered too.

Full history: https://api.protogrid.dev/v1/servers/sa.com.renewablevision%2Frenewable-vision/changes

## Remotes

- https://renewablevision.com.sa/api/mcp (streamable-http, auth none, reachable true, uptime30d 1)

## Packages

_none_

## Tools (28)

- `aggregate_projects`: Count projects, add up their stated capacity or their disclosed investment, grouped by country, place, stage, technology, sector, developer, year (of commercial operation) or source (tracker), optionally split by stage, technology, sector or country, over any filter find_projects takes. Computed by the same engine as the site’s assistant, so the figures equal the ones /assistant gives for the same question. The units rule: capacity is added within one family only, MW, MWp and MWac as each source states them, or one other unit alone (MWh, t/yr, m3/day); MWh is never added to MW and heat (MWth) never to electricity. Every answer says how many matching projects were not counted and why (no figure in the unit, a figure its source says must not be added up, no stated year), the method in words, the trackers it rests on with their pages, and the date the newest row was read. Answers anyone: these are aggregates, as the tracker pages print them; the rows themselves are find_projects.
- `equipment_trade`: Imports into Saudi Arabia, the UAE, Oman, Qatar, Kuwait and Bahrain from 2015 of PV cells and modules, lithium-ion cells, wind turbines, static converters, electrolysis machines and large transformers, by product group, year and the five largest partners (partner `WLD` is the total). US dollars as declared (CIF). Derived aggregates only: UN Comtrade does not allow its rows to be republished. HS 850440 and 854330 are broad codes and HS 854140 (before 2022) includes LEDs; the note says so.
- `find_projects`: Search and filter the whole project index, the one the site’s assistant reads: the Saudi, captive, GCC, Regional and World Renewables Trackers, Saudi battery storage, the Saudi, GCC, Regional and World Data Centre Trackers, the CCUS tracker, the IEA hydrogen map and the Saudi water, AI and dedicated-systems registers. Filter by free text, place (a country, gcc, mena …), sector, technology, stage or a stage range, commercial operation date range, developer, or one tracker; or pass the /data/projects query string as filter. Returns the matching rows, each with its id, capacity in the unit its source states, stage, country, developers, commercial operation date, its page, its dataset page, the publication it rests on (sourceUrl) and the date it was read (asOf), plus the trackers the rows come from with their own as-of dates. Page with limit and offset. For counts and totals use aggregate_projects, which never sums MWh with MW; for one project’s full facts and every source use get_project. Free with membership, like the project index: it answers a request carrying a member’s API key and refuses one without, except when tracker is global-ccus or iea-hydrogen.
- `fleet_outlook`: The week ahead for the tracked Saudi solar fleet: expected generation against the long-run normal, day by day, with the peak temperature forecast at the main load centres. Computed from an irradiance forecast, NASA POWER normals and each plant’s own published annual generation.
- `gcc_emissions`: National greenhouse gas emissions of the six GCC states by year: Climate TRACE by sector (power, fossil-fuel-operations, manufacturing and others; MtCO2e, 100-year basis), the Climate Watch historical series by sector, and Our World in Data per-person and intensity indicators. Every row names its source; the methods differ, so never add one source to another. National aggregates only.
- `gcc_series`: Annual country series for Saudi Arabia, the UAE, Oman, Qatar, Kuwait and Bahrain: installed solar, wind and renewable capacity (IRENA, MW); solar and wind generation (TWh), their shares of electricity, demand in total and per person and the carbon intensity of electricity (Our World in Data); CO2 per person, population and renewable share of final energy (World Bank). Each metric carries its publisher, licence and unit; a year not reported is absent, never zero. Narrow by metric, country and years. The country layer of the Energy Atlas, free with membership: it answers a request carrying a member’s API key and refuses one without.
- `get_brief`: One week’s brief at its permanent address, by ISO week, e.g. 2026-W38. A brief never changes after the Sunday it was written, so it is safe to cite. Call list_briefs for the weeks published.
- `get_company`: One developer or shareholder named in the Saudi Renewables Tracker, by the slug on its page (acwa-power, masdar, edf-renewables, saudi-aramco-power …; search_projects returns developers as published). Returns every project that names it with the equity share the developers publish, its capacity by stage (operational, construction, tendered) and by technology in MW, the capacity attributable by published equity share over the projects that publish one, and recent change-ledger entries across its projects. Spellings of one company (EDF and EDF Renewables; SAPCO, Aramco Power and Saudi Aramco Power) are read as one. Stage totals count each project’s whole capacity; never add them across companies. `coverage` lists the company’s Saudi captive and corporate projects, its GCC projects and its projects in the Regional and World Renewables Trackers, with capacity as each source states it; those are not in the stage totals. A company named only there (ENGIE, TAQA, DEWA …) is answered too.
- `get_project`: Everything the site holds on one project, by its id from find_projects, search_projects or a project page (/data/projects/{id}), whichever tracker lists it: name, sector, technology, capacity as stated with any other ratings and what the figure covers, stage with the source’s own words, place (locality and region only, never coordinates), dated milestones (planned or actual), disclosed investment, published tariff or levelised cost, the companies and their roles and published shares, the owner’s sourced facts, and every publication the row was compiled from with the date it was read. asOf is the date the tracker last read the project. Answers anyone, as the project’s public page does.
- `get_register`: Rows from one official Saudi register as this platform last mirrored it. register: sppc (Saudi Power Procurement Company, the Principal Buyer — every solar and wind project with its contracted capacity in MW and status connected|construction), swpc (Saudi Water Partnership Company / SHARAKAT — independent desalination, sewage treatment, transmission and strategic storage projects with capacity, regions, commercial operation year, contract model and published tariff; status operation|construction|tendering|planning), swa (Saudi Water Authority open-data catalogue — every dataset the authority publishes, with formats and resource counts; these rows carry no status). Use this rather than a tracker when the question is what the publisher itself lists.
- `get_report`: One report at its permanent address: the caption as prose, the definitions of its headline figures quoted from its own notes, its sources, the cover and the public preview pages. Its figures are as filed on contentUpdated; the live dashboards are separate tools and may read differently. Public fields only — the PDF and the data pack stay behind free membership.
- `get_series`: One statistical series this platform mirrors from a publisher (the KAPSARC energy data portal, JODI, IRENA, the IMF, the IEA, the World Bank, Our World in Data, the CFTC, Climate TRACE, UN Comtrade), with its publisher, unit, licence, period range, a summary over the window (latest value per category, minimum, maximum, first-to-last change) and its newest points. Narrow the window with from and to, written as YYYY, YYYY-MM or YYYY-MM-DD. Series ids come from list_datasets.
- `latest_brief`: The current weekly energy brief: its subject, the figures it opens on, every block of its text and the permanent page for the week. Compiled every Sunday from the change ledger — what moved, what the registers did, what is due. Use it for "what happened this week in Saudi energy".
- `list_briefs`: Every weekly brief published, newest first, with its ISO week, the Sunday it covers up to, its subject in both languages and its page. Use it to find the week to pass to get_brief.
- `list_changes`: Every row-level change this platform observed in an official register, a mirrored series or a tracker since a date, newest first, with the value on both sides and the size of the move. This answers "what moved since I last looked" in one call. Magnitudes carry their own unit and are not comparable across units — a water plant’s cubic metres a day are not megawatts.
- `list_datasets`: The catalogue of everything this platform publishes: each dataset with its id, title, topic, publisher, licence, coverage, record count, refresh cadence and the page it is published on; each mirrored statistical series with its id, publisher, unit and period range; and the three official registers mirrored weekly. Call this first when you do not yet know which dataset, series or register holds the figure you need — get_series and get_register take their ids from here.
- `list_reports`: The report library: every report this company has filed, newest edition first, with its id, title, summary, scope, sector, edition, the date its figures were compiled, page count and cover. Public fields only — each report’s PDF and data pack are free to members and are named by their member download route. Pass an id to get_report for the quoted definitions and the sources.
- `news_mentions`: Recent headlines on Saudi and GCC energy (renewables, storage, hydrogen, power, oil and gas, water, data-centre power), gathered every three hours from publishers’ own feeds and the GDELT Project: the headline, its link, the publisher’s domain, the date and the language only. Filter by a tracked project id or a company slug; a headline is tagged only when it names the project or company unambiguously. Headlines belong to their publishers: cite the link, and do not treat a headline as a verified fact.
- `oil_balance`: This platform’s oil balance model run on its live inputs: the lever set, a summary, and the monthly path of anchor, price, band, demand, supply, stock change and inventories, with the source and status of every input. scenario: base, tight (stronger demand against tighter supply), transition (weaker demand with more displacement) or flood (more supply and more elastic shale). The path is modelled and indicative; the inputs and the anchor are published data.
- `oil_outlook`: This platform’s oil price and production strategy model: Brent today, the model’s monthly path for the next 24 months under current Saudi and OPEC+ policy (anchored to the EIA outlook and the futures strip, with the unanchored structural path beside it) with a Monte Carlo fan (P10–P90), the OECD stocks and balance behind it, the EIA Short-Term Energy Outlook and the WTI futures strip as benchmarks, World Bank and IMF price assumptions, the inventory–price calibration with its fit statistics, and what changed since the previous EIA outlook. Modelled scenario analysis, not a forecast.
- `oil_scenario`: Runs one preset Saudi production path through the model and returns what it implies: Brent by month for 24 months and by year to 2050, Saudi crude exports, oil revenue, the fiscal balance against the IMF breakeven, market share, spare capacity, the net present value of revenue and the US shale response, with the difference from holding current policy. preset: hold, gradual, accelerated, deeperCut or marketShare. shocks: any of hormuz, recession, chinaSlowdown, hurricane, and {iran|russia|venezuela}-{tighten|ease}. demandScenario: iea-cps, iea-steps, iea-aps, iea-nze, opec-woo or eia-ieo. Modelled scenario analysis under stated assumptions; it describes paths and never recommends one.
- `power_balance`: Saudi renewable capacity operational, under construction and tendered, against the 2030 National Renewable Energy Program target and against the Principal Buyer’s own register, with what changed since last month and which projects the register corrected on stage. With month, the balance as it was stored for that month rather than recomputed.
- `project_output_estimate`: Estimated annual generation (GWh) and capacity factor of solar projects in the Saudi tracker, the GCC tracker and the Saudi captive segment, modelled with PVGIS (EU JRC) at the town or region centroid — never the plant — for a fixed array at the optimal tilt and for a single-axis tracker, with totals by tracker and stage. Pass `project` (a tracker id such as sudair-pv-1500-mw) for one project, or filter by tracker, stage and country. The list of projects is a layer of the Energy Atlas and is free with membership: it needs a member’s API key; one project by `project` answers anyone. Modelled, not measured: quote it as an estimate.
- `search`: Ranked matches across the datasets, the mirrored series, the published insight articles and the tracked projects — the same index the site’s own command palette reads. Use it when you do not know which page or dataset covers a subject; each result carries the page to cite.
- `search_projects`: Match a name, developer, country, region or city across the project trackers and return the matching rows with their capacities, largest first. dataset: renewables (Saudi renewable projects — technology, capacity MW, status operational|construction|tendered|announced, developers, LCOE), captive (Saudi captive and corporate solar: corporate PPAs, plants owned by the factory or farm they supply, plants built into water projects — capacity as the source states it, offtaker, arrangement, status operational|construction|contracted|tendered|announced|observed, sources), gcc (utility-scale solar, CSP, wind and battery projects of 50 MW or more in the UAE, Oman, Qatar, Kuwait and Bahrain — country as ISO code, capacity as stated, procurer, owners and developers, published tariff, the same statuses, sources), regional (the same kind of rows in the Middle East beyond the Gulf, Africa, the Caucasus, Central Asia and South and Southeast Asia — country as ISO code, wind-solar hybrids as technology hybrid, tariffs only in US cents/kWh), world (the same row shape for the flagship projects of every other country — the US, Canada, Latin America, Europe, China, Japan, Korea, Australia and the rest: renewables of 1 GW or more and batteries of 300 MW or 1,000 MWh or more), data-centres (Saudi data-centre records — lead, city, disclosed MW with its basis, investment), ccus (global carbon capture projects — developer, country, capture Mt/yr, sector), hydrogen (the IEA low-emission hydrogen map, mirrored as capacity by year, region and stage rather than as named projects). Omit dataset to search the renewables, captive, GCC, regional, world, data-centre and CCUS trackers at once. Capacity totals are summed only inside one dataset, in that dataset’s own unit; captive, GCC, regional and world capacity is MW as each source states it (MWac or MWp) and heat (MWth) is never added. The renewables, captive, gcc, regional, world and data-centres datasets are free with membership: they answer a request carrying a member’s API key, and refuse one without, as does a search with no dataset named; ccus and hydrogen answer anyone. For every other tracker in the project index (Saudi battery storage, the GCC, Regional and World Data Centre Trackers, the water, AI and dedicated-systems registers), filters by stage, technology or date, and counts or totals, use find_projects and aggregate_projects.
- `solar_resource`: The long-run (2001–2020) NASA POWER climatology for one 0.5° cell (about 55 km): global horizontal and direct normal irradiance in kWh/m²/day, wind speed at 50 m in m/s, air temperature in °C and aerosol optical depth at 550 nm (dust, and so panel soiling), each as an annual mean and by month. Ask by a tracked project id (answered for its locality, never its site), by a place given as "north,east" in decimal degrees, or by a cell id. Area-level only: it is not a site measurement and must not be quoted as a plant’s yield.
- `tracker_summary`: A tracker’s headline figures as its own page prints them, with the date they are true as of, read exactly as the site’s assistant reads them: projects and capacity by stage, and by country for the GCC, Regional and World Renewables Trackers. tracker: saudi-renewables (stages as the page counts them, the Principal Buyer’s register leading where it differs), gcc-renewables, regional-renewables, world-renewables (the flagship projects of every other country), captive-solar, data-centres (Saudi: the 2024 baseline, the flagship records by status and the 2030 scenarios), ccus (capture Mt CO2 a year by stage), storage, hydrogen, water. For any other cut, aggregate_projects. Answers anyone.
- `whats_due`: The publications and milestones this platform expects next: each mirrored source with the date its refresh is due and how many days late it is, and the tracked projects carrying a stated commercial operation year. Schedule facts, not forecasts.