nempulse

 ⟨3 unchanged words⟩ ":{"date_from":{"description":"Start date, YYYY-MM-DD (inclusive).","format":"date","type":"string"},"date_to":{"description":"End date, YYYY-MM-DD (inclusive).","format":"date","type":"string"},"duid":{ ⟨18 unchanged words⟩ 

 ⟨3 unchanged words⟩ ":{"date_from":{"description":"Start date, YYYY-MM-DD (inclusive).","format":"date","type":"string"},"date_to":{"description":"End date, YYYY-MM-DD (inclusive).","format":"date","type":"string"},"duid":{"description":"Battery DUID, e.g. HPR1HPR1. Use list_bess_units to find it from a station name.","type":"string"}},"required": ⟨5 unchanged words⟩ 

SummaryOne statsprice forevent oneby marketevent_id (take the id from list_events), with the response of every battery that was online, ranked by est_revenue. Event fields are as in list_events. Each battery row has duid, station, region, response (DISCH = discharging, CHRG = charging, IDLE, OFFLINE = no availability), avg_mw (positive is discharge), peak_mw, est_revenue (energy only, sum of MW times price over the event, bygross, idnot MLF-adjusted; excludes FCAS), soc_pct at start and soc_pct_end, availability_mw, fcas_mw (per-intervalaverage FCAS commitment), plus is_commissioning, unit_class and peer_comparable. Check those labels before comparing units. Per-interval dispatch during the event is not exposed).exposed.

 ⟨3 unchanged words⟩ ":{"id":{"description":"Event id, as returned in event_id by list_events.","type":"string"}},"required": ⟨3 unchanged words⟩ 

Fleet-wide snapshot for the NEM battery fleet: unitunit_count, countactive_unit_count, totaltotal_mw, capacitytotal_mwh, revenuefleet_rev_mtd, month-to-dateavg_efficiency_pct, averagelast_interval and spot_prices (latest price per region, $/MWh). Covers month-to-date unless date_from and date_to are given. fleet_rev_mtd is gross spot price.revenue (energy + FCAS + FPP) over that window, whatever its length, despite the name. avg_efficiency_pct is dollar-weighted actual energy revenue as a share of the perfect-foresight optimum (a capture rate), null if the optimisation has not run for the window. Commissioning units are excluded from the efficiency figure unless include_commissioning is true. For one battery use get_battery_detail; for a ranking use get_rankings.

{"additionalProperties":false,"properties":{"date_from":{"description":"Optional. Start date YYYY-MM-DD (requires date_to). Omit both for month-to-date.","format":"date","type":"string"},"date_to":{"description":"Optional. End date YYYY-MM-DD (requires date_from).","format":"date","type":"string"},"include_commissioning":{"description":"Include units still commissioning in the efficiency figure (default false).","type":"boolean"}},"type":"object"}

ListReference list of every NEM-registered grid-scale batterybattery. Call this first to turn a station name into the DUID the other tools need. Returns the whole fleet in one response (no filters): DUID, station, region, MW/MWh, MLF, coordinates, is_commissioning, commercial_context, unit_class, peer_comparable)., rev_per_mw_yr. Caveats on the fields follow. rev_per_mw_yr is trailing 365-day energy + FCAS revenue ⟨264 unchanged words⟩ 

List NEM spot-price events, newest first. An event is a run of 5-minute intervals in one region where the price stays above $500/MWh or below -$200/MWh (short gaps are bridged), typed by its peak price: negative (below -$200), elevated (peak $500 to $1,000), spike ($1,000 to $5,000) or extreme ($5,000 and above). Each event has event_id, optionallyregion, filteredevent_type, started_at, ended_at, duration_min, peak_rrp, avg_rrp and is_open (still ongoing). Filter by region.region, event_type and a date range. By default only event summaries are returned; set include_responses to true to also get how each battery behaved during each event, in which case keep limit small (response rows make the payload large and it is truncated at about 100 KB). Use get_event_detail for one event's battery responses.

{"additionalProperties":false,"properties":{"date_from":{"description":"Optional. Only events starting on or after this date, YYYY-MM-DD.","format":"date","type":"string"},"date_to":{"description":"Optional. Only events starting on or before this date, YYYY-MM-DD.","format":"date","type":"string"},"event_type":{"description":"Optional event type filter.","enum":["negative","elevated","spike","extreme"],"type":"string"},"include_responses":{"description":"Also return per-battery responses for each event (default false).","type":"boolean"},"limit":{"description":"Max events to return (default 5010, max 500).","maximum":500,"minimum":1,"type":"integer"},"offset":{"description":"Skip this many events, for paging (default 0).","minimum":0,"type":"integer"},"region":{"description":"NEM region code: NSW1, e.g.QLD1, SA1 (optionalSouth Australia), TAS1 or VIC1.","enum":["NSW1","QLD1","SA1","TAS1","VIC1"],"type":"string"}},"type":"object"}

AskLast resort for ad hoc questions the other tools cannot answer. Takes a natural-languageplain-English question, aboutgenerates NEMSQL BESSover data;NEMPulse's tables, and returns generatedthe SQL, the result rows and a plain-Englishshort explanation. It is the slowest tool (can take close to a minute) and it is AI-generated, so check the returned SQL before relying on a number. Scope each question to roughlyabout one region-month or less: —wider aggregates spanning more (e.g. a full year by region, or per-day top-N across all regions) risk the generated SQL exceeding itsthe own8 8ssecond executionSQL caplimit, which thisand tool'sa longer timeoutwait does not extend.help. For per-day top-N /or bottom-N questions, phrase them so the generated SQLask usesfor a window function (ROW_NUMBER/RANKROW_NUMBER or RANK) rather than a per-day correlated subquery — the, latterwhich has been observedseen to silently return all-null rows withrows. noQueryable error.data: Onlydispatch dispatch_pricesprices, daily_revenuedaily revenue, optimal_dispatchoptimal dispatch, bess_price_profilebattery andprice market_eventsprofiles areand reachablemarket here;events. theThe market_*market cacheanalysis tables (market_monthly, market_regression,monthly market_corr_trackerspreads, market_daily_priceregressions, market_daily_fleetcorrelations) behind the market-analysis page live in a separate database and are NOT queryable through this tool — a question about them will be recomputed from dispatch_prices instead, which is slower and easy tonot phrasereachable incorrectly.here.

 ⟨3 unchanged words⟩ ":{"question":{"description":"Plain-English question, (max 500 chars).characters. Name the region and date range, e.g. 'Which SA1 battery earned the most FCAS revenue in August 2026?'","maxLength":500,"type":"string"}},"required":[ ⟨3 unchanged words⟩