canonical: https://jentic.com/apis/geolink-eg.com/geolink-eg # Geolink Eg GeoLink Directions API The GeoLink Directions API calculates a route between two points given their latitude and longitude. A single directions operation takes the origin and destination coordinates and returns the route between them, with an option to return up to three alternative routes. Results can be returned in one of 40+ languages using an ISO 639-1 code and localized with an ISO 3166-1 country code. It is built for delivery, logistics, and travel-planning applications that need point-to-point routing from a simple request. ## For AI agents Calculate a route between two latitude and longitude points, optionally returning up to three alternatives, in 40+ languages. A single GET operation secured with an API key passed as a query parameter. ## Scope Does not handle geocoding, map rendering, or place search. Use for calculating routes and directions between coordinates only. ## Capabilities - Calculate a route between two latitude and longitude points - Return up to 3 alternative routes for a trip - Return directions in one of 40+ languages with an ISO 639-1 language code - Localize routing results by country with an ISO 3166-1 country code ## Use cases ### AI Agent Routing via Jentic An AI agent reaches GeoLink through Jentic to route between two points without wiring the API key itself. It searches by intent, receives the directions operation and its input schema, and executes the call with the key injected at run time. This lets the agent turn a pair of coordinates into a route inside a larger logistics or travel task. Example prompt: Search Jentic for 'directions between two points', load the GET /directions schema, and execute it with the key injected at run time ### Point-to-Point Routing A delivery or logistics app needs the route between an origin and a destination it already holds as coordinates. GeoLink takes the origin and destination latitude and longitude and returns the route between them from a single request. Sub-200ms response times make it suitable for interactive route lookups. Example prompt: Call GET /directions with origin_latitude, origin_longitude, destination_latitude, and destination_longitude to calculate the route ### Multilingual Directions A travel or store-locator app shows directions in the user's own language. GeoLink accepts an ISO 639-1 language code and returns the route in one of 40+ supported languages, and a country code localizes the result. The agent sets the language per user so the directions read naturally wherever they are shown. Example prompt: Call GET /directions with a language code to return directions in one of the 40+ supported languages ### Route Alternatives A trip planner offers travellers a choice between routes. GeoLink returns up to three alternative routes for the same origin and destination when the alternatives option is set, so the agent can present options that trade distance against other factors. The caller picks the route that best fits the trip. Example prompt: Call GET /directions with alternatives enabled to return up to 3 route options between two points ## Key resources - **Directions** — Calculate a route between two coordinates, with optional alternatives, language, and country, via /directions ## AI readiness This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use. - **Score:** 49 / 100 - **Maturity:** Foundational - **Dimensions:** - Foundational Compliance: 100 / 100 - Developer Experience & Jentic Compatibility: 82 / 100 - AI-Readiness & Agent Experience: 45 / 100 - Agent Usability: 94 / 100 - Security: 15 / 100 - AI Discoverability: 100 / 100 - **View full report:** https://jentic.com/apis/geolink-eg.com/geolink-eg/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **Setup:** Wiring GeoLink by hand means subscribing to a plan, passing the key as a query parameter, and supplying origin and destination coordinates on every directions call. Through Jentic you install once, import GeoLink from the API Directory, store the key once, and your agent calls it. - **Permission scoping:** The API has a single directions operation, so a rule can allow your agent exactly that read and nothing else. Because there are no write or account operations, the agent can only calculate routes and can never change anything through this API. - **Credential handling:** Your GeoLink 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, which matters because the key would otherwise travel in the URL query string. - **Discovery method:** Agents search Jentic by intent such as 'route between two points' or 'directions in another language', and Jentic returns the GeoLink directions operation with its input schema so the agent calls it with the right coordinates without browsing the reference docs. ## Related APIs - **GraphHopper Directions** — Routing, route optimization, matrix, and isochrone endpoints - **Mapbox** — Directions, maps, geocoding, and navigation services - **Geoapify** — Geocoding, places, and routing services ## FAQ ### What authentication does the GeoLink Directions API use? The GeoLink Directions API authenticates with an API key passed as a key query parameter, per its OpenAPI spec, and you include it on the directions request. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at execution time, so it never reaches the agent or appears in your code. ### What are the rate limits for the GeoLink Directions API? The OpenAPI spec does not specify request rate limits; they depend on the subscription plan you choose. See https://docs.geolink-api.com for current limits and plan details. ### Can I get alternative routes with the GeoLink Directions API? Yes. GET /directions takes origin and destination coordinates and, with the alternatives option set, returns up to 3 route options. You can also set an ISO 639-1 language code for directions in one of 40+ languages and an ISO 3166-1 country code to localize the result. ### Is there a GeoLink Directions MCP server? You don't need an MCP server to give your agent GeoLink. Jentic connects it directly from the API Directory: import it and your agent calls the directions operation on demand, discovering its input schema when it needs it rather than loading a separate server's tool definitions into context. ### How do I route between two points with the GeoLink Directions API through Jentic? Search Jentic for 'directions between two points', and it returns the GeoLink directions operation with its input schema. Load it and execute GET /directions with the origin and destination coordinates, with the key injected at run time. To run it on your own infrastructure, install Jentic One from its GitHub repo. ### Can I limit what my agent is allowed to do with the GeoLink Directions API? Yes. The API exposes only the directions operation, so a rule that allows that single read lets the agent plan routes and do nothing else. Because every call runs through your own instance, each one is logged for you to review.