How can we help?

Your API Key is generated automatically upon subscription. You can view your active keys in the Dashboard section under the "Active API Key" panel. Ensure you keep this key private and include it in the api_key parameter for all requests.

Usage is counted per successful HTTP request to our API endpoints (Tiles, OSRM, or Geo). The quota resets every 30 days based on your billing cycle. You can track your current usage and "Over Quota" costs directly on the Unified Analytics dashboard.

• Raster (PNG): Pre-generated images. Easier to use in simple maps (like Leaflet) but heavier on bandwidth and less flexible for styling.
• Vector (PBF): Raw map data points. Requires MapLibre or Mapbox GL JS. It allows for dynamic styling, client-side zooming without blur (overzooming), and smaller file sizes.

If you are using Raster tiles, our native resolution stops at Zoom Level 14. To see sharp tiles at Zoom 18+, you must enable "Overzooming" in your mapping library (e.g., set maxNativeZoom: 14 and maxZoom: 22 in Leaflet). If you are using Vector tiles, they should remain sharp indefinitely.

Yes. To add multiple stops, separate the coordinate pairs with a semicolon ; in the URL path. For example: /v1/car/route/v1/driving/lon1,lat1;lon2,lat2;lon3,lat3.

We currently support three primary profiles via our API endpoints:

• Car: Optimized for standard road vehicles.
• Bike: Considers cycling paths and terrain.
• Foot: Optimized for pedestrian walkways and pathways.

Use the countrycodes parameter to restrict by country (e.g., countrycodes=np). For more specific bounding box constraints, use the viewbox and bounded=1 parameters to define a rectangle area to search within.