Mmeshbase

EV Charging — DACH / EU

OCPP-aligned, OCPI-clean. A station graph eMSPs and AI can actually use.

Sprawling station fleets, mismatched protocols, missing roaming data. Your stations cleaned, OCPI-aligned, and queryable through one API.

Book a pilotTalk to sales

Standards & protocols we work with

  • OCPP 1.6 / 2.0.1
  • OCPI 2.2.1
  • ISO 15118
  • Plug & Charge
  • OICP
  • OpenAPI

Five pains we keep seeing

What goes wrong between stations, CPOs, eMSPs, and the customer.

Every CPO and eMSP we've talked to runs into some version of these. Most are protocol problems wearing operational clothes — outdated availability, mismatched tariffs, broken roaming.

Pain 1

Station availability lies

An OCPP heartbeat doesn't equal availability. Your eMSP partners report 'available' on stations a customer can't actually use. Trust collapses one bad session at a time.

Pain 2

OCPI integration drift

Each new eMSP partner is a custom mapping job. Tariffs, locations, and EVSEs end up shaped slightly differently per integration.

Pain 3

Connector + tariff mismatches

Connector standards, max power, and tariff structures vary by manufacturer. Mapping mistakes show up at the charging point — wrong tariff, wrong connector, wrong customer.

Pain 4

Session and CDR reconciliation

OCPP session data and OCPI CDRs need to match — for clearing, billing, regulatory reporting. Manual reconciliation eats hours per month, leaks revenue, and risks compliance.

Pain 5

No clean API for navigation, fleet, and AI

Maps want real-time availability. Fleet operators want pre-authorization. AI navigation agents want typed JSON with provenance. OCPI raw doesn't deliver — and shouldn't be exposed externally without governance.

How it composes

From OCPP heartbeats to a governed station graph.

Meshbase ingests OCPP traffic from your stations, normalizes the location/EVSE/connector model, and reconciles sessions to OCPI CDRs. The cleaned graph is queryable by eMSPs, navigation, fleet, and AI.

Stations
OCPP
Normalize
OCPI
Reconcile
API

Stations → OCPP → Normalize → OCPI → Reconcile → API.

What it looks like

OCPI-shaped data, your governance.

Once your stations are normalized, eMSPs and AI agents query availability, tariffs, and sessions through one governed surface — typed, audited, rate-limited, and policy-checked.

01

REST

Plain HTTP under `/rest/v1`. Lowest-friction option for navigation apps, fleet platforms, and reporting partners on legacy stacks.

bash

bashbash
# Available DC fast chargers near a coordinate, with current tariff
curl -H "Authorization: Bearer $KEY" \
"https://api.meshbase.ai/rest/v1/stations?lat=48.137&lng=11.575&radiusKm=5&power=DC_FAST&availability=AVAILABLE" \
| jq '.data[] | {id, evseIds, connectors, tariff, availability}'
02

GraphQL

Federated GraphQL across stations, sessions, and tariffs. Best when partners need precise field selection and typed cross-domain queries.

graphql

graphqlgraphql
query AvailableChargers($lat: Float!, $lng: Float!) {
stations(near: { lat: $lat, lng: $lng, radiusKm: 5 },
         power: DC_FAST,
         availability: AVAILABLE) {
  nodes {
    id
    evses {
      id
      connectors { type, maxPowerKw, status }
    }
    tariff {
      currency
      elements { priceComponents }
    }
    lastSeenAt        # OCPP heartbeat freshness
  }
}
}
03

MCP

Model Context Protocol — AI routing and fleet agents call your station graph as a typed tool, under the same caller-governance and audit as a human partner.

json

jsonjson
{
"tool": "find_available_chargers",
"arguments": {
  "near": { "lat": 48.137, "lng": 11.575, "radiusKm": 5 },
  "power": "DC_FAST"
}
}

Two sides, one platform

Whether you operate stations or consume them.

Most charging ecosystems involve both sides. Meshbase keeps the two separated where it matters (governance, billing, OCPI roaming) and unified where it helps (data model, API surface).

01 · If you operate stations

You're a CPO running stations under OCPP. Your fleet is your asset — make it queryable, roamable, and partner-ready.

  • Connect OCPP 1.6 / 2.0.1 backends, station feeds, OCPI partners
  • Normalize EVSE / connector / tariff models across vendors
  • Reconcile OCPP sessions ↔ OCPI CDRs for clearing and billing
  • Govern eMSP, navigation, and AI access via API plans, caller profiles, and audit
Pilot as a CPO

02 · If you consume station data

You're an eMSP, navigation system, fleet operator, or AI mobility agent. Subscribe to verified CPO feeds without bespoke OCPI per partner.

  • Marketplace of OCPP/OCPI-aligned CPOs
  • REST · SDK · CLI · MCP — pick what fits your stack
  • Streaming + webhook updates for availability, tariff, and session events
  • One bill, multiple CPOs, governed quotas
Browse the catalog

Charging FAQ

Industry-specific questions we hear most.

DACH-first, OCPI-ready

Bring a station feed. We'll show you the normalized graph by next week.

Email, contact form, or LinkedIn. We respond within one business day and don't waste your time with a generic deck.