Frequently asked questions

OSRMRoute is the Maps, Routing and Geocoding API platform by MAMMADOFF AGENCY LLC. We run our own routing engine and geocoders over OpenStreetMap and Overture data on dedicated infrastructure.

Directions & route planning, distance/time matrices, map matching, forward & reverse geocoding, address autocomplete, places/POI search, isochrones, route optimization and location clustering — all over a clean REST API, with SDKs and an MCP server for AI agents.

Create a free account, open your dashboard and generate a key. You can set per-key restrictions (allowed origins/IPs) and see live usage.

Yes. Every account receives a daily free quota for non-commercial tests and personal projects. Paid plans support commercial use and raise quotas and limits.

Open Security in your dashboard, scan the QR code with an authenticator app and confirm its code. Two-factor authentication is optional. Keep recovery codes in a private, safe place; never send them to support.

Driving routes and address search worldwide. Walking, cycling and detailed local data vary by service and region; see Coverage for availability.

Principally OpenStreetMap (ODbL) plus Overture Maps (CDLA-Permissive / ODbL). Routing runs on the open-source OSRM engine; geocoding on our own Nominatim + Photon, enriched with Overture places.

Street and place coverage is strong; house-number precision depends on the underlying open data, which is denser in cities. We enrich coverage with millions of Overture points, and results include coordinates you can map or route to. Outputs are estimates, not survey-grade.

Yes. Request walking/cycling profiles or detailed administrative data on the Coverage page. Driving routes and address search are already worldwide and need no country activation.

Live traffic is not currently included. Route durations are estimates based on available road data and routing profiles. They do not predict current congestion, incidents or a guaranteed arrival time.

Plans include a daily credit quota and a requests-per-minute limit. Credit cost depends on the service. See Pricing for current plans and pay-as-you-go options.

Paddle is our authorized reseller and Merchant of Record. Paddle charges your card, handles VAT/sales tax and issues invoices. Your purchase is also subject to Paddle’s buyer terms.

Yes — Paddle emails a receipt/invoice for every payment, and you can access billing details from the checkout receipt.

See our Refund Policy. There’s a free tier to try before you pay; statutory cooling-off rights are honored where they apply. Requests go to us or via Paddle.

Yes. Subscriptions renew automatically until you cancel; you keep access through the paid period.

Saving a card alone does not buy credits. A confirmed top-up adds prepaid balance. On an eligible active paid subscription, purchased credits cover usage beyond the daily allowance; the top-up itself does not replace that subscription. Review the dashboard confirmation before any plan change.

Check the payment status and billing history first. Do not submit repeated purchases while the outcome is pending or unknown. If it remains unresolved, send support the transaction reference and approximate time, without card details or API secrets.

Each key has credit quotas and requests-per-minute limits tied to its plan. Your dashboard shows consumption, remaining quota and reset information.

Exceeding a request rate or available quota can return HTTP 429. Insufficient prepaid balance returns HTTP 402. Respect Retry-After for rate limits; top up after a 402 instead of blindly retrying, and cache where appropriate.

Yes — restrict a key to specific referrer origins and/or IP addresses from the dashboard to protect it if it leaks.

Yes — official SDKs plus an MCP server (osrmroute-mcp) so AI agents can call routing and geocoding tools directly.

Follow the endpoint documentation. OSRM-style coordinate pairs and GeoJSON use longitude first, then latitude: [longitude, latitude]. Reversing them can put a point in the wrong country or outside the road network.

For 400, check required fields, coordinate order and request limits. For 401, check authentication; for 403, check key restrictions and permissions. For temporary 5xx errors, use bounded retries with backoff for read-only requests. Share the endpoint, time, status and request reference with support, never your API key.

Query content (addresses, coordinates, search terms) is processed transiently to return results and is not kept as a separate profile. We log request metadata (key, endpoint, IP, status, timing) for security and billing. See the Privacy Policy.

We act as controller for account data and as your processor for end-user data you submit through the API, governed by our Data Processing Addendum (DPA). We rely on Standard Contractual Clauses for international transfers.

Wherever you show map or geocoding results you must credit “© OpenStreetMap contributors” and preserve any other required dataset attribution, and comply with the ODbL (including share-alike if you publish a derived database).

Yes, within your commercial plan and the Terms. The free plan is for non-commercial tests and personal projects. You may not resell raw outputs as a competing dataset or systematically rebuild source databases.

Open Tickets in your dashboard to create and follow support requests. Staff replies to tickets are also sent to the email associated with the ticket; check that mailbox and spam folder. You can also email [email protected] or use Contact. Never send passwords, API secrets or full card details.

Yes — for volume pricing, custom coverage or a written service-level agreement, contact us via the Sales option on the Contact page.

Sign in to your dashboard to see service status relevant to your account and APIs. If a request fails, include its endpoint, time and status code when contacting support.

Check that you signed in with the email used to create the ticket. A guest ticket or a ticket opened with another email may not appear in the current account. Contact support with the ticket number so ownership can be verified before linking it.

Yes. Map Studio lets you start with a preset, adjust colors and visible layers, then publish a map and use the available integration code. Keep required attribution visible. Preview the result on the devices your customers use.

You can add supported geographic data in Map Studio or integrate your data in your application. Check the supported formats and limits in the editor. You are responsible for the rights to that data; publishing a map may make its displayed data accessible to visitors. Do not publish confidential locations.