NextBillion.ai Platform
Coverage Details

"Coverage: Yes" means that routing services are available in that country using one of NextBillion.ai’s SKUs. These services include routing APIs and relevant traffic data where applicable. It indicates that the country is supported on our platform for route planning and optimization use cases.

NextBillion.ai offers two powerful variants of its Routing API to serve diverse operational needs: Fast and Flexible.
The Fast API is optimized for real-time performance. It returns routing results with low latency and is ideal for high-speed use cases like live dispatching, dynamic re-routing, and on-demand navigation. It supports basic constraints and route preferences — making it lightweight and efficient for scenarios where speed and responsiveness are critical.
The Flexible API is designed for complex and large-scale routing problems. It supports significantly more advanced features and is ideal for batch planning, multi-stop deliveries, and logistics workflows that involve custom business logic. This variant can handle:

• High volume of stops or waypoints
• Truck-specific routing, including height, weight, and hazmat restrictions
• Time-based routing, like time windows for jobs or vehicles
• Route type selection: choose between the fastest or shortest route
• Segment-level speed limits for detailed route analysis
• Extensive “avoid” options such as: sharp_turn, service_road, bounding box areas, left_turn, right_turn, and more
• In short, Fast API is best for instant routing with minimal constraints, while Flexible API is suited for rich, constraint-aware planning and optimization.

Car routing uses road networks optimized for personal or small commercial vehicles, considering general traffic regulations.
Truck routing accounts for commercial vehicle constraints such as weight limits, bridge heights, hazmat restrictions, and truck-only road access. This ensures your routes are compliant and realistic for fleet vehicles.

Live Traffic refers to real-time traffic data including congestion, road closures, and delays. This data is used dynamically during route computation to find the fastest and most reliable paths — especially valuable for dispatch and last-mile delivery use cases.

Historical Traffic data reflects traffic trends based on past patterns (e.g., daily rush hours, weekend slowdowns). It is useful for route optimization in planning scenarios where live data is unavailable or not needed — such as scheduled deliveries or capacity planning.

If your country shows no current coverage or lacks traffic data in the tables, you can reach out to our team. Based on the scale and nature of your requirements, we can deploy the necessary map and traffic data in those regions — ensuring you’re not limited by current availability.

Yes. If you operate in regions not currently supported, we can onboard map data and traffic feeds specifically for your use case. Depending on your scale, this can be done quickly to ensure seamless integration with your logistics or mobility operations.

Yes, we offer you the option to choose between different sets of map data, so you can always operate on the most accurate and relevant maps for your location. This allows you to optimize for coverage, quality, regulation compliance, and routing efficiency.

With Custom Map Data, you can overlay your own business-specific data onto the base map. This includes customer POIs, warehouse layouts, off-road paths, delivery zones, or geofences — enabling highly personalized and operationally intelligent routing.

Choosing the right API depends on your specific operational goals and the complexity of your routing needs.
If your application requires real-time routing with minimal constraints — such as ride-hailing, on-demand delivery, or quick re-routing — the Fast API is your best choice. It's optimized for speed and ideal for low-latency scenarios.
If you’re dealing with complex & large scale logistics — like multi-stop delivery planning, truck-specific routing, or custom constraints such as time windows, skills, and segment-level preferences — the Flexible API is better suited. It provides advanced configurability and greater control over how routes are calculated.
If you're unsure which variant fits best for your geography, fleet, or business workflow, feel free to reach out to our team. We can evaluate your use case and recommend the most suitable combination based on your goals, constraints, and expected scale.

Yes. In several regions, truck-specific restrictions may not be available due to map data limitations. In such cases, routing defaults to car mode. For logistics-heavy use cases, we recommend checking our vehicle mode column or contacting us to add truck data where needed.

Absolutely. Our routing engine supports advanced constraints like time windows, capacity, skills, depot preferences, etc. You can even customize constraint behavior to fit your exact operations — especially when using the Flex API.

Live traffic is refreshed at high frequency (typically every few minutes), ensuring your routes stay current with road conditions. Historical traffic is updated periodically to incorporate long-term trends and behavior across regions.

Reach out to our technical solutioning team. We’ll help you select the best map data, routing API, and vehicle settings for your use case, geography, and industry — ensuring you get the most efficient, compliant, and scalable setup.