Browse High Mobility's Auto API capability categories to identify which vehicle functions, such as charging, climate, diagnostics, doors, or engine data, are relevant before designing your integration's data model
domain: high-mobility.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Review the Auto API capability reference to see the full set of categories High Mobility groups vehicle functionality into
Map the specific categories your product needs, such as charging or diagnostics, to the corresponding capabilities and states in the Auto API
Check per-brand capability support for each category you need, since not every OEM implements every capability
Design your internal data model around the categories you actually use rather than assuming full category coverage across all connected brands
Recheck the capability list periodically, since High Mobility adds and adjusts categories as it onboards new vehicle functionality
Known gotchas
Category and capability names have evolved over time; verify current naming against the live API reference rather than older integration guides
Capability support varies significantly by OEM and vehicle model, so a category existing in the Auto API does not guarantee a given brand implements it
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?