Register for ABRP API access at abetterrouteplanner.com and obtain an API key from the developer portal.
Select the target vehicle by querying the vehicle model list endpoint to retrieve the ABRP vehicle model ID (e.g., using make, model, and year parameters).
Call the route planning endpoint with origin and destination coordinates, vehicle model ID, initial state-of-charge percentage, and optional waypoints.
Parse the route response: extract charging stops (station name, network, plugType, arrival SoC, charge time, departure SoC) and total trip duration.
Display the route on a map with charging stop markers; show estimated arrival SoC at each stop and at the destination.
Handle the 'no-route' or 'insufficient-range' error by either lowering the minimum-arrival-SoC setting or adding a manual intermediate waypoint.
Known gotchas
ABRP route quality depends on accurate vehicle consumption data; always pass real-time weather and wind data if available, as range estimates can vary significantly in cold weather.
ABRP's free API tier is rate-limited and intended for testing; production traffic requires a paid plan — review pricing tiers before deploying.
Charging station availability data in ABRP is sourced from third-party networks (PlugShare, OCPI feeds) and may lag real-time occupancy; advise users to verify stall availability at the station.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp