Product

How Jentic Works

From API assessment to production deployment in four simple steps.

Product Overview

PLATFORM

API DirectoryBrowse 10,000+ APIs ready for AI agent integration API ScorecardAssess your APIs for AI-readiness with automated scoring Agentic SandboxSafely simulate AI agents with your production APIs Jentic MiniFree, self-hosted API execution layer for AI agents

CAPABILITIES

IntegrationConnect AI agents to your existing systems WorkflowsDiscover and capture successful agent workflows GovernanceDefine, observe, and enforce AI policies

TOOLS

Arazzo UIVisualize Arazzo workflows as interactive documentation Arazzo EditorBuild and edit multi-step API workflows visually

Developers

GET STARTED

DocumentationGuides and API reference QuickstartGet up and running in minutes

COMMUNITY

GitHubOpen source projects and examples

Resources

BlogLatest articles and insights Press & MediaBrand assets and press contact Open StandardsBuilt on open specs. Never locked in.NewsletterAPIs, AI agents, mixed with architecture and strategy.

Company

About UsOur mission and team CareersJoin our team ContactGet in touch

Sign in Book a Demo

How Jentic Works API Directory API Scorecard Agentic Sandbox Jentic Mini Integration Workflows Governance Arazzo UI Arazzo Editor

Documentation Quickstart GitHub

Blog Press & Media Open Standards Newsletter

About Us Careers Contact

Request a demo Sign Up

Sign up for exclusive Jentic updates

Website

For Developers

Docs
GitHub

Company

About
Blog
Careers
Contact us

© 2026 Jentic. All rights reserved.

Terms & Conditions•Privacy Policy•

Maps & Geolocation APIs | Jentic

APIs/Maps & Geolocation

Maps & Geolocation APIs

Explore APIs in this category. Connect any of them to your AI agent through Jentic.

Browse Maps & Geolocation APIs

Filters

AI/ML

Analytics

Cloud Infrastructure

Communications

CRM

Data Enrichment

Developer Tools

E-Commerce

Education

Finance

Healthcare

HR & Recruiting

Identity & Auth

IoT

Maps & Geolocation

Marketing

Media

Payments

Productivity

Security

Social Media

Storage

A-Z

Most Popular

Abstract IP Geolocation API

Jentic publishes the only available OpenAPI specification for Abstract IP Geolocation API, keeping it validated and agent-ready. Abstract's IP Geolocation API resolves IPv4 and IPv6 addresses to a precise location, timezone, currency, and ISP across 4 billion+ addresses and 250,000+ cities, with weekly data refreshes. The service exposes a single GET endpoint and is keyed by an api_key query parameter, returning JSON with optional security and connection-type fields. It is built for inline lookups in onboarding, fraud, personalization, and analytics flows.

Maps Geolocation

Abstract IP Geolocation API

Jentic publishes the only available OpenAPI specification for Abstract IP Geolocation API, keeping it validated and agent-ready. Abstract IP Geolocation provides lookup of geolocation data for any IPv4 or IPv6 address, including city, region, country, timezone, currency, language, and security signals. The whole API is a single GET /v1/ endpoint keyed by an api_key query parameter, returning JSON. It is a drop-in replacement for self-hosted GeoIP databases when you only need a few hundred lookups per second.

Maps Geolocation

ADS-B Exchange API

Jentic publishes the only available OpenAPI specification for ADS-B Exchange API, keeping it validated and agent-ready. ADS-B Exchange exposes real-time and historical aircraft tracking data sourced from a global network of community-run ADS-B receivers, with no filtering of military, government, or blocked aircraft. The API returns aircraft positions by latitude/longitude radius, ICAO hex code, callsign, registration, or aircraft type, and includes specialised feeds for military aircraft, LADD-listed aircraft, and PIA registrations. Distribution is via RapidAPI, with all 13 endpoints accepting an X-RapidAPI-Key header.

Maps Geolocation

Aero Paquetes Adaptador AlMundo

Aero-Packs es la aplicacion donde Aero S.R.L ofrece todos sus servicios en un único servicio integral. Este documento debe utilizarse como referencia para utilizar la API de AeroPacks integrada con AlMundo para la venta de paquetes desde un consumo externo con modalidad consulta y venta "on the fly". <b>Tener en cuenta:</b> La disponibilidad de una salida depende de que la misma haya podido mapear. The API exposes 11 endpoints.

