Create a High Mobility developer account and set up a new application in the developer console to receive sandbox credentials
Navigate to the Develop Mode sandbox environment and launch the in-browser vehicle emulator for the target OEM or a generic Auto API emulator
Use the emulator UI to set vehicle state values (such as odometer reading, door lock status, battery level) and confirm your API requests return the expected responses
Implement the OAuth2 authorization code flow using the sandbox credentials, directing the test user through the High Mobility consent screen to authorize your app against the emulated vehicle
Make REST calls to the Auto API using the sandbox token to retrieve or set vehicle state, verifying your data model handles the Auto API normalized schema correctly
Transition to a live OEM vehicle by swapping sandbox credentials for production credentials and completing OEM-specific data sharing agreements
Known gotchas
Sandbox emulators expose all Auto API capabilities regardless of what a real OEM vehicle supports; test against a real vehicle or review the OEM's capability list before assuming all data points are available in production
Auto API level versioning affects available capability fields; check the current API level in the developer console and align your integration to avoid breaking changes on level upgrades
Production access to specific OEM data requires separate data access clearances from each OEM; the High Mobility platform brokers these agreements but approval timelines vary by manufacturer
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