Geoapify API
Agent-ready OpenAPI document · curated by JenticMaps GeolocationGeocodingapiKey5 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Geocode and reverse-geocode addresses, autocomplete address input, find nearby places, and compute routes between points using Geoapify.
Use for: Geocode this address into latitude and longitude, What is the street address for these coordinates?, Suggest address completions for a partial input, Find restaurants near this point
Not supported: Does not handle map tile rendering, traffic overlays, or geofencing. Use for geocoding, place lookup, and point-to-point routing only.
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.
Install Jentic One Beta
Connect the Geoapify API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Geoapify 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.
1
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%2Fgeoapify.com%2Fgeoapify" | sh2
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%2Fgeoapify.com%2Fgeoapify" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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 Geoapify API.
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
Patterns agents use Geoapify API for, with concrete tasks.
★ 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.
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.
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.
Compute a route across the supplied waypoints and return the geometry and travel estimate
Key Endpoints
5 endpoints — 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.
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
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
Why Jentic?
What agents get from Jentic-routed access to this vendor.
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 isolation
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.
Intent-based discovery
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
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Geoapify API through Jentic.
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.
GET STARTED