Embed EV charging in your application.

WaveCharge is the API for EV charging. We handle the protocol, the chargers, the roaming, the billing, and the AI operations. You ship the customer experience.

View the Agent API Book a 30-min architecture call

your-app/charging.ts

@wavenetic/wavecharge

import { WaveCharge } from "@wavenetic/wavecharge";

const wc = new WaveCharge({ apiKey: env.WC_KEY });

// Find available chargers near the tenant
const chargers = await wc.chargers.list({
  near: { lat: 46.05, lng: 14.50, radiusKm: 5 },
  available: true,
});

// Start a session under your brand
const session = await wc.sessions.start({
  chargerId: chargers[0].id,
  userId: "tenant_jana_12345",
});

// Same API — AI agents answer operator queries
const status = await wc.ai.query({
  prompt: "any chargers with faults in the last 24h",
});

OCPP 1.6J + 2.0.1OCPI 2.2 roamingREST + GraphQL + webhooksNIS2-alignedSelf-hosted or WaveNode

§02 · What WaveCharge handles

400 pages of OCPP,
hidden behind 3 lines of code.

Building EV charging in-house means twelve months of protocol engineering, vendor adapters, and edge-case state machines. WaveCharge ships that work as an API.

Without WaveCharge

12 months of engineering

OCPP 1.6J — 30+ message types
OCPP 2.0.1 protocol upgrade
Vendor adapters (ABB / Alpitronic / Kempower / Wallbox / others)
Session state machine + reconciliation
Offline charger resilience + message replay
OCPI 2.2 roaming (Hubject / Gireve)
ISO 15118 plug-and-charge
Smart charging profiles + dynamic tariffs
Multi-site fleet topology + load balancing
NIS2 audit log substrate
Anomaly + fraud detection on session telemetry
OCPP log parsing for L2/L3 support
Authorisation flows (RFID / app / plug-and-charge)

With WaveCharge

3 lines of code

const chargers = await wc.chargers.list({ available: true });

const session = await wc.sessions.start({ chargerId, userId });

const insights = await wc.ai.query({ prompt: "any faults?" });

● In production at a Slovenian TSO. Already battle-tested at national-grid scale.

§03 · What's inside

One API.
Three surfaces.

Charging operations as code. White-label everything. AI agents on the same control plane — same audit log, same deployment, same perimeter.

01 · Agent API

Charging operations,
exposed as code.

A clean REST + GraphQL surface for everything you'd do with chargers — sessions, status, tariffs, roaming, reservations, billing. AI agents call the same API as humans, with read · recommend · simulate · execute modes. OCPP, OCPI, and ISO 15118 are hidden underneath. Your dev team writes against business primitives, not a 400-page protocol spec.

REST + GraphQL + signed webhooks + OpenAPI spec
SDKs in Python, TypeScript, Go (Java on the roadmap)
Every action signed, replayable, audit-logged

See the Agent API

02 · White-label

Ship it under your brand.

Every customer-facing surface is fully brandable in a day — driver app on iOS + Android, operator web console, custom domain, push notifications, invoices, email templates. Your dev account on the app stores, your domain in the URL bar, your colors throughout. White-label is the surface. The Agent API is the engine.

iOS + Android driver app (your developer account)
Operator + site-host web consoles
Custom domain, push, invoices, email

See the white-label platform

03 · AI agents on the same control plane

Bring your own model.
Run it in your perimeter.

Every WaveCharge deployment ships with an AI agent layer that handles operator queries, anomaly detection, fraud flagging, and OCPP log triage. The model never leaves your perimeter. Bring Gemma 4, Llama, Mistral, or any GGUF-compatible model. Agents act through the same API as humans, with explicit approval flows on sensitive actions.

Operator copilot — natural-language ops over CPMS data
Anomaly detection — RFID cloning, fraud, hardware tampering
OCPP log triage — root-cause analysis on failed sessions

§04 · Built for your stack

Embed charging
in any application.

WaveCharge powers EV charging behind enterprise apps across six verticals — each with its own integration pattern, none requiring you to become a CPMS operator.

Real estate

EV charging in your tenant and visitor apps.

Office tower visitor app
Shopping mall guest app
Residential complex driver portal

Energy retailers

Chargers in your customer app, your tariffs, your billing.

Residential energy app
Smart-tariff matching
Grid-aware charging

Auto OEMs

Native charging in the car’s companion app.

Pre-loaded driver app
Plug-and-charge ISO 15118
OEM-branded session UX

Hospitality / mall ops

Charging as a guest amenity, branded to your venue.

Hotel guest charging
Mall destination charging
Loyalty-program integration

Fleet operators

Chargers inside your dispatch + telematics stack.

Depot charging
Reimbursement reconciliation
Driver assignment

Smart cities · transit

Citizen mobility apps with embedded charging.

City mobility apps
Bus depot charging
Park-and-charge schemes

Each vertical gets a dedicated integration page in the next sprint. For now, the contact form captures your vertical so we route you to the right engineer.

§05 · Trust anchor

If a national grid trusts it
inside their own perimeter, your app can too.

Slovenia's transmission system operator runs national-grid EV charging on WaveCharge today — fully self-hosted, NIS2-aligned, with AI agents handling operator queries and anomaly detection inside their perimeter. The TSO is the most demanding charging- infrastructure buyer in the EU. They picked WaveCharge.

~70%

less time spent searching the dashboard for fault context

~50%

faster root-cause analysis on Level-2 support tickets

100%

operational data stays in the customer's perimeter

Read the case study

Embed charging.
Skip the OCPP year.

Talk to an engineer about how your app stack — tenant, fleet, energy, automotive, or guest — gets EV charging through one API and your existing brand.