Pre-flight GPS-integrity check for AI drone agents.
Natural-language drone control is now an ops interface, not a demo - an agent can call takeoff_swarm and go_to_point. The missing piece is the pre-flight check: is GNSS being jammed in that airspace, and what's the weather? Dynamic Feed answers that in one keyless call, signed so the aircraft can verify it before acting, and leaves a tamper-evident record of what the agent knew the moment it flew.
The call
One keyless pre-flight call returns the signals an agent checks before takeoff - GPS-interference + aviation weather, each Ed25519-signed:
curl -s -X POST https://dynamicfeed.ai/v1/batch \
-H 'Content-Type: application/json' \
-d '{"calls":[
{"tool":"gps_interference","args":{"region":"baltic"}},
{"tool":"aviation_weather","args":{"icao":"EFHK"}}
]}'Sample response
{ "results": [
{ "tool": "gps_interference", "ok": true,
"data": { "region": "baltic", "degraded_fraction": 0.53, "severity": "high",
"method": "ADS-B NIC/NACp (GPSJam)",
"freshness": { "state": "live", "age_seconds": 41 } } },
{ "tool": "aviation_weather", "ok": true, "data": { "flight_category": "VFR", "wind_kt": 12 } } ],
"signature": { "alg": "Ed25519", "key_id": "df-ed25519-...", "sig": "..." } }
# severity "high" → an agent should HOLD / re-route. Verify the signature on the aircraft before acting.Why live data
The instant an agent can fly a drone, two things become non-optional: (1) it needs verifiable live situational data to act on - above all, is GNSS being jammed where it intends to fly - and (2) a tamper-evident record of what it was told the moment it acted. Dynamic Feed provides both over one keyless call: a live GPS-interference indicator measured from ADS-B navigation integrity (the GPSJam method), aviation weather, and an optional per-class go / caution / no-go awareness verdict at POST /v1/awareness - every answer Ed25519-signed over its exact bytes and optionally Bitcoin-anchored. The open-source verifier runs on a Pi-class companion computer, so the aircraft checks the signature before acting, no network round-trip. To be precise: a signature is proof a reading existed unchanged at a time - tamper-evidence, NOT a claim it is accurate and NOT a safety certification. It is evidence; your flight stack owns every decision. Full guide: dynamicfeed.ai/iot.
Use it for
- Gate takeoff_swarm on a live GPS-jamming read + aviation weather for the area
- Have the agent HOLD or re-route when an airspace reads high GPS-interference
- Verify each datapoint's signature on the companion computer before acting
- Anchor a signed record of the conditions + indicator the agent flew under, for incident review
FAQ
Does this control the drone?
No. Dynamic Feed is a read-only data + verification layer: it tells the agent what's true (signed) so it can decide. It is evidence, not an autopilot and not a safety system - your flight stack (PX4/MAVLink and your own logic) owns every actuation.
Where does the GPS-interference signal come from?
It's derived from live ADS-B: the fraction of aircraft in a region reporting degraded navigation integrity/accuracy (NIC/NACp) right now - the public GPSJam method. An independent indicator, not an official jamming bulletin.
Do I need an API key?
No. The pre-flight call is keyless over MCP or the REST batch endpoint. A key only adds higher rate limits for a fleet.