What Can You Build?
- AI agents that answer questions about live aircraft, earthquakes, storms and satellites.
- Dashboards for aviation, maritime, space, weather or disaster monitoring.
- Educational maps and demos that need real-world data without complex API setup.
Examples
GET /api/live-summary for compact live counts. GET /api/flights for aircraft. GET /api/quakes for seismic events. GET /api/tle-catalog for orbital objects.
Please keep requests reasonable, cache where possible, and attribute upstream providers listed in the public API page.
Use live endpoints defensively
Public API responses reflect upstream availability and may contain partial or unknown fields. Clients should honor timestamps, cache repeated requests, handle empty arrays without treating them as errors, and preserve provider attribution. Historical guarantees, higher limits and commercial service levels are separate from the free public interface.
What PocketWorld adds
The public endpoints expose the normalized records used by the product: consistent JSON envelopes, practical cross-origin access and source metadata where available. PocketWorld is not the owner of upstream observations and does not grant rights beyond each provider's terms. Applications should retain source names, avoid polling faster than the documented limit and design for partial outages. A successful HTTP response can legitimately contain no observations for a place or time.
Examples on the API page are intended to be reproducible without registration. They show basic error handling and caching so a demo does not become an accidental denial-of-service client.
Licensing and attribution
PocketWorld aggregates upstream public APIs and community datasets. Consumers should follow the attribution, caching and licensing terms documented for each endpoint and its original provider.