Find charging stations via the NLR (formerly NREL) Alternative Fuel Stations API
domain: developer.nlr.gov · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Request a free API key at developer.nlr.gov (note: the domain migrated from developer.nrel.gov to developer.nlr.gov, with the old domain fully retired May 29, 2026; update all existing references accordingly).
To retrieve all EV stations matching a location query, send GET https://developer.nlr.gov/api/alt-fuel-stations/v1.json?api_key={yourKey}&fuel_type=ELEC&location={cityOrZip}&radius={miles}.
To find the nearest stations to a coordinate, send GET https://developer.nlr.gov/api/alt-fuel-stations/v1/nearest.json?api_key={yourKey}&fuel_type=ELEC&latitude={lat}&longitude={lng}&radius={miles}&limit={n}.
To find stations along a driving route, send POST https://developer.nlr.gov/api/alt-fuel-stations/v1/nearby-route.json with a GeoJSON LineString representing the route in the request body along with the api_key and fuel_type parameters.
To retrieve a specific station by its ID, send GET https://developer.nlr.gov/api/alt-fuel-stations/v1/{id}.json?api_key={yourKey}.
Filter results using query parameters such as ev_network (charging network name), ev_connector_types (CHADEMO, J1772, TESLA, etc.), access (public or private), and status (E for open).
Known gotchas
The API domain changed from developer.nrel.gov to developer.nlr.gov (the old domain was fully retired May 29, 2026 with no redirect); requests to the old domain fail outright. Update all hardcoded URLs — your existing API key continues to work unchanged under the new domain, no re-registration or key regeneration is needed.
Station data is self-reported by network operators and may lag actual site status; a station listed as open may be offline or under construction — treat the data as a discovery tool, not a real-time availability feed.
Connector type filters use the API's own enum values (J1772, CHADEMO, J1772COMBO, TESLA); do not assume that standard connector names from other data sources map directly to these enum values without consulting the API documentation.
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?