Routing engine API reference

This is the deployed routing engine contract, not the separate frontend proxy API. Its paths, request bodies, and responses describe this service only; frontend authentication and proxy conventions are outside this reference.

Start with v2 for single-profile navigation and multi-profile planning. Legacy v1 is deprecated but still supported for existing integrations.

On POST /api/v2/routing/plan, omit profiles for automatic planning: the configured baseline plus successful active alternatives strictly less than 50% longer by distance. An explicit list selects compatibility mode, preserving every requested profile key (including deprecated profiles and NoRoute results) without filtering. Null and empty lists are invalid. The v2 profile catalog includes weights and resolved policies; the deprecated v1 catalog includes weights only.