Site chargers on real tariff math, not averages
Demand charges and TOU windows make or break charging economics. RateAcuity gives you the verified component detail for each utility that siting and pricing models need.
The problems we take off your plate
Averages hide the demand charge
A site that pencils on average ¢/kWh dies on a $15/kW demand charge. Component-level data shows the real cost curve.
Every market means new tariffs
Multi-state rollouts multiply the research. One standardized source covers every candidate market.
Rates change under your model
A revised rider can flip a site’s economics. Daily monitoring and continuous updates keep your models honest after commissioning.
Model a candidate site on the actual schedule
Pull the exact commercial schedule for the host utility (demand charges, energy tiers, TOU windows, riders) and feed your utilization model real numbers.
- Demand and energy components separated
- TOU windows and seasonal variants
- Riders that hit charging loads
Roll the same model across every market
Because every utility is normalized to one structure, the model you built for one metro runs unchanged in the next fifty. Feed it from the portal or straight through the API.
- One data structure across all markets
- API access for automated site screening
- Continuously updated data to re-score live sites
Built for how your team works
Utility Rate Navigator
A custom research service: we examine each schedule in your chosen utilities and report the best fit with monthly costs, built for service-location decisions like charger siting.
Which path fits you?
Siting teams start in the portal; platforms screening sites at scale run the API.
Research it yourself
Search, view, and export verified schedules across every jurisdiction.
Feed your systems
Pipe standardized rate components straight into your tools and products.
Common questions
Do you separate demand from energy?
Yes, every component is itemized with its unit, so $/kW demand and ¢/kWh energy stay distinct in your model.
Can we screen sites programmatically?
Yes, the API returns the same standardized components, ideal for automated site scoring.
What about rate changes after launch?
Change detection flags any component move on schedules you depend on, with effective dates.