BatteryArb API
Book Demo Request Pilot
Battery market intelligence for revenue-critical operations

Know when a battery should charge, discharge, or wait before the next 5-minute interval.

BatteryArb gives battery asset managers, operators, VPP teams, and trading desks one place to see short-horizon price signals, outage stress, congestion risk, and the next best operating posture.

Why buyers care: better interval decisions, fewer avoidable bad intervals, faster pilot evaluations, and a cleaner path from analysis into live operating workflows.
Operator uplift

Make a battery desk more consistent without asking your best operator to carry every shift.

BatteryArb packages interval drift, outage regime, congestion pressure, confidence, and clear hold-or-act guidance into one operating layer so teams can make better 5-minute decisions without depending on one person to interpret the whole market by hand.

Explain why posture changed Flag when not to chase price Surface the next best action fast
Why this earns budget

BatteryArb is built for portfolio managers and operating teams that already have people, process, and assets in market.

The product value is not another dashboard. It is a repeatable decision layer that learns from realized outcomes, improves outage-aware forecasts, and helps the existing team capture more value with fewer avoidable bad intervals.

Self-learning loop

Calibrate by regime

Post realized production outcomes back into the API so bid and offer posture tightens by ISO, location, time bucket, and outage regime.

Outage forecast learning

Learn what actually stressed the grid

Use realized outage slope, reserve posture, and price reaction to improve how tomorrow's stressed windows are flagged and forecast.

Existing team leverage

Raise desk consistency

Help asset managers institutionalize senior operator judgment so results do not depend on one person seeing every market signal first.

Evaluation Sandbox: the live product demo automatically falls back to anonymized sample scenarios so charts, JSON panels, and quickstart examples remain usable during technical review.

Request Pilot Book Demo View API Docs
API-first Self-learning by market regime Outage forecast learning Enterprise-ready Built for existing ops teams Fast integration

Learning Loop

Turn realized dispatch outcomes into bounded, explainable calibration rather than static threshold drift.

Outage Advantage

Flag outage and reserve stress earlier so the desk can adapt before naive dispatch exposes the fleet.

Team Leverage

Make an existing battery desk more scalable without forcing a dashboard rebuild or adding extra analysts.

Built for the people who have to act on the signal

BatteryArb is positioned around business workflow fit, not generic data coverage. Each buyer type gets a different operational benefit from the same infrastructure layer.

View all solutions
For battery operators

Improve dispatch quality and capture more valuable intervals

Turn interval pricing, outage posture, and congestion flags into more disciplined charge/discharge decisions, better reserve posture, and fewer avoidable bad intervals.

  • Revenue opportunity visibility for morning and evening ramps
  • Outage-aware dispatch guidance for stressed conditions
  • Congestion signals that prevent poor-location execution
For VPP / EMS teams

Deploy signals into automation without a dashboard rebuild

Use BatteryArb as a programmable layer for forecasting, interval-level visibility, and operational policy inputs that fit into orchestration systems and fleet software.

  • Unified access across ERCOT, PJM, MISO, ISO-NE, and IESO
  • API-friendly responses for optimizers, schedulers, and internal tools
  • Fast pilot path for one market before wider rollout
For traders / quant teams

Generate interval-level battery signals and simulate strategy before deployment

Combine 5-minute pricing, similar-day context, outage forecasts, and battery policy simulation to speed up signal research and reduce brittle heuristics.

  • Programmable edge signals with raw JSON output
  • Bid/offer simulation and similar-day scenario support
  • Forecast bands and MAE proxy to help size aggressiveness

Translate market complexity into operational outcomes

The commercial case is straightforward: better interval decisions, less blind exposure, faster evaluation, and cleaner deployment into production systems.

Outcome 01

Improve dispatch decisions

Move beyond static thresholds by incorporating outage regime, congestion warnings, and forecast confidence.

Outcome 02

Reduce bad-interval exposure

Avoid charging or discharging into intervals where outage or congestion posture is deteriorating.

Outcome 03

Simulate before deployment

Test bid/offer ideas and similar-day analogs before those policies reach the live stack.

Outcome 04

Shorten integration cycles

Use API docs, quickstarts, and sandbox scenarios to move from evaluation to pilot faster.

Evaluation Sandbox

A guided sample environment for commercial and technical evaluation. Live data is used when your key is available; otherwise the site switches to anonymized scenarios with the same response shape.

Open quickstart
Scenario 01

Morning ramp dispatch

Evaluate how price drift, forecast confidence, and reserve posture affect early-day charge timing.

Scenario 02

Congestion stress

Review how location-specific congestion warnings should change dispatch and bidding posture.

Scenario 03

Outage-aware bidding

Test a stressed-evening regime where outage forecasts widen the distribution and tighten execution.

Guided Sample Walkthrough

Use a pilot key if you have one. Otherwise this stays in evaluation sandbox mode.

View API Docs
Awaiting availability check

Choose a scenario or run the walkthrough manually.

Edge Score
-
Regime
-
Posture
-
Confidence
-

Executive Summary

Run the guided walkthrough to evaluate posture and signal quality.

Recommended Actions

  • Action guidance will populate here after the walkthrough runs.
Operator Assist

How this makes the desk easier to run

Run the walkthrough to convert raw price and outage data into plain-language operator guidance.

  • Senior-style context and exception handling will populate here.
Guided walkthrough output will appear here.

Outage Risk Readout

No scenario loaded yet.

Forecast Quality Proxy

No scenario loaded yet.

Cost / Profit Snapshot

No scenario loaded yet.

5-Minute LMP + Forecast

Y-axis: price in USD/MWh. X-axis: market local time at 5-minute intervals.

Outages and Reserve Margin

