Retrieve nearby Supercharger sites and estimated wait times for a Tesla using the Nearby Charging Sites endpoint
domain: developer.tesla.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Authenticate a Fleet API partner application and obtain a vehicle-scoped access token covering the target VIN
Wake the vehicle if it's asleep, since location-dependent endpoints require it to be online
Call the vehicle's nearby_charging_sites endpoint to retrieve Supercharger and destination-charging sites near its current location
Parse the returned site list for distance, plug type, and any available wait-time/occupancy fields
Cache results briefly client-side since repeated calls to vehicle-specific endpoints count against your per-vehicle rate limit and cost a vehicle wake if the car is asleep
Known gotchas
Waking a sleeping vehicle to check nearby chargers drains a small amount of battery and counts toward Tesla's command rate limits, so don't poll this on a tight loop
The response depends on the vehicle actually knowing its current location, so location-sharing/location_data permission must be enabled or the call will fail on newer firmware
Site data reflects Tesla's own charging network context and does not include third-party (CCS-only) stations near the vehicle
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?