Situational-awareness API for robots & embodied AI.
One call returns a signed go / caution / no-go advisory for a robot at a location, with the source-attributed facts behind it. Supported records are Ed25519-signed so exact-byte integrity and attribution can be checked.
Advisory evidence — not a safety system. Each verdict is a signed snapshot carrying observation times for public data: NOT a safety certification, safety system or safety function, and not a guarantee that acting is safe. Your control stack owns every action and applies its own safety logic; a valid signature establishes signed-byte integrity and attribution, not independent time, truth or the safety of a decision.
The call
One keyless call. It returns in time or returns degraded — it never blocks a physical system.
# Keyless — POST a robot's location + class:
curl -X POST https://dynamicfeed.ai/v1/awareness -H "Content-Type: application/json" -d '{"robot":{"class":"aerial"},"location":{"lat":51.5,"lon":-0.12}}'
# Back: a go/caution/no-go verdict + grounded facts, Ed25519-signed.
# Request an RFC 3161 artifact for the snapshot digest: POST /v1/anchorSample response
{ "verdict": { "status": "go", "advisory": "Clear to proceed." },
"facts": [ { "id": "wx.wind_kmh", "value": 21, "unit": "km/h",
"source": "Open-Meteo", "age_s": 240, "stale": false } ],
"degraded": false,
"signature": { "alg": "Ed25519", "key_id": "df-ed25519-3a52a473cde2" } }Why live data
A hallucinating chatbot writes a bad sentence; a hallucinating robot puts an arm through a wall. Embodied AI needs verified, low-latency, signed world-state before it acts — and a tamper-evident record after. One call fuses live weather, wind, air quality, space weather and nearby earthquakes into a per-class verdict, with a hard deadline so it never hangs (it degrades to caution instead of blocking).
Use it for
- Drone airspace + wind safety checks before takeoff
- Autonomous-vehicle over-the-horizon hazard awareness
- A reality-check reflex before an embodied LLM commits to an action
- A signed, source-attributed record for incident review
FAQ
Does it ever hang?
No. It returns within a hard deadline; a slow feed is dropped and the snapshot flagged degraded — and a degraded verdict can never be 'go', it floors to caution. A physical system always gets a timely, conservative answer.
What exactly is signed?
Every response is Ed25519-signed over its exact contents. Verify it against the public key at /.well-known/keys — change one byte and the signature breaks.
How does independent timestamping work?
POST a digest to /v1/anchor to request an RFC 3161 artifact. Independent proof requires full token/CMS, digest-binding, certificate-chain, EKU, revocation and trust-anchor validation.
Which robot classes are supported?
ground, humanoid, aerial, marine and orbital — each with its own hazard thresholds, overridable per request.