DEV Community

JustRouting
JustRouting

Posted on

AI Agents Need a Routing Layer: Building Location Intelligence for Southeast Asia

#ai #agents #mcp #routing

AI agents are becoming better at understanding users, planning tasks, and making decisions.

But there is one important limitation:

AI agents do not understand the physical world by default.

They know language.

They can reason about goals.

They can call tools.

But they still need external capabilities to answer questions like:

  • "Which driver should deliver this order?"
  • "What is the fastest way to visit these five locations?"
  • "How long will it take to reach the airport?"
  • "Which warehouse is closest to this customer?"

These are not language problems.

They are routing problems.

And routing is becoming a fundamental capability for AI agents operating in the real world.

From API calls to agent capabilities

Traditional software integration looks like this:

Application → API → Response
Enter fullscreen mode Exit fullscreen mode

A developer writes code:

  1. collect coordinates
  2. call a routing API
  3. parse the response
  4. implement business logic

This works well for traditional applications.

But AI agents introduce a different model:

AI Agent → Tools → Capabilities
Enter fullscreen mode Exit fullscreen mode

The agent does not need to know every API detail.

It needs tools it can discover and use.

This is where the Model Context Protocol (MCP) becomes interesting.

MCP provides a standard way for AI applications to connect with external capabilities.

Instead of building custom integrations for every agent, developers can expose tools that agents can call when needed.

Routing becomes one of those tools.

Why AI agents need routing

Many real-world tasks require spatial reasoning.

Consider a delivery assistant:

"I have 20 orders in Jakarta. Assign them to three drivers and optimize today's routes."

A general-purpose AI model cannot solve this alone.

It needs:

  • address → coordinates conversion
  • road network knowledge
  • travel time estimation
  • distance matrix calculation
  • vehicle routing optimization

A routing layer provides these capabilities.

The AI agent handles the reasoning:

"We have three drivers, 20 deliveries, and a priority customer."

The routing system handles the geography:

"These are the realistic driving times and optimized sequences."

Together they create a complete workflow.

Why Southeast Asia needs a specialized routing layer

Most global mapping platforms are designed for global coverage.

That is useful.

But Southeast Asia has unique routing challenges:

  • motorcycles are a primary transportation mode
  • dense urban areas create complex travel patterns
  • delivery businesses depend heavily on two-wheel vehicles
  • addresses are often less structured than Western markets
  • local road access rules matter

A routing layer optimized for Southeast Asia can provide better building blocks for applications such as:

  • food delivery
  • last-mile logistics
  • fleet management
  • ride-hailing
  • e-commerce fulfillment
  • field service operations

The goal is not to replace global maps.

The goal is to provide the right routing capability for the region where your users actually operate.

Introducing JustRouting MCP Server

JustRouting provides an MCP server that exposes Southeast Asia routing capabilities to AI agents.

The server provides four core tools:

route

Calculate a route between locations.

Example:

"How long does it take to drive from Marina Bay Sands to Changi Airport?"

The agent can geocode the locations and request the driving route.

geocode

Convert human places into coordinates.

Example:

"Find the location of this customer address."

The agent does not need users to provide latitude and longitude manually.

table

Calculate travel-time matrices.

Example:

"Which warehouse is closest to these five customers?"

The agent can compare multiple origins and destinations efficiently.

optimize

Solve vehicle routing problems.

Example:

"Plan today's delivery routes for five drivers."

The agent can use optimization tools instead of manually reasoning through hundreds of possible routes.

Installing the MCP server

Installation:

curl -fsSL https://raw.githubusercontent.com/justrouting/mcp/main/install.sh | sh
Enter fullscreen mode Exit fullscreen mode

Configure your MCP client:

{
  "mcpServers": {
    "justrouting": {
      "command": "justrouting-mcp",
      "env": {
        "JUSTROUTING_API_KEY": "YOUR_API_KEY"
      }
    }
  }
}
Enter fullscreen mode Exit fullscreen mode

Now an MCP-compatible AI client can access routing capabilities directly.

Three examples: from answering questions to making decisions

A routing layer becomes more valuable when an AI agent can use it as a tool.

The agent does not need to understand road graphs, coordinates, or optimization algorithms.

It only needs to understand the user's intent and call the right capability.

Here are three examples.

1. Route: answering real-world travel questions

User:

How long does it take to drive from Marina Bay Sands Singapore to Changi Airport?

The AI agent can use the route tool:

User request
      |
      v
  geocode places
      |
      v
  calculate route
      |
      v
  explain result
Enter fullscreen mode Exit fullscreen mode

The response:

Driving from Marina Bay Sands to Changi Airport takes about
23-24 minutes, covering roughly 19 km.

Route details:
- Main roads: East Coast Parkway (ECP), Airport Boulevard
- Distance: ~19.1 km
- Time: ~23 min 36 s
- Tolls: Yes (ERP charges may apply)
Enter fullscreen mode Exit fullscreen mode