Y-axis: outage and reserve values in MW. X-axis: market local time.

Left chart uses USD/MWh on the y-axis. Right chart uses MW on the y-axis. Both charts are aligned to market local time at 5-minute intervals.

Advanced Output JSON

Cost Tracker Output

Run Cost Tracker to view interval cashflows.

Bid/Offer Simulation Output

Run Bid/Offer Simulation to view strategy output.

Similar Day Analogs

Run Similar Days to view analog operating days.

Outage Forecast Output

Run Forecast Outages to view confidence bands and commentary.

Commercial proof placeholders that speak to buyers

These are intentionally written as replacement-ready proof blocks. You can swap in customer names and real backtests later without changing the structure.

Anonymized case study

Standalone battery operator in ERCOT

Placeholder: pilot team used outage-aware posture guidance to reduce avoidable dispatch into stressed intervals and improve operator confidence during evening ramps.

Benchmark result

Backtest against naive thresholds

Placeholder: compared fixed threshold dispatch to adaptive outage-aware bid/offer logic and tracked margin delta, avoided congestion intervals, and forecast error bands across stressed and non-stressed operating days.

Workflow example

From API signal to operating action

Pull the edge signal, blend it with internal constraints, simulate a threshold policy, and deliver only the approved actions to the control layer or trading desk.

Why teams choose us over manual workflows or generic feeds

BatteryArb is not trying to be a general-purpose market data warehouse. It is optimized for short-horizon, battery-relevant operating decisions.

Capability Manual workflow / spreadsheet Generic market data feed BatteryArb
Battery-specific signal framing Analyst-dependent and slow Usually raw data only Derived arbitrage, outage, congestion, and bid/offer signals
Outage-aware dispatch support Hard to maintain consistently Not usually productized for batteries Built into forecast, sandbox, and operating examples
Self-learning loop from realized outcomes Usually trapped in operator memory or spreadsheets Rarely tenant-scoped or battery-specific Tenant-scoped learning calibrated by regime, with bounded explainable adjustments
Outage forecast learning Manual watchlist work Usually generic reliability context Realized outage trajectory, reserve posture, and stress response fed back into future forecasting
Integration into EMS / bots Custom internal work every time Requires more downstream transformation API-first, normalized, and pilot-ready
Commercial evaluation path Ad hoc Usually broad enterprise sale Sandbox, pilot, then production rollout

Why an existing asset team pays for BatteryArb

BatteryArb is not sold as a dashboard replacement. It is sold as a way to make an existing battery desk more consistent, more teachable, and more responsive to outage-driven market stress.

Self-learning dispatch loop

Bid and offer posture improves with realized production outcomes

The simulator updates thresholds every five minutes using short-horizon trend and realized volatility, and it can also absorb actual production outcomes so posture improves by regime instead of staying static.

Outage forecast learning

Learn which outage patterns actually changed dispatch economics

Outage trajectory, reserve posture, and realized price reaction can be fed back into the forecast stack so the desk gets a more informed view of which stressed windows deserve tighter posture.

Team leverage

Institutionalize senior judgment across the desk

Many pilots are evaluated against targets such as 2-8% dispatch margin lift, fewer avoidable bad intervals, stronger shift-to-shift consistency, and less dependence on one operator spotting the signal first.

Pricing structured like enterprise software, not a hobby API

Start with evaluation, move into a guided pilot, then expand into production access and enterprise support.

View full pricing and rollout

Pricing shown below is synced from Stripe plan configuration.

Evaluation

Sandbox / Evaluation

$20.00 /month

For one evaluator or small technical group proving data quality, API fit, and workflow integration before internal rollout.

  • Live + historical API access
  • Evaluation sandbox, quickstarts, and live docs
  • 120 req/min, hard caps, and email support
Pilot

Pilot / Team

$50.00 /month

For asset teams proving value against a real dispatch, trading, or EMS workflow before broader procurement.

  • 600 req/min for shared team workflows
  • Pilot configuration, implementation help, and ROI framing
  • Best fit for budget approval before production rollout
Production

Enterprise / Production

$90.00 /month

For production teams that need rollout planning, procurement support, and a cleaner path through security review.

  • 2400 req/min baseline and priority onboarding
  • Support for enterprise security and procurement review
  • Annual contract path and SLA discussion as usage stabilizes

What each buying stage is for

Sandbox / Evaluation: technical diligence, integration speed, and early data trust checks.

Pilot / Team: proof of value against one real workflow, one market, and one scorecard.

Enterprise / Production: rollout planning, support path, procurement review, and production controls.

Commercial policy

Pricing model: flat-rate per organization, not per-seat.

Overages stay disabled at launch. Hard caps are better than surprise invoices for early customer trust.

Annual contracts can be offered once a workflow is in production and volume is predictable.

The pilot is meant to pay for itself through avoided bad intervals, stronger consistency, and faster budget decisions.

Enterprise readiness for serious buyers

The site should answer security, integration, support, and operational readiness questions without forcing every buyer straight into an engineering review.

View security and readiness
Security

Token management and safe delivery

Keys are delivered by email, rotate on resend, can be revoked, and should stay on the server side.

Reliability

Live docs, health endpoints, and operational visibility

Public health, Swagger, OpenAPI, and a static docs mirror reduce friction during evaluation.

Integration

Fast onboarding into notebooks, EMS, or internal services

Quickstarts, Postman, and a starter repo reduce the work required to validate real workflow fit.

Start a serious evaluation

Use the form below to request a pilot, book a demo, or start a buyer conversation around pricing, security, and rollout fit.

Pilot and demo qualification

Request Pilot Access

Share the workflow you want to evaluate so the response can be commercially useful.

Book Demo

No request submitted yet.