Every so often someone emails me asking for a route optimization API — they want to hit an endpoint from their own app, get routes back as JSON, and skip the whole “upload a spreadsheet” workflow entirely. Fair ask. But before you go shopping for one, it’s worth understanding what you’re actually paying for, because “API” in this space covers everything from a thin wrapper around a free library to a genuinely expensive enterprise platform.
What a route optimization API actually is
Strip away the marketing and a route optimization API is a web service that does what my browser-based tool does — take stops, vehicles, and constraints, run a solver, return optimized routes — except it’s designed to be called programmatically from your own software instead of clicked through in a browser. You send a request with your data, you get back an assignment of stops to vehicles and a stop order for each one, and your app does whatever it wants with that (dispatch it to a driver app, print it, feed it into a bigger system). The value isn’t the optimization itself — it’s the integration. You’re paying to not build a form.
The solver underneath is usually the same one
Here’s the part that surprises people: most commercial route optimization APIs aren’t running some proprietary secret-sauce algorithm. A large share of them are built on the same class of open-source routing engines I use for my own tool — Google’s OR-Tools being the most common, alongside a handful of other constraint solvers. What you’re actually buying with a paid API is infrastructure: uptime, request scaling, a support contract, prebuilt SDKs in six languages, and someone else’s servers running the OSRM-style road-network lookups so you don’t have to host them. That’s genuinely valuable if you’re shipping a product. It’s not valuable if you’re a five-truck operation trying to plan Tuesday’s routes.
What it actually costs
Commercial route optimization APIs are almost universally priced per request or per stop, and the free tiers are thin — a few hundred optimization calls a month before you hit a paywall, which sounds like a lot until you realize a single day’s routing for one delivery operation can burn through dozens of calls during testing alone. For a business already running the numbers, that’s a real, ongoing line item, not a one-time tool purchase.
The third option nobody mentions: self-hosting the solver
There’s a middle path between “pay per call” and “click a website” that gets skipped in most comparisons: if you have engineering capacity in-house, you can run the same open-source solver yourself. Google OR-Tools is a free library, not a hosted service — you install it, write the constraint model, and call it from your own backend, with no per-request bill and no vendor lock-in. The trade-off is real: you own the infrastructure, the road-network data lookups, the uptime, and the debugging when a solve behaves strangely at 2 a.m. For a team with a developer who can dedicate real time to it, this is often cheaper long-term than a metered API and gives you full control over the constraint model instead of whatever knobs a vendor’s API happens to expose. For a team without that capacity, it’s a worse deal than either of the other two options — you’re trading a monthly bill for an ongoing engineering commitment, and that’s not free either, it’s just a different currency.
Do you actually need the API, or just the answer?
This is the question worth sitting with before you write any integration code. If you need routes inside your own software — a driver app, a dispatch dashboard, something customers interact with — yes, you need something API-shaped. But if what you actually need is a good route for tomorrow, an API is solving a problem you don’t have yet. My own free route optimizer covers that second case directly: upload a workbook, get routes back, no integration required, no per-call bill. I’m also working on a lighter-weight, paste-your-addresses version for people who want something closer to embeddable without a full API contract — a middle ground between “spreadsheet upload” and “full REST API” — more on that once it’s live.
Where I’d actually draw the line
If your product’s whole pitch depends on routing being invisible and automatic inside someone else’s workflow, pay for the API — that’s exactly the problem those platforms exist to solve, and building it yourself on a shoestring is a bad use of engineering time. If you’re solving your own delivery routes and nobody outside your company ever needs to see a JSON response, you almost certainly don’t need one. I don’t currently expose a public API on my own tool — it’s on the list, not shipped — and I’d rather say that plainly than dress up a file-upload tool as something it isn’t yet.
Questions worth asking before you sign up
If you do land on “yes, I need an API,” a few questions separate a good fit from an expensive mistake. Does pricing scale per request, per stop, or per vehicle — and which of those matches how your usage will actually grow? Does the API natively support the constraints you have (capacity, time windows, multiple vehicle types), or will you be bolting logic onto the outside of it to compensate for gaps? What does the free or trial tier actually let you test at realistic volume, not toy examples? And can you get your own historical stop data back out in a format you control, in case you ever want to switch providers or bring the solving in-house later? None of these are exotic questions, but they’re the ones that separate “this saved us money” from “we’re locked into a bill that grew faster than our business did.”
Twenty years of building these models has taught me the same lesson from a different angle every time: the fanciest-sounding option is rarely the one that actually needed to exist for your specific problem. Figure out which case you’re in before you sign anything.
Things that I use, like, and am affiliated with:
Mint Mobile offers great cell phone service for $15 flat, get $15 off using the link. Get discounted phones with service activation and no contract.
I never spend money before I check Mr Rebates or Rakuten to get cashbacks, rebates, discounts, coupons or cheaper gift cards.