Obtain a free API key by registering at developer.nrel.gov; the key is required for all requests
Call the station locator endpoint: GET https://developer.nrel.gov/api/alt-fuel-stations/v1.json?api_key=<API_KEY> with location parameters (location as city/state/zip or latitude+longitude with radius)
Filter by fuel type using the fuel_type parameter (e.g., ELEC for electric, CNG, LPG, HY for hydrogen); combine with status=E for open stations only
Parse the fuel_stations array in the response; for EV stations, key fields include ev_connector_types (CHADEMO, J1772, TESLA, etc.), ev_network, ev_level1_evse_num, ev_level2_evse_num, and ev_dc_fast_num
Use the GET /v1/{id}.json endpoint to retrieve details for a single station by its NREL station ID when you need authoritative data for a known location
Known gotchas
NREL data is sourced from station operators and federal/state programs; update frequency varies and some stations may show as open when permanently closed — treat status as best-effort, not real-time
The radius parameter is in miles by default; combine with the units parameter if your application uses kilometers to avoid returning a larger or smaller area than intended
EV connector type codes (CHADEMO, J1772, J1772COMBO, TESLA) reflect NREL's internal taxonomy; map these to user-friendly names or vehicle compatibility yourself — the raw codes will confuse end users
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