Present compatible POIs
Match vehicle inlet and charging capability to connector standard, current type and power.
FOR OEM & INFOTAINMENT TEAMS
Charging data for in-vehicle EV experiences
Build a consistent charger-search experience across fragmented networks and changing market coverage.
In-vehicle charging search needs a stable data contract even when operators publish different identifiers, status values and tariff structures. The driver should see a coherent result, not the quirks of every upstream feed.
Data for EV maps operator records into one canonical model and preserves the connector-level detail needed for compatibility. Automotive teams can consume the same hierarchy as an API or bulk dataset and project it into their own POI model.
DECISIONS
What this data helps your team decide
Improve driver confidence
Display access, operator, live availability, pricing and freshness in one predictable interface.
Expand market coverage
Add operator feeds behind a stable canonical contract instead of changing the vehicle schema.
DATA MODEL
Fields relevant to this workflow
Every field remains attached to the station, EVSE, connector or tariff entity it describes.
- POI identity
- Station name, coordinates, address, operator and stable source references
- Vehicle fit
- Connector standard, AC/DC current, power, voltage and amperage
- Driver context
- Availability, price, access restrictions, parking and amenities
- Data quality
- Provenance, observation timestamps and normalized status values
WORKFLOW
How it fits into your product
-
1
Ingest
Receive a normalized API response or scheduled bulk export.
-
2
Transform
Map the canonical hierarchy into the OEM or head-unit POI model.
-
3
Localize
Apply vehicle, market, language and presentation rules in your product.
-
4
Update
Refresh dynamic fields independently from slower-changing station metadata.
Evaluate the data for your workflow
Share your markets, required fields and delivery cadence. We will map the request to available coverage.
Request a data quote