Maps Geolocation

Airport & City Search

The Amadeus Airport & City Search API turns partial place strings into structured airport and city records for autocomplete and search experiences. The /reference-data/locations endpoint accepts a keyword such as 'lon' and returns matching airports and cities with IATA codes, geo coordinates, time zones, and the parent metropolitan area, while /reference-data/locations/{locationId} returns a single record by ID. It is the standard building block behind 'where do you want to go?' inputs in flight and travel UIs.

Maps Geolocation

Airport Nearest Relevant

The Amadeus Airport Nearest Relevant API returns the commercial airports closest to a given latitude and longitude, ranked by relevance. The single GET endpoint at /reference-data/locations/airports takes coordinates plus an optional radius and returns each airport with its IATA code, distance, time zone, and an analytics score that reflects passenger traffic. It is used to default a flight search to the nearest airport and to suggest secondary airports for fare comparisons.

Maps Geolocation

Antsroute API

Jentic publishes the only available OpenAPI specification for Antsroute API, keeping it validated and agent-ready. Antsroute is a last-mile route-optimisation platform whose API exposes 74 endpoints for managing services, deliveries and collects, agents and their hourly plans, customers and absences, item types, skills, packages, and route planning under the /capi namespace. Agents can create orders, place them on a planning, search availability slots, and reconcile order status by external ID, supporting both schedule-and-dispatch and bring-your-own-route workflows. Authentication uses an API key sent in the cakey header.

Maps Geolocation

API Demo

Basic API description for statistics and events. In case of a live session, fire requests every X seconds (depending on your needs) to get updated live data. <br><br> player_id: Kinexon internal, unique identifier<br> league_id: Secondary identifier. Can be set to 3rd party player identifier.<br><br> Units: <br> Speeds: meters/second <br> Accelerations: meters/second^2 <br> Distances/Coordinates: . The API exposes 2 endpoints secured with basic authentication.

Maps Geolocation

API Locations

Ferguson's Location API for exchanging location data with internal Ecommerce platforms and 3rd party companies.    > Fetch summary list of locations via pagination: <details> <summary>Click to see example response</summary> </details> --- --- > Fetches details for a specific location based on id and application scope: For external users, this endpoint features a refined response. <detail. The API exposes 3 endpoints secured with oauth2 authentication.

Maps Geolocation

API of the Adshot Scraping Engine

This is the API definition for the Adshot Scraping Engine service. This API should only be made available internally for use by Adshot Core. There is no dependency in the other direction. Meaning that the Scraping Engine API should not fetch data from Adshot Core or store foreign keys to entities stored in Adshot Core, thereby avoiding coupling between these services as much as possible. Mappings . The API exposes 14 endpoints.

Maps Geolocation

Apiip - IP Geolocation API

Apiip is an IP geolocation service that resolves a single IP, the requester's IP, or a comma-separated batch of up to many IPs to detailed location records. Each lookup returns city, region, country, latitude and longitude, ISO codes, timezone, currency, and connection metadata in a JSON response. The API exposes three GET endpoints rooted at /api/check and authenticates via an accessKey query parameter. It is well suited for fraud signals, content localization, and routing visitors to the nearest data centre.

Maps Geolocation

Apiip - IP Geolocation API

Jentic publishes the only available OpenAPI specification for Apiip - IP Geolocation API, keeping it validated and agent-ready. Apiip resolves an IP address to a structured location record with city, region, country, latitude and longitude, timezone, currency, and connection metadata. Three GET endpoints rooted at /api/check cover requester-IP self-lookup, single-IP lookup, and comma-separated bulk lookup. Authentication is via an accessKey query parameter, and the fields parameter trims responses to just the attributes you need.

Maps Geolocation

Arizona 511 API

Jentic publishes the only available OpenAPI specification for Arizona 511 API, keeping it validated and agent-ready. The Arizona 511 API exposes traffic and transportation data published by the Arizona Department of Transportation, including cameras, weather stations, message signs, traffic events, alerts, rest areas, and Work Zone Data Exchange (WZDx) work-zone data. The API is rate limited to 10 calls per 60 seconds and authenticates via an API key in the `key` query parameter.