The same question can include transportation preferences:

What if I'm riding a motorcycle?

The agent can switch routing profiles:

Car:
  Distance: ~19.1 km
  Time: ~23.6 min

Motorcycle:
  Distance: ~19.1 km
  Time: ~26.5 min
Enter fullscreen mode Exit fullscreen mode

Or apply constraints:

What if I want to avoid tolls?

The agent can request a different route:

Motorcycle with tolls:
  Distance: ~19.1 km
  Time: ~26.5 min

Motorcycle without tolls:
  Distance: ~21.6 km
  Time: ~35 min
Enter fullscreen mode Exit fullscreen mode

The important part is not the API call.

The agent understands the intent:

  • "drive" → driving profile
  • "motorcycle" → motorcycle profile
  • "avoid tolls" → routing constraint

The routing layer handles the geography.

2. Dispatch: making operational decisions

Now consider a logistics assistant.

A dispatcher asks:

I need to assign a delivery to the closest available driver by driving distance.

Customer:

Mondrian Singapore Duxton
Enter fullscreen mode Exit fullscreen mode

Available drivers:

D1: Marina Bay Sands
D2: Waterford Residence
D3: IKEA Alexandra
D4: VivoCity
Enter fullscreen mode Exit fullscreen mode

A human might estimate based on a map.

An AI agent can calculate the actual driving distance:

Driver  Location              Distance    Drive time

D1      Marina Bay Sands      3.60 km     ~8 min
D2      Waterford Residence   2.78 km     ~6 min
D3      IKEA Alexandra        5.33 km     ~13 min
D4      VivoCity              3.30 km     ~7 min
Enter fullscreen mode Exit fullscreen mode

Recommendation:

Assign D2.

Reason:
- Shortest driving distance: 2.78 km
- Fastest estimated arrival: ~6 minutes
Enter fullscreen mode Exit fullscreen mode

The AI agent handles the business reasoning:

"Find the closest available driver."

The routing layer provides the transportation intelligence:

"These are the real driving costs."

This pattern applies to:

  • food delivery
  • courier dispatch
  • field service
  • ride-hailing
  • emergency response

3. Optimize: planning an entire fleet

The next level is multi-vehicle optimization.

User:

I have two vans available to pick up packages from six customers. How should these pickup tasks be assigned and ordered?

Vehicles:

V1:
249 Sixth Ave, Singapore

V2:
8 Harlyn Rd, Singapore
Enter fullscreen mode Exit fullscreen mode

Customers:

C1: 75 Jln Kelabu Asap
C2: 20 Mount Sinai Rd
C3: 10 Bin Tong Park
C4: 9 Cluny Park
C5: 28 Nassim Rd
C6: 30 Chancery Ln
Enter fullscreen mode Exit fullscreen mode

The AI agent calls the optimize tool.

The routing optimizer returns:

Van V1

Start:
249 Sixth Ave

Route:
C2 → C1 → C3

Total:
~19.4 minutes
Enter fullscreen mode Exit fullscreen mode

and:

Van V2

Start:
8 Harlyn Rd

Route:
C6 → C5 → C4

Total:
~29.0 minutes
Enter fullscreen mode Exit fullscreen mode

Final plan:

All 6 jobs assigned.
No customer left unserved.

Combined fleet driving time:
~48.5 minutes
Enter fullscreen mode Exit fullscreen mode

The AI agent did not manually solve the vehicle routing problem.

It delegated the mathematical optimization to a specialized routing engine.

That is the future architecture:

AI Agent
    |
    |
    +---- Understand user goal
    |
    +---- Call routing tools
              |
              +---- Geocode
              |
              +---- Route
              |
              +---- Matrix
              |
              +---- Optimize
Enter fullscreen mode Exit fullscreen mode

Large language models are good at reasoning.

Routing engines are good at transportation mathematics.

Together they create AI systems that can operate in the physical world.

The future architecture: AI + specialized infrastructure

The future of AI applications will not be one giant model doing everything.

It will look more like this:

                 AI Agent

                    |
        ---------------------------
        |            |            |
    Routing       Payments      Search
      Tool          Tool         Tool

        |
  Specialized Infrastructure
Enter fullscreen mode Exit fullscreen mode

Large language models provide reasoning.

Specialized services provide reliable capabilities.

Routing is one of those capabilities.

Building the physical world layer for AI

The next generation of AI applications will interact with the real world:

  • robots
  • delivery systems
  • transportation networks
  • warehouses
  • field operations

They will need more than text generation.

They will need location intelligence.

A routing layer gives AI agents the ability to understand movement, distance, and time.

For Southeast Asia, that means providing routing capabilities designed around the region's transportation reality.

The future AI agent will not only answer questions.

It will make decisions in the physical world.

And every physical decision needs a map.

Learn more:

Top comments (0)