Register a developer application at developer.tesla.com, complete business verification, and host the required EC public key (secp256r1 curve) at https://{appDomain}/.well-known/appspecific/com.tesla.3p.public-key.pem.
Obtain a partner token via the partner authentication endpoint, then call POST /api/1/partner_accounts to register your domain and link the public key.
Obtain a third-party user access token using the standard OAuth 2.0 authorization code flow to get consent from the vehicle owner with scopes that include vehicle_device_data.
Create a Fleet Telemetry configuration by sending a signed POST request through the vehicle-command proxy to /api/1/vehicles/{vin}/fleet_telemetry_config/create, specifying your server hostname, port, TLS certificate, and the fields you want streamed (e.g., Location, Odometer, BatteryLevel, VehicleSpeed).
Run your Fleet Telemetry server (open-source reference implementation at github.com/teslamotors/fleet-telemetry); it receives protobuf-encoded messages over a TLS-secured WebSocket from the vehicle approximately every 500 milliseconds.
To remove streaming, call DELETE /api/1/vehicles/{vin}/fleet_telemetry_config using a partner token.
Known gotchas
Fleet Telemetry requires your server to have a publicly reachable hostname with a valid TLS certificate; self-signed certificates are not accepted by the vehicle.
Model S and Model X vehicles with Intel Atom car computers require firmware version 2025.20 or later for Fleet Telemetry support; older firmware will not connect.
The telemetry configuration must be signed using your registered private key via the vehicle-command proxy; sending the config directly to the REST endpoint without a valid signature will fail.
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