Maps Geolocation

AZ511 Traffic Data API

Jentic publishes the only available OpenAPI specification for AZ511 Traffic Data API, keeping it validated and agent-ready. The AZ511 API gives developers programmatic access to Arizona Department of Transportation (ADOT) traffic feeds, including live traffic cameras, weather stations, dynamic message signs, traffic events, alerts, and rest areas across the Arizona highway network. All six endpoints are GET-only and require an API key passed as a `key` query parameter.

Maps Geolocation

Azure Location Based Services Resource Provider

Jentic publishes the only available OpenAPI specification for Azure Location Based Services Resource Provider, keeping it validated and agent-ready. The Azure Location Based Services Resource Provider API manages account-level resources for the Microsoft.LocationBasedServices namespace, letting operators provision Maps accounts inside an Azure subscription, list and rotate the primary and secondary subscription keys, and move accounts between resource groups. It is a control-plane API rather than a maps query API, so all calls go through Azure Resource Manager at management.azure.com and use Azure AD OAuth 2.0. Use it to automate the lifecycle of a Maps account before pointing applications at the Azure Maps data plane for geocoding or routing.

Maps Geolocation

Azure Maps Resource Provider

Jentic publishes the only available OpenAPI specification for Azure Maps Resource Provider, keeping it validated and agent-ready. The Azure Maps Resource Provider manages account-level resources under the Microsoft.Maps namespace, the successor to the older Microsoft.LocationBasedServices namespace. Operators can provision Azure Maps accounts, list accounts at subscription or resource-group scope, retrieve and rotate primary and secondary subscription keys, update SKU and tags, and move accounts between resource groups. All requests authenticate with Azure AD OAuth 2.0 against Azure Resource Manager.

Maps Geolocation

BART Legacy API

The BART Legacy API gives access to Bay Area Rapid Transit data, including real-time departure estimates, station information, schedule planning, and service advisories for the San Francisco Bay Area rail network. The same endpoints accept either XML or JSON via a format query parameter. BART recommends GTFS and GTFS-RT feeds for new integrations, but the legacy REST endpoints remain operational and are well-suited to lightweight commuter dashboards, chatbots, and station signage. An API key is required and is passed in the key query parameter.

Maps Geolocation

BART Legacy API

Jentic publishes the only available OpenAPI specification for the BART Legacy API, keeping it validated and agent-ready. The Bay Area Rapid Transit (BART) Legacy API exposes real-time train departure estimates, station information, route data, schedule data, and service advisories for the San Francisco Bay Area's rapid transit network. A public testing key (MW9S-E7SL-26DU-VV8V) is documented for development. Useful for transit-aware mobile apps, commute assistants, and data-driven research into Bay Area transit operations.

Maps Geolocation

BC Geographical Names Web Service - REST API

The BC Geographical Names Web Service exposes searchable, authoritative records for the official place names of British Columbia, including features such as lakes, rivers, mountains, communities, and parks. It serves the Province's gazetteer with endpoints for keyword search, official-only and not-official-only search, spatial 'inside' and 'near' search, recent name decisions, name change history, and detail lookup by name or feature ID. The service responds in multiple output formats and supports a feature taxonomy enumeration for filtering by feature class.

Maps Geolocation

BC Route Planner REST API

The BC Route Planner is the British Columbia government's routing engine for the province's public road network, computing shortest and fastest routes between a start point and one or more stops. It exposes pairwise distance, optimal route ordering, turn-by-turn directions, and a dedicated truck routing track that respects commercial vehicle restrictions. Output formats include JSON, GeoJSON, and KML, with 22 endpoints split across passenger and truck modes. Access is currently restricted to B.C. Government Ministries.

Maps Geolocation

Bets API

The Bets API methods are used to place single, multiple and complex bets and to retrieve a customer’s bet history. When retrieving a customer’s bet history you can organize the bets from the betting history in terms of date, bet type and whether the bet is settled or not. You can also specify what fields to be included/excluded or return a list of all default fields the method returns. <br /><br /. The API exposes 6 endpoints.

Maps Geolocation

Bets API

The Bets API methods are used to place single, multiple and complex bets and to retrieve a customer’s bet history. When retrieving a customer’s bet history you can organize the bets from the betting history in terms of date, bet type and whether the bet is settled or not. You can also specify what fields to be included/excluded or return a list of all default fields the method returns. <br /><br /. The API exposes 6 endpoints.

