Build your product on the network’s data
Desk displays, apps, pilot tools and drones: FlyItalyADSB data can go into a product, even one you sell, on every plan, Free included. Here are the rules in plain words, what each pattern uses and the code to start with.
Measured on 26 October 2026, 20:24 UTC, worldwide.
What are you building?
Displays, frames, LEDs, ESP32
The aircraft overhead on a desk or wall object, from a handful of units to a few thousand.
Spotting apps, alerts, maps
An app or a site that shows traffic, finds unusual flights or sends alerts.
Drones, ultralights, pilots
Low-level traffic near a field, to plan and to know who is in the air.
The rules in short
- 1In a product you sell: yes, on every plan.
- 2One key per product, not per device.
- 3Your own server with a cache: yes, and it’s the lightest option.
- 4One attribution line; share-alike covers the data, not your product.
- 5Over the limits: an error, never extra costs. No SLA.
- 6Position, altitude, speed, registration and type; no routes.
Which plan for which pattern
Requests from all devices and all users count on the same key. A 30-day month; the plan is the smallest one that fits requests per minute, per month and the radius.
| Pattern | Per minute | Per month | Plan |
|---|---|---|---|
| 1 device, every 30 s, 15 km around it | 2 | 86,400 | Free |
| 3 devices, every 30 s, 15 km | 6 | 259,200 | Free |
| 10 devices, every 30 s, 50 km | 20 | 864,000 | Starter |
| 90 devices, every 30 s, 15 km | 180 | 7,776,000 | Pro |
| Your server fetches the whole world every 30 s, for any number of users | 2 | 86,400 | Pro |
Under the limits nothing changes; over them, the request gets an error and isn’t billed. The plans · how to choose.
Where the receivers are
Coverage follows the receivers: where there are many, low-level aircraft show up too. About 3,192 receivers are connected to multilateration; those with a declared position (2,708) split like this, by rough area.
Measured on 26 October 2026, 20:24 UTC, worldwide.
A receiver near you improves coverage for everyone: become a feeder.
Give your assistant these links
Many people arrive here from ChatGPT, Claude or Copilot. The pages for assistants already say it all: endpoints, fields, limits and these rules. Paste the text below into the conversation and the assistant will write the code the right way, with the key on your server. If you only want to ask about aircraft in a chat, there’s the MCP server.
Use the FlyItalyADSB REST API (base https://api.flyitalyadsb.com/v2, header X-Api-Key).
Docs for agents: https://flyitalyadsb.com/llms.txt
OpenAPI 3.1: https://flyitalyadsb.com/openapi.json
Rules for products: https://flyitalyadsb.com/en/data/products/using-the-data/
Call the API only from my server, cache the result for all users, use one key for the whole product,
and show "Flight data: FlyItalyADSB (flyitalyadsb.com), CC BY-SA 4.0" where users see the data.