Developers
Use EasyRoute from your own code or from an AI assistant. There is a REST API, an MCP server and a UTCP manual. All three use the same API key and the same limits.
Get a key
Open the API keys page, sign in, and create a key there. Keys belong to your account, and you can have up to 5. A key is shown once, when you create it, so copy it then. EasyRoute stores only a hash of it. You can revoke a key at any time. Keep it secret: send it in a header, never in a web address.
Quick start
Put the stops in a shorter order:
curl -X POST https://easyroute.ae/api/v1/optimize \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"start": {"lat": 25.2048, "lon": 55.2708},
"stops": [
{"name": "A", "lat": 25.1972, "lon": 55.2744},
{"name": "B", "lat": 25.2285, "lon": 55.3273},
{"name": "C", "lat": 25.1124, "lon": 55.1390}
]
}'
The answer lists the stops in the order to visit them, with an arrival time for each, the distance and time in total, and an estimate of what the new order saves. Distances and times are estimates, not live traffic.
| Request | What it does |
|---|---|
| POST /api/v1/optimize | Orders the stops |
| GET /api/v1/geocode?q= | Finds an address |
| POST /api/v1/routes/link | Makes a link a driver can open |
| GET /api/v1/usage | Plan, limits and today's use |
The full description is the OpenAPI document. It covers only this public API. Every error has the same shape: {"error": {"code": "...", "message": "..."}}. The code is stable, the message is a sentence for a person. Limit errors also say which limit it was and where to upgrade.
Use it from an AI assistant (MCP)
EasyRoute is an MCP server at https://easyroute.ae/mcp (Streamable HTTP, no sessions). It has four tools: optimize_route, geocode_address, create_route_link and get_usage. Listing the tools needs no key. Calling them does.
For a client that reads an mcpServers file:
{
"mcpServers": {
"easyroute": {
"url": "https://easyroute.ae/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
}
For Claude Code:
claude mcp add --transport http easyroute https://easyroute.ae/mcp \
--header "Authorization: Bearer YOUR_API_KEY"
Sign-in with OAuth, as some connector directories need, is not available yet. Use an API key.
UTCP
The UTCP manual is at https://easyroute.ae/utcp. It describes the same four operations as HTTP calls to the REST API. The key is not in the manual: it asks the caller for a variable named EASYROUTE_API_KEY.
Limits
Limits follow the plan of the account that owns the key. Optimizations through the API and in the apps count against the same number for the day.
| Free | Pro | |
|---|---|---|
| Stops per route | 4 | ∞ |
| Optimizations per day | 3 | ∞ |
| Time windows and priority | — | Yes |
| Address search and route links | Yes | Yes |
| Requests per minute, per key | 30 | 30 |
| API keys per account | 5 | 5 |
The day starts and ends at 00:00 UTC. A fair-use ceiling of 1,000 stops a route applies to everyone. The free full optimization in the apps is not available through the API.
Pro
EasyRoute Pro lifts the limits above. It is bought in the iPhone app, and the web app does not sell it yet. Pro follows your account: sign in to the web app with the account you use in the iPhone app, and your keys get the Pro limits. If Pro ends, they go back to the free limits.
Privacy
The server uses the stops you send only to answer the request and does not store them, except for a route you turn into a link, which is kept for 7 days. See the privacy page. Questions: support@easytech.ae.