canonical: https://jentic.com/apis/geoapify.com/geoapify # Geoapify API The Geoapify API turns addresses into coordinates and back, suggests address completions as a user types, finds places near a location, and computes routes between points. Geocoding search resolves a free-form address to coordinates, reverse geocoding does the opposite, autocomplete returns ranked address suggestions, the places endpoint lists points of interest by category, and routing returns a path between waypoints. Every call takes an apiKey query parameter. ## For AI agents Geocode and reverse-geocode addresses, autocomplete address input, find nearby places, and compute routes between points using Geoapify. ## Scope Does not handle map tile rendering, traffic overlays, or geofencing. Use for geocoding, place lookup, and point-to-point routing only. ## Capabilities - Resolve a free-form address into coordinates with geocoding search - Convert coordinates back into a street address with reverse geocoding - Return ranked address suggestions as a user types with autocomplete - List points of interest near a location filtered by category - Compute a route between two or more waypoints ## Use cases ### Agent Address Resolution An AI assistant handling a delivery or booking request can turn a user's typed address into precise coordinates before it acts. The agent calls geocoding search, reads back the resolved coordinates and confidence, and uses them to place an order or plan a trip, so a vague address is normalized without a human copying it into a map. Example prompt: Geocode a user-supplied address and return the top coordinate match with its confidence score ### Nearby Place Discovery A concierge agent can find points of interest around a location on the user's behalf. Given a coordinate, it calls the places endpoint filtered by category, reads back the candidate venues, and presents the closest ones, so a request like 'cafes near the hotel' is answered without the user opening a map app. Example prompt: List places of a requested category near a coordinate and return the closest candidates ### Route Planning A logistics agent can compute the path between stops before it commits to a schedule. It calls the routing endpoint with the waypoints, reads back the geometry and travel estimate, and hands the result to a downstream planner, so a route is calculated on demand rather than pre-baked. Example prompt: Compute a route across the supplied waypoints and return the geometry and travel estimate ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/v1/geocode/search` | Geocode a free-form address | | GET | `/v1/geocode/reverse` | Reverse geocode coordinates | | GET | `/v1/geocode/autocomplete` | Autocomplete an address | | GET | `/v2/places` | Find places near a location | | GET | `/v1/routing` | Compute a route between waypoints | ## Key resources - **Geocoding** — Forward and reverse geocoding endpoints that convert between addresses and coordinates - **Autocomplete** — Ranked address suggestions for partial input - **Places** — Points of interest near a location, filterable by category - **Routing** — A computed path and travel estimate between waypoints ## Why Jentic - **Setup:** Wiring the Geoapify API by hand means appending your apiKey to every request across five differently shaped endpoints and matching each response format. Through Jentic you install once, import it from the API Directory, store the key once, and your agent calls the geocoding, places, and routing operations. - **Permission scoping:** Geoapify's five operations are read-only lookups, so a rule can allow only the geocoding and routing operations your agent needs and leave the rest out of scope. You decide which operations are in scope, and every call the agent makes is logged. - **Credential handling:** Your Geoapify apiKey is stored once, encrypted, by your own Jentic One instance and injected as the query parameter at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'geocode an address' or 'find places near a point', and Jentic returns the matching Geoapify operation with its input schema so the agent calls the right endpoint without reading the reference docs. ## Related APIs - **OpenCage** — Forward and reverse geocoding built on open data. - **LocationIQ** — Geocoding, reverse geocoding, and routing on OpenStreetMap data. - **HERE Maps** — Full mapping platform with geocoding, routing, and traffic data. - **Mapbox** — Maps, geocoding, and navigation APIs with map rendering. ## FAQ ### What authentication does the Geoapify API use? The Geoapify API authenticates with an apiKey passed as a query parameter on every request, per its OpenAPI spec. When you call it through Jentic, that key is held by your own self-hosted instance and added to each request at execution time, so it never appears in the agent's prompt or logs. ### Can I geocode an address and get a route with the Geoapify API? Yes. Call the geocoding search endpoint to turn an address into coordinates, then pass those coordinates as waypoints to the routing endpoint to get a path and travel estimate between them. Reverse geocoding and autocomplete are available for the opposite direction and for typed input. ### What are the rate limits for the Geoapify API? The OpenAPI spec for the Geoapify API does not define rate limits. Check Geoapify's plan documentation for the request allowances that apply to your key before running high-volume geocoding. ### Is there a Geoapify API MCP server? You don't need an MCP server to give your agent the Geoapify API. Jentic connects it directly from the API Directory: import it, store the apiKey once, and your agent calls geocoding, places, and routing operations without another server's tool definitions loaded into its context. ### Can I control which Geoapify operations my agent can call? Yes. Write a rule that allows only the geocoding and routing operations you need, so the agent can resolve addresses and plan routes while the places lookup stays out of scope until you add it, and every call it makes is logged. You decide which operations are in scope. ### How do I geocode an address with the Geoapify API through Jentic? Search Jentic with an intent like 'geocode an address into coordinates', and it returns the geocoding search operation with its input schema so the agent submits the address and reads back the match. To run it on your own infrastructure, install Jentic One from its GitHub repo.