Use the Enode API to link a customer's electric vehicle and read its charge state, battery level, and odometer
domain: developers.enode.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Review the Enode API reference and Brands overview to confirm the target EV brand/model is supported
Follow the Getting Started guide to link a vehicle and make the first API call
Fetch vehicle, charge-state, and odometer/location telemetry via the vehicle endpoints
Issue charging start/stop or max-current commands through Enode's control endpoints
For scheduling or smart-charging features, review Enode's separate Smart Charging and Scheduling guides
Known gotchas
Enode aggregates 45+ EV brands, but exact data field availability differs per brand/model, so validate against the Brands overview before assuming a signal is present
Smart charging and scheduling are documented as separate feature sets from basic vehicle read/control, each with its own guide
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?