Register as a developer at developers.stellantis.com and review the Connected Vehicle API documentation covering the REST-based architecture and available endpoints
Complete the application and approval process to obtain API credentials; review the data usage terms specific to Stellantis vehicle brands
Implement the OAuth authorization flow to obtain user consent for accessing vehicle data; the owner authenticates through their Uconnect or brand app account
Call the vehicle data endpoints to retrieve telemetry such as location, odometer, fuel or battery level, and door status, parsing the normalized response schema
Issue remote commands (lock, unlock, horn, lights, remote start) via the command endpoints and handle the asynchronous response pattern using polling or callback URLs as documented
Test across multiple brand vehicles (Jeep, Ram, Dodge) as capability sets may vary by brand, model, and connected services subscription level
Known gotchas
Stellantis operates two developer platforms for different brand lineages: developers.stellantis.com for FCA brands (Jeep, Ram, Dodge, FIAT, Chrysler, Alfa Romeo, Maserati) and developer.groupe-psa.io for PSA-origin brands (Peugeot, Citroën, Opel, DS); ensure you are using the correct portal
Vehicle command availability depends on the owner's active connected services subscription (such as Connect ONE or Connect Wi-Fi PLUS); command calls may succeed at the API level but fail silently if the vehicle's subscription does not include that feature
The Stellantis API uses standard REST with OAuth, but the specific vehicle capability schema differs from other OEM APIs — do not assume Smartcar or High Mobility field names map directly
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