One call → a signed go / caution / no-go verdict for a robot at a location, with the grounded facts behind it. It never blocks, and the record is Ed25519-signed and anchored to Bitcoin.
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.
# Anchor the snapshot's hash to Bitcoin (free, no wallet): POST /v1/anchor{ "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" } }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).
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.
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.
POST the snapshot to /v1/anchor and its SHA-256 is timestamped on the Bitcoin blockchain via OpenTimestamps — only the hash, never the data. Free, no wallet.
ground, humanoid, aerial, marine and orbital — each with its own hazard thresholds, overridable per request.