nempulse

{
  "id": "aix_f5c9cec0e6",
  "name": "nempulse",
  "operator": "(unclaimed - source: registry-official · publisher: au.com.nempulse)",
  "description": "Read-only access to Australian NEM grid-scale battery performance, revenue, dispatch and FCAS data.",
  "depth": 2,
  "status": "unclaimed",
  "last_crawled": "2026-09-26",
  "missing_fields": [
    "pricing",
    "operator.identity"
  ],
  "skills": [
    "general-tools"
  ],
  "protocols": {
    "mcp": "https://nempulse.com.au/mcp",
    "a2a": null
  },
  "pricing": null,
  "regions": [
    "global"
  ],
  "languages": [
    "en"
  ],
  "reputation": {
    "tasks_completed": null,
    "dispute_rate": null,
    "p95_latency_ms": 11608,
    "uptime_30d": 0.9473684210526315,
    "onchain_volume_30d_usd": null
  },
  "aix_score": 0,
  "verification": {
    "identity": "none",
    "health": "probe/24h",
    "pricing": "unknown",
    "last_check": "2026-09-26T14:01:01.315Z"
  },
  "pricing_model": "unknown",
  "links": [
    {
      "label": "homepage",
      "url": "https://nempulse.com.au/"
    },
    {
      "label": "repository",
      "url": "https://github.com/FDSchaefer/bessPerformance"
    }
  ],
  "avatar": "https://github.com/FDSchaefer.png?size=160",
  "socials": [
    {
      "label": "github",
      "url": "https://github.com/FDSchaefer"
    }
  ],
  "profile": {
    "mcp_server": "NEMPulse MCP",
    "mcp_version": "1.0.0",
    "tool_count": 8,
    "tools": [
      {
        "name": "list_bess_units",
        "description": "List every NEM-registered grid-scale battery (DUID, station, region, MW/MWh, MLF, coordinates, is_commissioning, commercial_context, unit_class, peer_comparable). rev_per_mw_yr is trailing 365-day energy + FCAS revenue (NOT FPP), gross (no MLF), divided by Max Cap MW, then annualised over the days the unit actually had dispatch data — not over a fixed 365-day denominator. This is a rough simulator guide, NOT a performance ranking. It is distorted for any unit with is_commissioning=true or commissioned within the last 365 days, because that span-annualisation extrapolates a few months of ramp-u"
      },
      {
        "name": "get_fleet_summary",
        "description": "Fleet-wide snapshot: unit count, total capacity, revenue month-to-date, average spot price."
      },
      {
        "name": "get_battery_detail",
        "description": "Deep-dive metrics for one battery by DUID (e.g. HPR1 = Hornsdale): revenue, dispatch, SOC, FCAS. WARNING: rev_today, energy_rev_today, fcas_rev_today and contingency_fcas_rev_today are MONTH-TO-DATE by default, not daily (matching the rev_mtd keys in fcas_breakdown) — do not report them as 'today's revenue'. throughput_cycles, throughput_mwh, avg_dispatch_price, avg_charge_price and efficiency_pct cover the same window. Pass date_from and date_to (both required together) to scope this window explicitly, e.g. to a single day, instead of relying on the month-to-date default. For a true daily tim"
      },
      {
        "name": "query_nem_data",
        "description": "Ask a natural-language question about NEM BESS data; returns generated SQL, result rows and a plain-English explanation. Scope each question to roughly one region-month or less — aggregates spanning more (e.g. a full year by region, or per-day top-N across all regions) risk the generated SQL exceeding its own 8s execution cap, which this tool's longer timeout does not extend. For per-day top-N / bottom-N questions, phrase them so the generated SQL uses a window function (ROW_NUMBER/RANK) rather than a per-day correlated subquery — the latter has been observed to silently return all-null rows w"
      },
      {
        "name": "get_battery_revenue",
        "description": "Daily gross-spot revenue by market (energy + FCAS) for one battery (DUID) over a date range. Daily grain only. This is the tool for total revenue questions — use get_battery_optimal only for the actual-vs-perfect-foresight benchmark, not as a revenue source (its 'actual' figure is MLF-adjusted and solved-days-only, so it will not match this tool's totals). Each day also carries energy_rev_mlf_adjusted (null if the LP backcast hasn't run for that day yet, not zero) alongside the gross energy_rev, so MLF-adjusted figures are available here too without switching tools."
      },
      {
        "name": "get_battery_optimal",
        "description": "Actual vs LP-optimal dispatch revenue, per-DUID summary, over a date range (energy-only, perfect-foresight benchmark). NOT a revenue-total source — use get_battery_revenue for that. Both the 'actual' AND the 'optimal' figures here are MLF-adjusted (get_battery_revenue's is gross) — the LP's objective is solved on MLF-adjusted prices, not just settled at them afterward — and both cover solved LP days only (days where the solver failed are dropped from both), so the two tools' totals will not match even for the same DUID and date range. The requested date_to may also be silently truncated to the"
      },
      {
        "name": "list_events",
        "description": "List NEM spot-price events (negative, elevated, spike, extreme), optionally filtered by region."
      },
      {
        "name": "get_event_detail",
        "description": "Summary stats for one market price event by id (per-interval dispatch during the event is not exposed)."
      }
    ],
    "profiled_at": "2026-09-26T14:01:01.315Z"
  },
  "unreachable": false
}