GET STARTED
TOOLS
COMMUNITY
Explore APIs in this category. Connect any of them to your AI agent through Jentic.
Filters
Jentic publishes the only available OpenAPI specification for Habitatrichtlijn verspreiding van habitattypen WFS, keeping it validated and agent-ready. This WFS (Web Feature Service) provides geographic distribution data for habitat types within Natura 2000 areas in the Netherlands, covering the 2007-2012 reporting period. The API exposes 208 endpoints representing individual habitat type distributions and their geographic extent, enabling spatial queries on dry heathlands, wet forests, dune vegetation, salt marshes, pioneer communities, and dozens of other habitat classifications defined under the EU Habitats Directive.
Jentic publishes the only available OpenAPI specification for Transport for London Unified API, keeping it validated and agent-ready. The TfL Unified API is the canonical source for live London transport data: tube and bus arrivals, line statuses and disruptions, journey-planner results, BikePoint availability, air-quality readings, accident statistics, road status, taxi and minicab contacts, and station details. Travel apps, journey planners, and London-focused agents use it to answer 'when is the next Victoria-line train?' and 'how do I get from King's Cross to Heathrow right now?'. Authentication uses paired app_id and app_key query parameters issued from the TfL portal.
tfl.gov.uk/main version v1. The API exposes 84 endpoints secured with apiKey authentication.
Snipe-IT REST API for IT asset management including hardware, users, licenses, locations, and more. The API exposes 79 endpoints secured with bearer authentication.
Antsroute publishes the OpenAPI specification behind this page from its own application host, and Jentic bundles it, validates it, and keeps it 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.
GeoDB Cities API is a curated geographic database covering countries, regions, administrative divisions, populated places, and time zones, distributed via the RapidAPI marketplace under the wft-geo-db host. Each city record carries population, latitude/longitude, elevation, and Wikidata IDs, with nearby-city and distance-radius search built in. The API is intended for autocomplete UIs, store-locator features, and AI agents that need to look up places without licensing a full GIS dataset. Authentication uses a RapidAPI key passed as the `X-RapidAPI-Key` header.
Our API uses a REST based design, leverages the JSON data format, and relies upon HTTPS for transport. We respond with meaningful HTTP response codes and if an error occurs, we include error details in the response body. API Documentation is at https://api.youneedabudget.com. The API exposes 31 endpoints secured with apiKey authentication.
The National Park Service API provides programmatic access to authoritative data about US national parks, including park profiles, alerts, campgrounds, events, visitor centers, multimedia, and trip-planning content sourced from NPS.gov. Twenty-nine endpoints cover parks, activities, amenities, articles, lesson plans, news releases, road events, things to do, tours, webcams, and more. The API is free with an API key obtained from the NPS Developer portal and is the canonical source for park data inside trip-planning, education, and travel apps.
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.
The PTV Timetable API provides direct access to Public Transport Victoria’s public transport timetable data. The API returns scheduled timetable, route and stop data for all metropolitan and regional train, tram and bus services in Victoria, including Night Network(Night Train and Night Tram data are included in metropolitan train and tram services data, respectively, whereas Night Bus is a separa. The API exposes 26 endpoints.
DFlight supplies UAV and drone operators with the airspace, weather, restriction, and surface-obstacle data required for preflight compliance assessment. Operators define an area of interest as a point with radius, a GeoJSON LineString route, or an arbitrary GeoJSON Polygon, and DFlight returns airspace classifications, special security areas, restricted public venues, surface obstacles, aerodromes, UAS operating areas, and weather forecasts that intersect that geometry. The API is organised by data category, with three query shapes per category (distance, route, polygon) for predictable integration into flight-planning tools.
Jentic publishes the only available OpenAPI specification for MBTA V3 API, keeping it validated and agent-ready. The MBTA V3 API exposes real-time and scheduled transit data for the Massachusetts Bay Transportation Authority covering subway, commuter rail, bus, and ferry services across Greater Boston. It follows the JSON:API specification and includes 24 endpoints for stops, routes, schedules, predictions, vehicles, alerts, facilities, and trip planning data. Agents use it for arrival predictions, service alerts, and accessibility-aware journey planning.
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.
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.
Lock and unlock vehicles and get data like odometer reading and location. Works on most new cars. Smartcar provides a unified API to read vehicle data and send commands to vehicles across brands. The API exposes 21 endpoints secured with basic, oauth2 authentication.
Route planning and delivery management API for Shopify merchants. The API exposes 19 endpoints secured with bearer authentication.
Rose Rocket is an all-in-one Transportation Management System (TMS) API that provides access to boards, events, user groups, and object records for trucking and logistics management. The API exposes 19 endpoints secured with bearer authentication.
Jentic publishes the only available OpenAPI specification for GeoNames API, keeping it validated and agent-ready. GeoNames is a worldwide geographical database web service offering postal-code search, place-name lookup, country and subdivision data, neighbourhood resolution, ocean and timezone lookups, and digital-elevation queries (SRTM1, SRTM3, ASTER GDEM). The 18 JSON endpoints are widely used as a free or low-cost alternative to commercial geocoders for global place-name and postcode resolution. Authentication is by username, attached as a query parameter on every request.
ParkWhiz Partner API v4 provides comprehensive parking search, booking, and account management for reservable parking facilities. The API enables parking availability search by location, event, or venue with date/time filters, location and quote retrieval with pricing, booking creation and management with previews and cancellations, parking pass retrieval, account registration and profile management, vehicle management, review submission and retrieval, and support ticket operations. OAuth 2.0 authentication supports multiple grant flows including client credentials, password, authorization code, and refresh token.
Jentic publishes the only available OpenAPI specification for Longdo Map API, keeping it validated and agent-ready. Longdo Map is a Thailand-focused mapping service that also covers global addresses, with a REST surface for search, suggest, geocoding, reverse geocoding, address extraction, routing, traffic, TSP route planning, and POI lookups. Endpoints sit under /mapsearch, /smartsearch, /addresslookup, /map/services, /POIService, and /RouteService, and every call carries an API key as the 'key' query parameter. The service is the most reliable provider of Thai-language address parsing and place data, returning coordinates and POIs that other global providers often miss inside Thailand.
The BC Address Geocoder REST API cleans, corrects, completes, geocodes, and reverse geocodes British Columbia physical addresses, intersections, and the occupants associated with them. It exposes single-address geocoding, bulk autocomplete, and proximity searches such as nearest site, occupants near a point, and intersections near a point. Several endpoints accept a path-level outputFormat extension (such as .json or .geojson). Authentication is by API key passed in the apikey header.
Geocode individual and batch addresses to coordinates, reverse geocode coordinate pairs to addresses, and append data fields like congressional districts, census tracts, school districts, timezones, and ACS demographics to results. The API supports single and batch requests (up to 10,000 addresses per batch), spreadsheet-based list processing with job management, a distance calculation feature for measuring driving or straight-line distance between geocoded results and destination points, and US/Canada-specific address parsing across 16 endpoints.
Jentic publishes the only available OpenAPI specification for GraphHopper Directions API, keeping it validated and agent-ready. This spec covers the full Directions API surface - Routing, Route Optimization, Isochrone, Map Matching, Matrix, Geocoding, and Cluster - across 16 endpoints, with both synchronous and async job-style calls. Authentication is a single API key passed as a query parameter, and OpenStreetMap is the default data layer with optional TomTom traffic add-ons available for the Route Optimization API.
The Lyft API exposes Lyft's ridesharing primitives - cost estimates, ETAs, available drivers nearby, ride request and lifecycle, ride types, profile, and a sandbox for simulating ride status transitions and primetime. The 16 endpoints cover the journey from quoting a ride through requesting, updating destination, rating, and pulling a receipt. Authentication uses OAuth 2.0 with two flows: client credentials for public endpoints (cost, ETA) and authorization code for user-scoped operations (rides, profile).
The MBTA V3 API provides schedule, real-time vehicle position, and service alert information for the Massachusetts Bay Transportation Authority's bus, subway, commuter rail, and ferry network across the Greater Boston area. Responses follow the JSON:API specification with sparse fieldsets, filtering, and included relationships, so clients can request exactly the data they need. The API exposes resources for routes, stops, trips, vehicles, predictions, schedules, alerts, and shapes. Anonymous access is rate-limited; an x-api-key header lifts the cap for higher-volume agents.
Jentic publishes the only available OpenAPI specification for Ontario 511 Transportation API, keeping it validated and agent-ready. The Ontario 511 Transportation API exposes real-time provincial traffic and travel data published by the Ontario Ministry of Transportation, including incidents, construction zones, traffic camera feeds, road surface conditions, ferry schedules, carpool lots, transit hubs, service centres, truck inspection stations, and winter maintenance vehicles. The API returns JSON for sixteen GET endpoints scoped to Ontario highways and is intended for navigation apps, fleet operators, and travel planning tools that need authoritative road data. Authentication uses a per-developer API key requested through the Ontario 511 developer portal.
The PreflightAPI Aviation Data API provides VFR flight planning data from 7 FAA and NOAA sources including real-time METARs, TAFs, PIREPs, SIGMETs, G-AIRMETs, NOTAMs, airport details, airspace boundaries, navigation aids, obstacles (625,000+ structures), runway information, communication frequencies, route briefings, and E6B flight computer calculations. All 16 endpoints support proximity-based geospatial queries with configurable radius in nautical miles.
Jentic publishes the only available OpenAPI specification for TomTom Search API, keeping it validated and agent-ready. Run fuzzy, category, POI, nearby, and geometry-based searches across TomTom's global location database to find addresses, businesses, and points of interest. The API supports forward and structured geocoding, reverse geocoding with cross-street lookup, search along a driving route with detour-time constraints, and geometry filtering to restrict results to custom polygons or circles - all returning coordinates, address components, and POI metadata across 16 endpoints.
API provided by data from transit.app. The API exposes 16 endpoints secured with apiKey authentication.
MapQuest provides a suite of mapping services covering geocoding, reverse geocoding, batch geocoding, turn-by-turn directions, optimised multi-stop routing, alternate routes, route matrices, static map images, and predictive place search. The API exposes 15 endpoints across the /geocoding, /directions, /staticmap, and /search namespaces and authenticates with a single API key passed in the URL query string. It is positioned for logistics, delivery dispatch, in-product address lookups, and embedded route planning in web and mobile clients.
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.
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.
BOOK A DEMO
Browse thousands of APIs and connect them all to your agent with Jentic One. One layer, one credential — every API your agent needs.