API / EV, V2H & charging API · Kokusai Kogyo
Add energy-cost comparisons for EVs, charging and V2H to your own digital service, with Japan-specific calculation capabilities.
Use Enegaeru as the energy calculation and data component behind your own product: a solar-and-storage configurator, dealer proposal tool, electricity-plan comparison, BEV charging service or commercial project workflow.
Collect location, demand, equipment and comparison assumptions through your own interface.
Connect the supported demand, PV generation, energy-balance and tariff calculations for the selected use case.
Present comparisons and connect the outcome to a quote, application, CRM or project review.
Centralizing supported calculation logic and data maintenance helps teams standardize proposals across products and channels. Agree the API specification, licensed data, update behavior and validation cases before deployment.
A battery electric vehicle (BEV) can change both mobility costs and household electricity demand. Vehicle-to-home (V2H) adds another decision: when and how the vehicle battery is available to supply the home.
For automakers, charging providers, homebuilders and energy retailers, compare driving patterns, charging timing, electricity tariffs, rooftop solar and stationary batteries within the supported scope. Explain the assumptions behind household energy-cost changes, rather than treating the vehicle battery as always available.
Use the EV TCO service for vehicle ownership-cost comparisons, and BizEV for commercial fleet and facility scenarios. Vehicle compatibility, charging hardware, battery use and V2H operating limits must be confirmed for the actual system.
Vehicle total cost of ownership → · Commercial fleets and site energy →
Automotive and charging companies; utilities; connected-home platforms.
Define the user decision first: charging costs, tariff selection or equipment comparison. Validate the endpoints needed for that decision.
Calculation support does not automatically include live vehicle control, scheduling optimization or hardware compatibility certification.
Tell us your customer segment, local operating model and first use case. We will discuss product fit and any additional data, integration, training or specialist work required.
This page is an English introduction. Confirm interface, documentation, report and support languages for the product or engagement. Bilingual outputs and localization should be specified explicitly.
Request a quotation for the product, users or usage, data rights, scope and support you need. Confirm implementation fees, recurring fees, contract term and any project work before ordering.
Tell us what you want to launch in Japan, who will use it, and where the work is getting stuck. We can discuss the right combination of software, APIs, data and specialist support.