Signed weather & GPS data for drone fleets.
A drone decides whether to fly on data it usually cannot independently trust. Dynamic Feed delivers signed current weather, a multi-model forecast, aviation weather and a live GPS-interference (jamming) read over one keyless call - each datapoint Ed25519-signed and stamped with its source and observed-at time - so the aircraft or ground station verifies it before acting, and you keep a verifiable record of the conditions you flew under.
The call
One keyless call returns the pre-flight signals plus an Ed25519 signature over the exact bytes - verify on the aircraft before launch:
curl -s -X POST https://dynamicfeed.ai/v1/batch \
-H 'Content-Type: application/json' \
-d '{"calls":[
{"tool":"current_weather","args":{"lat":-33.87,"lon":151.21}},
{"tool":"gps_interference","args":{"region":"baltic"}}
]}'Sample response
{ "results": [
{ "tool": "current_weather", "ok": true,
"data": { "temperature_c": 16.3, "wind_kmh": 11.2, "conditions": "Light drizzle",
"observed_at": "2026-06-15T10:45+01:00",
"freshness": { "state": "live", "age_seconds": 434 } } },
{ "tool": "gps_interference", "ok": true,
"data": { "region": "baltic", "degraded_fraction": 0.53, "severity": "high" } } ],
"signature": { "alg": "Ed25519", "key_id": "df-ed25519-...", "sig": "..." } }Why live data
Drone and UAV operations turn on conditions the aircraft cannot vouch for: the local wind and precipitation, the airspace weather, and whether GNSS is being jammed where you intend to fly. Dynamic Feed returns all of it over one keyless MCP/REST call, with every datapoint signed over its exact bytes against a published Ed25519 key - so a ground station (or a Pi-class companion computer) can verify the reading on-device before launch rather than trusting the pipe. After a flight you can anchor a hash of the conditions and the GPS-interference indicator you acted on to Bitcoin (free, no wallet) for a tamper-evident incident record. A signature proves the datapoint existed unchanged as we reported it at that time; it is not a claim the value is objectively true, and it is evidence, not a safety guarantee — your device's own stack owns every decision. Full integration guide: dynamicfeed.ai/iot.
Use it for
- Gate a launch on signed wind/precipitation + a live GPS-jamming read for the area
- Verify the reading on the ground station or companion computer before takeoff
- Anchor the conditions and the GPS-interference indicator you flew under for incident review
- Feed a fleet dashboard one keyless call instead of stitching three unsigned APIs
FAQ
Do I need an API key?
No. The keyless MCP endpoint and the REST batch endpoint are free for fair use. A key only adds higher rate limits and per-key usage controls for a fleet.
Is the GPS-interference data real-time?
It is derived from live ADS-B (the GPSJam method): the fraction of aircraft in a region reporting degraded navigation accuracy right now. It is an independent indicator, not an official jamming bulletin - the tool says so in its own fields.
What does the signature actually prove?
That the datapoint existed, unchanged, exactly as we reported it at that time, verifiable by anyone against our published key. It is not a claim the value is objectively true, and it is evidence, not a safety guarantee - your flight stack owns the decision.