For agents and robots that act,
proof, not promises.
When an AI acts on the world, "trust me" isn't enough. Dynamic Feed hands any agent or robot a cryptographically signed snapshot of the verified present and time-stamps its fingerprint with an independent RFC 3161 authority, so anyone can prove exactly what it was told the moment it acted, independently, even against us.
A verdict that can't hang
One call → a go / caution / no-go verdict for a robot at a location (ground · humanoid · aerial · marine · orbital), with the grounded facts behind it. A hard deadline guarantees a timely answer; stale safety data floors it to caution. A physical system never waits.
Every answer is signed
Each snapshot carries an Ed25519 signature over its exact canonical bytes (json-sorted-compact). Verify it against the published key, change one byte and it breaks. A record of exactly what we reported.
Timestamped, RFC 3161
The snapshot's hash is time-stamped by an independent RFC 3161 authority (instant). Only the fingerprint is sent, never the data. Prove the record existed at that time, whenever you need to.
What signing does (and doesn't) prove.
A signature proves Dynamic Feed reported X at time T, authenticity, tamper-evidence, and a signature we cannot later disown. It is the verifiable audit trail of what an AI was told when it acted. It is not a claim that X is objectively true in the world, no signature can promise that. Verify everything yourself against the public key; you never have to take our word for it.
Signed verdicts, one call.
Drone pre-flight
Wind, weather, air quality, space-weather (GPS/comms) & nearby hazards → a signed take-off verdict.
AV over-the-horizon
Weather, air quality & nearby earthquakes / hazards along the route → a signed go / caution / no-go.
Compliance receipt
Wrap any fact / claim in a timestamped, signed record, the audit trail regulated AI (fintech / legal / medical) needs.
Don't trust us, check it.
# 1) get a signed awareness snapshot (keyless)
curl -X POST https://dynamicfeed.ai/v1/awareness -H "Content-Type: application/json" \
-d '{"robot":{"class":"aerial"},"location":{"lat":51.5,"lon":-0.12}}'
# 2) fetch the public key and verify the Ed25519 signature
curl https://dynamicfeed.ai/.well-known/keys
# canonical form = JSON of the response WITHOUT its "signature" field, keys sorted, compact separators
# reference verifier: scripts/verify_awareness.py · C# client: clients/csharp/AwarenessClient.cs
# 3) timestamp the snapshot's hash via an independent RFC 3161 authority (free)
curl -X POST https://dynamicfeed.ai/v1/anchor -H "Content-Type: application/json" -d '{"snapshot": { ... }}'Free, keyless, no wallet required. Chain-of-custody for any datapoint: /v1/sources + /v1/explain.
🔐 Verify a signature, in your browser, right now
Don't take our word for it. Fetch a fresh signed verdict (or paste any signed Dynamic Feed response that includes its signature block) and check the Ed25519 signature against the published key. The check runs entirely client-side, the only thing fetched from us is the public key. Change one byte and it fails.
Same scheme as the reference verifier (scripts/verify_awareness.py): canonical = the response JSON without its signature field, keys sorted, compact separators.
Put a live badge on your site.
Grounding your app on Dynamic Feed? Drop in a badge that verifies a fresh signature in your visitor's browser, live proof your data is signed, not just claimed. It links back here.
Live demo (verifying now):
<div data-df-verify></div>
<script type="module" src="https://dynamicfeed.ai/verify.js"></script>Prefer a static shield? /badge/verified.svg (and live-value shields like /badge/models.svg).
Proof your agent can stand behind.
Every answer Ed25519-signed and time-stamped by an independent RFC 3161 authority, independently verifiable, even against us.