How Jentic Works
From API assessment to production deployment in four simple steps.
PLATFORM
CAPABILITIES
TOOLS
GET STARTED
COMMUNITY
Explore APIs in this category. Connect any of them to your AI agent through Jentic.
Filters
BOOK A DEMO
Browse thousands of APIs, connect in minutes via MCP, OpenClaw, or Python. One SDK, one credential — every API your agent needs.
Jentic publishes the only available OpenAPI specification for 2Captcha API, keeping it validated and agent-ready. 2Captcha is a captcha-solving service that resolves reCAPTCHA v2 and v3, hCaptcha, Cloudflare Turnstile, image-to-text, FunCaptcha, and other challenge types through a small task-based REST API. Agents submit a task with the captcha parameters, poll for the solved token or text, and then use that token to complete the protected form or API request. The service also exposes account balance lookups and a reporting endpoint for grading good and bad solutions, which feeds back into solver accuracy.
Jentic publishes the only available OpenAPI specification for 6sense API, keeping it validated and agent-ready. The 6sense API exposes the data and intelligence services behind 6sense's account-based marketing platform across eight endpoints covering company identification, firmographic enrichment, people enrichment, person scoring, people search, and the search dictionary. Marketing and revenue teams use it to identify anonymous website visitors, enrich CRM records with firmographics and contact data, and feed buying-stage scores into orchestration tools. Authentication is an API token issued from a 6sense account.
Jentic publishes the only available OpenAPI specification for Abstract APIs, keeping it validated and agent-ready. Abstract APIs is a collection of focused REST APIs from Abstract that covers email validation, phone validation, and currency exchange rates, each addressed by its own subdomain (emailvalidation.abstractapi.com, phonevalidation.abstractapi.com, exchange-rates.abstractapi.com). Every endpoint is keyed by a single api_key query parameter, returns JSON, and is intended for lightweight enrichment and verification work inside larger workflows. The bundle is useful when an agent needs quick checks on user-supplied contact data or live FX figures without integrating a heavier specialist provider.
This API provides services to query and validate user accounts. The API exposes 1 endpoints.
Jentic publishes the only available OpenAPI specification for AccuWeather API, keeping it validated and agent-ready. AccuWeather provides current conditions, daily and hourly forecasts, severe weather alerts, and lifestyle indices for any location worldwide. The API resolves locations through a city search or geoposition, returns a location key, and then serves weather data keyed off that location key. Authentication is via an apikey query parameter, and the base URL is dataservice.accuweather.com.
Jentic publishes the only available OpenAPI specification for AccuWeather Core Weather API, keeping it validated and agent-ready. This is the focused core cut of AccuWeather's data services, exposing 8 endpoints across location resolution, current conditions, and 1-day, 5-day, and 12-hour forecasts. Locations can be resolved by city search, autocomplete, or geoposition, and weather data is keyed by the resulting locationKey. The API uses an apikey query parameter for authentication and is hosted at dataservice.accuweather.com.
Jentic publishes the only available OpenAPI specification for Acuris Compliance Search API, keeping it validated and agent-ready. Acuris Compliance Search lets compliance teams screen individuals and businesses against sanctions, politically exposed persons (PEP), and adverse media data. The spec covers nine endpoints split across individuals, businesses, and reference dictionaries, with copyrighted evidence retrieval available per resource. Authentication is via the x-api-key header, scoped to the compliance subscription tier.
Jentic publishes the only available OpenAPI specification for AddressFinder API, keeping it validated and agent-ready. AddressFinder provides address autocomplete, verification, and metadata lookup tuned specifically for Australian and New Zealand postal addresses, plus an email verification endpoint. Each country has dedicated address search, address-info detail, location (suburb/postcode) search, and location-info endpoints, so agents can drive both type-ahead UX and back-end data quality checks. Authentication uses an API key passed as the key query parameter.
Jentic publishes the only available OpenAPI specification for the Adopt-a-Pet.com Pet List API, keeping it validated and agent-ready. The API exposes 6 read-only endpoints for searching adoptable pets, fetching pet and shelter details, listing pets at a specific shelter, searching for shelters, and retrieving the breed list. Use it to power pet-adoption discovery experiences, shelter directories, or AI assistants that surface adoptable animals near a location. Authentication is by API key passed as the 'key' query parameter.
Jentic publishes the only available OpenAPI specification for Adyntel API, keeping it validated and agent-ready. Adyntel is an ad intelligence service that scrapes and surfaces competitor advertising creative across the Facebook/Instagram ad library, Google Ads transparency centre, and LinkedIn ad library through a single REST endpoint per platform. Each call returns structured ad records — creative copy, media URLs, advertiser metadata, and run dates — so teams can monitor competitor campaigns without manually browsing each platform's ad library. The API exposes three POST operations, one per platform, all authenticated with an X-API-Key header.
Jentic publishes the only available OpenAPI specification for AEMET OpenData, keeping it validated and agent-ready. AEMET OpenData is the open data REST API operated by Spain's national meteorological agency (Agencia Estatal de Meteorología). It exposes 62 endpoints covering current observations, short and medium-range forecasts at municipal, provincial, autonomous-community and national level, maritime and mountain forecasts, climatological products, fire-risk maps, lightning networks, radar imagery, and weather warnings. Authentication uses an api_key passed in the api_key header obtained free of charge from the AEMET portal.
Jentic publishes the only available OpenAPI specification for AeroLeads API, keeping it validated and agent-ready. AeroLeads is a B2B prospecting service that finds business email addresses, phone numbers, and contact records from LinkedIn and other public sources. The API exposes a /search endpoint to look up prospects by name and company, a /find endpoint to enrich a known contact with email and phone, and list endpoints to retrieve saved prospects. Authentication uses an api_key header issued from the AeroLeads dashboard.
Jentic publishes the only available OpenAPI specification for Agarathi Dictionary API, keeping it validated and agent-ready. Agarathi is a Tamil dictionary service that exposes a small but focused API: list the available Tamil dictionaries, fetch the word of the day, and search for Tamil word definitions across multiple lexical sources. Useful for language-learning apps, content moderation pipelines that need Tamil semantic context, and AI agents handling Tamil-language inputs.
Jentic publishes the only available OpenAPI specification for Agify API, keeping it validated and agent-ready. Agify predicts the most likely age of a person based on their first name, optionally biased by a country code for localised distributions. The API exposes a single GET endpoint that accepts one or more name parameters and returns the predicted age along with the sample count behind the prediction. Free tier requests are unauthenticated; higher tiers attach an apikey query parameter.
Agrimetrics Catalog API exposes the agri-environmental data catalogue published by Agrimetrics, covering datasets, layers, query execution, and shapefile uploads for spatial analysis. The 93 endpoints include dataset discovery, layer metadata, SPARQL-style query execution, and authenticated download of layer files. The base host is api-test.agrimetrics.co.uk for the test environment, with multiple authentication schemes supported: an Azure APIM subscription key (ocp-apim-subscription-key), a JWT bearer token, header- or query-style API keys, and an x-user header.
Jentic publishes the only available OpenAPI specification for AirLabs Data API, keeping it validated and agent-ready. AirLabs provides real-time and reference aviation data covering live flight tracking, airport and airline databases, schedules, delays, routes, fleets, and timezone reference data. The API exposes 17 endpoints suitable for travel apps, dashboards, and operational tools. Authentication uses an API key passed as the api_key query parameter.
The Amadeus Airline Code Lookup API resolves IATA and ICAO airline codes to full carrier names and metadata. Given a code such as BA or AAL, it returns the carrier's commercial name and identifier mappings, which is essential for displaying human-readable airline names in flight search results, itineraries, and reporting. The single GET endpoint at /reference-data/airlines is read-only and is typically used as an enrichment step alongside Amadeus flight shopping APIs.
Jentic publishes the only available OpenAPI specification for AirNow API, keeping it validated and agent-ready. AirNow is the U.S. EPA's source for real-time and forecast air quality data covering Air Quality Index (AQI) observations across the United States. The API exposes current AQI readings, daily forecasts, and historical observations queryable by zip code, latitude/longitude, or monitoring site. Coverage spans pollutants including ozone, PM2.5, PM10, CO, NO2, and SO2, with data sourced from federal, state, local, and tribal monitoring networks.
Jentic publishes the only available OpenAPI specification for Airport Data API, keeping it validated and agent-ready. Airport Data API is a free reference service that returns IATA and ICAO codes, names, geographic coordinates, and other airport attributes. The five endpoints support listing all airports, lookup by IATA or ICAO code, free-text search, and nearby-airport queries by latitude/longitude. Useful for travel apps, flight planners, and any pipeline that needs to resolve airport identifiers to structured records.
Jentic publishes the only available OpenAPI specification for Airport Gap API, keeping it validated and agent-ready. Airport Gap is a developer-friendly REST API for accessing global airport data, calculating distances between any two airports, and managing a list of favourite airports under an authenticated user. The 10 endpoints cover paginated airport listing, lookup by IATA code, distance calculation, token issuance, and full CRUD on favourites. Designed for testing, prototyping, and educational use.
The Amadeus Airport On-Time Performance API predicts the probability that flights from a given airport will depart on time on a specified date. The single GET endpoint at /airport/predictions/on-time accepts an airport IATA code and a date and returns a probability score derived from historical performance and forecast conditions. It is used to flag risky connections and to decide whether to recommend buffer time on multi-leg itineraries.
airportsapi is a lightweight reference service that returns the human-readable name and official website URL for an airport given its ICAO code. Coverage focuses on airports in Germany, with limited entries elsewhere. The single-endpoint design makes it useful as a low-friction enrichment step inside flight, logistics, or travel-data pipelines that already have ICAO identifiers.
Jentic publishes the only available OpenAPI specification for AISHub API, keeping it validated and agent-ready. AISHub provides global AIS (Automatic Identification System) data sourced from a community of receiving stations, exposing vessel position retrieval and station metadata. The API is rate-limited to one request per minute and uses an API username passed as a query parameter, so it suits low-frequency monitoring rather than streaming use cases.
Jentic publishes the only available OpenAPI specification for AISHub API, keeping it validated and agent-ready. AISHub provides global AIS (Automatic Identification System) data sourced from a community of receiving stations, exposing two endpoints: vessel position retrieval and station metadata. The API is rate-limited to one request per minute and uses an API username passed as a query parameter, so it suits low-frequency monitoring rather than streaming use cases.
Jentic publishes the only available OpenAPI specification for Algodocs API, keeping it validated and agent-ready. Algodocs is an intelligent document data extraction service for invoices, receipts, and other structured documents. The REST API lets users upload documents (file or base64), route them to a configured extractor, list and inspect documents, organise them into folders, and retrieve the extracted JSON for downstream automation. Authentication uses an API key in the Authorization header.
Jentic publishes the only available OpenAPI specification for All Sports Football API, keeping it validated and agent-ready. AllSportsAPI exposes football (soccer) data — fixtures, live scores, standings, team and player records, head-to-head history, and odds — through a single GET /football/ endpoint. Behaviour is selected via a method query parameter (e.g. Fixtures, Standings, Teams), making this a method-dispatch style API rather than a resource-per-path REST design. Authentication is by query-parameter API key, and responses cover global leagues and competitions.
The Ambee Air Quality API delivers real-time, historical, and forecast air quality data indexed by latitude and longitude, postal code, city, or country code. Each response returns the Air Quality Index (AQI) plus pollutant concentrations for CO, NO2, O3, PM10, PM2.5, and SO2 at the requested location. The spec exposes 7 GET endpoints under api.ambeedata.com, authenticated with a single x-api-key header. It is commonly used by health, climate, logistics, and consumer apps that need pollution data without running their own monitoring network.
Jentic publishes the only available OpenAPI specification for Anti-Captcha API, keeping it validated and agent-ready. Anti-Captcha is a paid CAPTCHA-solving service that exposes seven endpoints for submitting solving tasks (image, reCAPTCHA, hCaptcha, FunCaptcha and friends), polling for the human-or-worker-produced solution, checking account balance, and reading queue statistics. Each task is created with POST /createTask, then polled via POST /getTaskResult until the solution is returned. Authentication uses the clientKey query parameter on every request.
Jentic publishes the only available OpenAPI specification for AnyMailFinder Email Finder API, keeping it validated and agent-ready. AnyMailFinder finds and verifies professional email addresses for prospecting, recruiting, and sales outreach. The API resolves a person email by name and domain, finds the decision-maker email for a target role at a company, verifies an email's deliverability against the recipient's mail server, and accepts bad-email reports to keep results fresh. Authentication is a Bearer token passed in the Authorization header.
Swagger da API responsável pela filtragem de editais. The API exposes 7 endpoints secured with oauth2 authentication.
Jentic publishes the only available OpenAPI specification for API Ninjas City API, keeping it validated and agent-ready. The endpoint returns city records including name, country, latitude and longitude, population, and capital status, covering over 50,000 cities on the free plan and over 5,000,000 cities, towns, and villages on premium. It is a single-endpoint lookup that supports filtering by name, country, minimum and maximum population, and limit. Authentication is by X-Api-Key header.
API-FOOTBALL provides structured access to football (soccer) data covering 1100+ leagues and cups worldwide, including fixtures, lineups, events, statistics, standings, top scorers, transfers, injuries, predictions, and pre-match and in-play odds. Data is updated continuously and supports historical lookback as well as live in-play coverage. The 38 endpoints in this spec cover everything from base reference data such as countries and timezones to deep per-fixture statistics. Authentication is via an x-rapidapi-key style API key passed in the header.