ADS-B Exchange API

Name: ADS-B Exchange API
Brand: ADS-B Exchange API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMaps GeolocationPlaces SearchapiKey13 EndpointsREST

For Agents

Look up aircraft positions, military flight tracks, and registration details from the unfiltered ADS-B Exchange feed by location, ICAO hex, callsign, or registration.

Install Jentic One Beta

Connect the ADS-B Exchange API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the ADS-B Exchange 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.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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 ADS-B Exchange API.

Find aircraft within a radius of a latitude/longitude using GET /aircraft/json/lat/{lat}/lon/{lon}/dist/{dist}/

Look up a specific aircraft's current position and metadata by ICAO hex code via /aircraft/icao/{icao}/

Track flights by callsign or registration to follow a known aircraft across its route

GET STARTED

Start building with ADS-B Exchange API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use ADS-B Exchange API for, with concrete tasks.

★ Live Aircraft Map for a Region

Power a flight-tracking dashboard or alerting tool by polling ADS-B Exchange for every aircraft inside a geographic radius. The /aircraft/json/lat/{lat}/lon/{lon}/dist/{dist}/ endpoint returns position, altitude, speed, heading, and squawk for matching aircraft so a UI or notifier can render them on a map. Useful for airport noise monitors, plane-spotting apps, and emergency response dashboards covering up to several hundred miles in one call.

Call GET /aircraft/json/lat/40.6413/lon/-73.7781/dist/50/ and return a list of all aircraft within 50 nautical miles of JFK with their callsign, altitude, and ground speed

Specific Aircraft Lookup by Hex or Registration

Identify a single aircraft and pull its latest telemetry without scanning a region. Agents can resolve an ICAO 24-bit hex (/aircraft/icao/{icao}/), a tail number (/aircraft/registration/{reg}/), or a callsign (/aircraft/callsign/{callsign}/) into the same telemetry payload. This is the right path when a user references a specific airframe by N-number, G-registration, or filed callsign.

Call GET /aircraft/registration/N628TS/ and return the current latitude, longitude, altitude, and last-seen timestamp for the requested tail number

Military and Restricted Aircraft Feeds

ADS-B Exchange is one of the only public sources that does not filter government, military, or blocked aircraft. The /aircraft/mil/, /aircraft/ladd/, and /aircraft/pia/ endpoints expose the live military feed, FAA Limiting Aircraft Data Display list, and Privacy ICAO Address registrations. OSINT analysts and journalists use these feeds to monitor government and corporate flights that disappear from filtered providers.

Call GET /aircraft/mil/ and return every military aircraft currently transmitting, grouped by aircraft type

Agent-Driven Flight Investigation via Jentic

An AI agent investigating a sighting, news event, or aviation incident can use Jentic to discover and call ADS-B Exchange operations from a natural-language prompt. The agent searches Jentic for an aircraft-tracking intent, loads the matching operation schema, and executes the call with credentials managed by your Jentic One instance. No code generation, no manual key handling, and no separate RapidAPI subscription wiring inside the agent context.

Use Jentic to search for 'find aircraft near coordinates', load the ADS-B Exchange radius lookup operation, and execute it for the user's chosen lat/lon and radius

Key Endpoints

13 endpoints — jentic publishes the only available openapi specification for ads-b exchange api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/aircraft/json/lat/{lat}/lon/{lon}/dist/{dist}/

Aircraft within a radius of coordinates

GET

/aircraft/icao/{icao}/

Lookup by ICAO 24-bit hex code

GET

/aircraft/callsign/{callsign}/

Lookup by callsign

GET

/aircraft/registration/{reg}/

Lookup by tail number or registration

GET

/aircraft/type/{type}/

All aircraft of a given type code

GET

/aircraft/mil/

All currently tracked military aircraft

GET

/aircraft/ladd/

Aircraft on the LADD restricted list

GET

/aircraft/pia/

Aircraft using Privacy ICAO Addresses

GET

/aircraft/json/lat/{lat}/lon/{lon}/dist/{dist}/

Aircraft within a radius of coordinates

GET

/aircraft/icao/{icao}/

Lookup by ICAO 24-bit hex code

GET

/aircraft/callsign/{callsign}/

Lookup by callsign

GET

/aircraft/registration/{reg}/

Lookup by tail number or registration

GET

/aircraft/type/{type}/

All aircraft of a given type code

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your ADS-B Exchange X-RapidAPI-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.

Intent-based discovery

Agents search Jentic by intent such as 'find aircraft near coordinates' or 'get the military aircraft feed', and Jentic returns the matching ADS-B Exchange operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using ADS-B Exchange API through Jentic.

Why is there no official OpenAPI spec for ADS-B Exchange API?

ADS-B Exchange does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call ADS-B Exchange API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the ADS-B Exchange API use?

The API is distributed via RapidAPI and uses an apiKey scheme. Requests must include an X-RapidAPI-Key header (an alternative api-auth query parameter is also defined). When called through Jentic, the RapidAPI key is stored in your Jentic One instance and injected at request time so the agent never sees the raw key.

Can I track military aircraft with the ADS-B Exchange API?

Yes. Unlike most flight-tracking APIs, ADS-B Exchange does not filter military or restricted aircraft. The dedicated GET /aircraft/mil/ endpoint returns every military aircraft currently transmitting ADS-B, and /aircraft/ladd/ and /aircraft/pia/ expose the LADD and PIA restricted lists.

How do I find aircraft near a specific location through Jentic?

Search Jentic for 'find aircraft near coordinates', load the ADS-B Exchange radius operation, and call GET /aircraft/json/lat/{lat}/lon/{lon}/dist/{dist}/ with your coordinates and search radius. Jentic returns the structured response so the agent can iterate over aircraft directly.

What are the rate limits for the ADS-B Exchange API?

Rate limits are set by the RapidAPI subscription tier you select on adsbexchange-com1.p.rapidapi.com - the OpenAPI spec itself does not declare programmatic limits. Choose a paid tier matched to your polling frequency before running production workloads.

Can I look up an aircraft by tail number?

Yes. GET /aircraft/registration/{reg}/ accepts a tail number or registration mark (for example N628TS) and returns the latest telemetry. /aircraft/icao/{icao}/ accepts the ICAO 24-bit hex, and /aircraft/callsign/{callsign}/ accepts a filed callsign.

Can I limit what my agent is allowed to do with the ADS-B Exchange API?

Yes. Because you run Jentic One yourself, your own rules decide which ADS-B Exchange operations and which stored RapidAPI key the agent may use, so you can allow only the lookups a task needs, such as finding aircraft near coordinates or pulling the military feed. Every operation on this API is a read-only lookup, whether by latitude and longitude radius, ICAO hex, callsign, registration, or aircraft type, so a scoped agent reads live tracking data without changing anything. You can, for example, permit the /aircraft/json/lat/{lat}/lon/{lon}/dist/{dist}/ radius search while withholding the /aircraft/mil/, /aircraft/ladd/, and /aircraft/pia/ feeds.