Install Jentic One Beta

Connect the Longdo Map API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Longdo Map API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fmap.longdo.com%2Flongdo-map" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fmap.longdo.com%2Flongdo-map" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Longdo Map API.

Geocode a street address or place name into latitude and longitude coordinates

Reverse geocode a single coordinate or a batch of coordinates into structured addresses

Extract a structured address from free-form text with the smart address extractor

Search nearby points of interest and return suggestions as a user types

Plan a route with turn-by-turn guidance, snapped road paths, and a route matrix

GET STARTED

Start building with Longdo Map API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Longdo Map API for, with concrete tasks.

★ Location tools for an AI agent

Give an AI agent the ability to turn addresses into coordinates and back, find nearby places, and plan routes across Thailand without hand-wiring the Longdo Map query-key auth. Through Jentic the agent discovers the geocoding, search, and routing operations by intent and calls them with a validated input schema, so a travel or delivery assistant can answer 'where is this' and 'how do I get there' in one flow.

Geocode the address '1 Sukhumvit Road, Bangkok', then find the driving route from that coordinate to Suvarnabhumi Airport and return the turn-by-turn guide

Address geocoding and cleanup

Convert user-entered addresses and place names into precise coordinates, and reverse geocode raw GPS points into structured Thai addresses. The smart extractor pulls house number, road, district, and province out of free-form text, which is useful for cleaning imported contact lists or normalising delivery addresses before storing them.

Reverse geocode a batch of 20 delivery GPS coordinates into structured addresses and flag any that fall outside Bangkok

Route planning and traffic-aware logistics

Plan delivery and travel routes with turn-by-turn guidance, snap noisy GPS traces back onto the road network, and build a travel-time matrix between multiple stops. Reachable-area spans and live traffic-speed lookups let a logistics tool estimate how far a vehicle can travel in a time budget and adjust for current congestion.

Build a travel-time matrix between four warehouse locations and return the fastest pairing given current traffic speed

Nearby place discovery

Power a search box that suggests places as the user types and returns nearby points of interest around a coordinate. The suggest and place-search operations back autocomplete and 'what's around me' features for store locators, tourism apps, and in-app search.

Return the five nearest coffee shops to a given latitude and longitude with their names and distances

Key Endpoints

17 endpoints — the longdo map api turns place names and addresses into coordinates, extracts structured addresses from free-form thai text, and plans routes across thailand and the wider world.

METHOD

PATH

DESCRIPTION

GET

/mapsearch/json/search

Search for a place by keyword

GET

/addresslookup/api/addr/geocoding

Geocode an address to coordinates

GET

/map/services/addresses

Batch reverse geocode coordinates

GET

/smartsearch/json/extract_address/v2

Extract a structured address from text

GET

/RouteService/json/route/guide

Calculate a route with turn-by-turn guide

GET

/RouteService/json/route/matrix

Calculate a route matrix between points

GET

/RouteService/json/traffic/speed

Get live traffic speed

POST

/route-tsp-v2

Solve a travelling-salesman route ordering

GET

/mapsearch/json/search

Search for a place by keyword

GET

/addresslookup/api/addr/geocoding

Geocode an address to coordinates

GET

/map/services/addresses

Batch reverse geocode coordinates

GET

/smartsearch/json/extract_address/v2

Extract a structured address from text

GET

/RouteService/json/route/guide

Calculate a route with turn-by-turn guide

GET

/RouteService/json/route/matrix

Calculate a route matrix between points

GET

/RouteService/json/traffic/speed

Get live traffic speed

POST

/route-tsp-v2

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Longdo Map API by hand means threading your key into the 'key' query parameter on every call and splitting requests across its search and API hosts. Through Jentic you install once, import Longdo Map from the API Directory, store the key once, and your agent calls the geocoding, search, and routing operations directly.

Permission scoping

You choose the operations your agent may call, so you can allow geocoding and place search while leaving out anything you have not listed. Longdo carries the query and coordinates in the request itself rather than a resource id in the URL path, so rules bound which operations run, not which place is queried.

Credential isolation

Your Longdo Map API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'geocode a Thai address' or 'plan a route', and Jentic returns the matching Longdo Map operation with its input schema so the agent calls the right endpoint without reading the reference docs.

FAQs

Specific to using Longdo Map API through Jentic.

What authentication does the Longdo Map API use?

The Longdo Map API authenticates with an API key passed as the 'key' query parameter on each request, per its OpenAPI spec. You obtain a key from the Longdo Map developer portal. Through Jentic the key is stored once and injected at call time, so your agent never has to place it in the query string itself.

Can I geocode and reverse geocode Thai addresses with the Longdo Map API?

Yes. The geocoding endpoint converts an address or place name into coordinates, the reverse-geocode services turn a single coordinate or a batch of coordinates back into structured addresses, and the smart extractor pulls address components out of free-form text. This makes it a good fit for cleaning and normalising Thai address data.

Is there a Longdo Map MCP server?

You do not need an MCP server to give your agent the Longdo Map API. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent calls the geocoding, search, and routing operations on demand. Nothing extra runs, and no server tool definitions sit in the agent's context between calls.

Can I limit what my agent is allowed to do with the Longdo Map API?

Yes. Write a rule that allows only the read operations you need, such as geocoding and place search, so the agent can look up locations and plan routes but cannot call anything you have not listed. Every call it makes is logged, so you can see exactly which operations ran.

What are the rate limits for the Longdo Map API?

The OpenAPI spec does not specify rate limits. Limits are tied to your Longdo Map API key tier, so check the developer documentation at https://map.longdo.com/docs/ for the current quota that applies to your key.

How do I plan a route with the Longdo Map API through Jentic?

Search Jentic for 'plan a route in Thailand' to find the route-guide operation, which returns turn-by-turn directions between coordinates, and pair it with the geocoding operation to convert addresses to coordinates first. Jentic returns each operation with its input schema so your agent calls it correctly. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Map Longdo Longdo Map API

Name: Longdo Map API
Brand: Longdo Map API
Availability: InStock

Official vendor OpenAPI document · agent-readyMaps GeolocationGeocodingapiKey17 EndpointsREST

For Agents

Geocode and reverse geocode Thai and global addresses, search places and points of interest, and plan routes with traffic and reachable-area analysis. Returns coordinates, structured addresses, and turn-by-turn route paths.

Use for: I need to geocode a Thai street address into coordinates, Reverse geocode a batch of GPS points into readable addresses, Search for restaurants and points of interest near a location, Find the driving route between two places with turn-by-turn guidance

Not supported: Does not render interactive map tiles or basemaps, host business listings, or manage user reviews. Use for location search, geocoding, and routing only.

The Longdo Map API turns place names and addresses into coordinates, extracts structured addresses from free-form Thai text, and plans routes across Thailand and the wider world. It reverse geocodes single points or batches of coordinates, searches nearby points of interest, and returns turn-by-turn route guides, route matrices, snapped road paths, and reachable-area (isochrone) spans. Live traffic speed and area lookups round out the location toolkit for building map and logistics features.

Jentic One on Github View OpenAPI Document