canonical: https://jentic.com/apis/locationiq.com/locationiq

# LocationIQ API

The LocationIQ API turns addresses and coordinates into structured location data. It performs forward and reverse geocoding, structured and postal-code lookups, place autocomplete, nearby point-of-interest search, timezone lookup, and driving directions, built on OpenStreetMap data. Responses are JSON, so an agent can resolve an address to coordinates, label a point on a map, or compute a route without hosting its own geocoder.

## For AI agents

Geocode addresses, reverse geocode coordinates, autocomplete places, find nearby points of interest, and get directions.

## Scope

Resolves addresses, coordinates, and routes through LocationIQ's geocoding endpoints; it does not host maps, store your data, or manage the underlying OpenStreetMap datasets.

## Capabilities

- Forward geocode a free-form or structured address
- Reverse geocode coordinates into an address
- Search by postal code
- Autocomplete place queries
- Find nearby points of interest
- Look up timezone and compute driving directions

## Use cases

### Geocode an address

Turning a street address into coordinates is the first step for mapping or distance work. The LocationIQ API forward-geocodes a free-form or structured address and returns matching coordinates with place details. An application can then plot the location or feed it into routing.

Example prompt: Forward geocode the supplied address and return its coordinates.

### Reverse geocode coordinates

A latitude and longitude often needs a human-readable label. The LocationIQ API reverse-geocodes coordinates into a formatted address and place components, letting an application describe where a point is. This is useful for tagging user locations or delivery points.

Example prompt: Reverse geocode the given coordinates and return the formatted address.

### Autocomplete and route

Address entry and trip planning both benefit from live suggestions and routing. The LocationIQ API autocompletes partial place queries and computes driving directions between coordinates, so an application can help a user pick a place and then find the way there. Directions return the route geometry and distance.

Example prompt: Autocomplete a place query, then compute directions to the chosen coordinates.

### Agent-driven location lookups

An AI agent can resolve locations for a user without a developer wiring each call. Through Jentic the agent matches an intent such as 'find the coordinates for this address' to the LocationIQ geocoding operation, runs it, and returns the result. The API key stays in the user's Jentic One instance and never reaches the agent's prompt.

Example prompt: Geocode the requested address and return the coordinates and place details.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/search` | Forward geocode a free-form address query. |
| GET | `/reverse` | Reverse geocode coordinates into an address. |
| GET | `/autocomplete` | Return autocomplete suggestions for a partial query. |
| GET | `/nearby` | Find points of interest near a location. |
| GET | `/timezone` | Look up the timezone for a location. |
| GET | `/directions/{profile}/{coordinates}` | Compute driving directions between coordinates. |

## Key resources

- **Search** — Forward, structured, and postal-code geocoding.
- **Reverse** — Reverse geocoding of coordinates to addresses.
- **Autocomplete** — Live suggestions for partial place queries.
- **Directions** — Driving directions and route geometry between points.

## Why Jentic

- **Setup:** Wiring LocationIQ yourself means managing an API key, choosing a regional host, and handling each geocoding and routing call. With Jentic you install once, import LocationIQ from the API Directory, and store the key a single time.
- **Permission scoping:** Jentic lets you grant your agent only the operations it needs, such as geocoding and directions without account balance access, and enforces that on every call.
- **Credential handling:** Your LocationIQ API key is stored once, encrypted, by your own Jentic One instance. It is injected when a call runs and never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents find LocationIQ through Jentic's intent search, matching a request like 'geocode this address' to the right operation without hardcoded endpoints.

## Related APIs

- **OpenCage** — Forward and reverse geocoding on open data.
- **Geocodio** — US and Canada geocoding with data appends.
- **Foursquare Places** — Rich place and point-of-interest data.

## FAQ

### What can an AI agent do with the LocationIQ API through Jentic?

An agent can geocode addresses, reverse geocode coordinates, autocomplete places, search nearby points of interest, and compute directions. Through Jentic the agent matches an intent to the right operation and runs it with your API key injected at execution time.

### How do I authenticate with the LocationIQ API?

LocationIQ authenticates requests with an API key passed as the key query parameter. You store the key once in your Jentic One instance, and it is added to each call at run time rather than exposed to the agent.

### Does LocationIQ have regional endpoints?

Yes. LocationIQ serves requests from a US region at us1.locationiq.com and an EU region at eu1.locationiq.com, and you can call whichever host suits your data residency needs. Both regions expose the same geocoding and routing operations.

### Does the LocationIQ API document rate limits?

The OpenAPI specification does not state rate limits; request allowances depend on your LocationIQ plan. Check the current limits for your account in the LocationIQ dashboard and documentation.

### Can I control which LocationIQ operations my agent can call?

Yes. Jentic lets you allow only the operations your agent needs, for example geocoding and directions while withholding others. Your Jentic One instance enforces that boundary on every call and keeps the API key outside the agent's context.