Maps Geolocation

bng2latlong

The bng2latlong API converts an OSGB36 easting and northing coordinate pair from the British National Grid into a WGS84 latitude and longitude. The single GET endpoint accepts the easting and northing as path parameters and returns the converted coordinates plus the original input echoed back. It is unauthenticated and aimed at UK GIS, surveying, and property workflows that need to bridge British National Grid data into modern web map layers.

Maps Geolocation

BOSS Location Management API

Manage locations and disposal for the Back of Store System, including available disposal, recycling, and donation options. Unless otherwise noted, the following limits apply to fields in URL path and query params: - Date/time strings must be provided in ISO 8601 format. All values converted to UTC, no time zone info will be retained. - All string fields, path and query parameters are limited to 12. The API exposes 26 endpoints secured with apiKey authentication.

Maps Geolocation

ChargeHub API

ChargeHub maintains one of the largest public databases of EV charging stations in North America, covering Level 2 and DC fast chargers across all major networks. The API exposes three read endpoints: a service status check, a points-of-interest lookup that returns charging stations and their connector details, and a user-content endpoint for community-supplied photos and check-ins. It is intended for trip planners, EV navigation apps, and fleet routing tools that need accurate, network-agnostic charger data without scraping individual operator sites.

Maps Geolocation

City of Surrey Traffic Loop Count API.

This API provides locations of City of Surrey traffic loops and the corresponding traffic loop counts in 15 minute intervals. While the counts are broken up by 15 minute intervals, the data is currently loaded only once per day. We are hoping to increase this frequency to at least once every hour. The LOOP_ID field is common to both datasets and can be used to cross-reference them. The API exposes 2 endpoints.

Maps Geolocation

Clash of Clans API

Official Clash of Clans API for accessing game data including clans, players, leagues, locations, and war information. The API exposes 22 endpoints secured with bearer authentication.

Maps Geolocation

Cloud-RF API

Jentic publishes the only available OpenAPI specification for Cloud-RF API, keeping it validated and agent-ready. The Cloud-RF API computes radio frequency coverage, link budgets, and interference for any radio, antenna, and terrain on Earth. It exposes endpoints to model point-to-point paths, point-to-multipoint heatmaps, multi-site coverage meshes, and best-server selection across networks, plus archive management to list, export, and delete past calculations. Authentication is via a key header, and outputs include heatmap tiles, GIS exports, and structured link budget data.

Maps Geolocation

Common Platform API Case URN Mapper

Case URL Mapper specification. The API exposes 1 endpoints.

Maps Geolocation

DB Fahrplan API

The DB Fahrplan API is Deutsche Bahn's open timetable interface for the German rail network and connecting European services. The four endpoints cover the canonical journey-planning flow: resolve a station name to a stop ID, retrieve a board of upcoming departures or arrivals at that stop, and pull the detail view for a specific journey. Authentication is a single authKey query parameter. Travel apps, expense tools, and AI travel agents use it to surface live train timetables without operating a dedicated rail-data feed.

Maps Geolocation

DB Fahrplan API

Jentic publishes the only available OpenAPI specification for DB Fahrplan API, keeping it validated and agent-ready. Deutsche Bahn's Fahrplan (timetable) API exposes train and station data for Germany and connecting European routes. The four endpoints cover station search by name, departure and arrival boards for a station, and detail lookups for a specific journey leg. It is the canonical agent-readable view of DB schedule data and is suitable for travel-assistance, journey-planning, and station-monitor use cases.

Maps Geolocation

Dealer

The Mercedes-Benz Dealer API provides a structured directory of authorised Mercedes-Benz dealerships and the countries they operate in. It returns dealer locations with addresses, contact details, and identifiers, plus a country reference list to scope queries. The dataset is the same dealer information surfaced on mercedes-benz.com's dealer locator, suitable for embedding a 'find a Mercedes dealer' experience inside a third-party app.

Maps Geolocation

BOOK A DEMO

Start Connecting APIs to Your AI Agents

Browse thousands of APIs, connect in minutes via MCP, OpenClaw, or Python. One SDK, one credential — every API your agent needs.