A verifiable data layer for IoT & edge devices.
Edge devices act on data and produce it, and both directions are usually unverifiable. Dynamic Feed is the layer they plug into: signed world-data that a gateway can verify on-device, plus a keyless endpoint that can request an RFC 3161 timestamp artifact for a digest of a device's own reading. One keyless API, with reference clients for the stacks fleets already run.
The call
One keyless call returns a signed datapoint an edge device verifies before acting:
curl -s -X POST https://dynamicfeed.ai/v1/batch \
-H 'Content-Type: application/json' \
-d '{"calls":[{"tool":"current_weather","args":{"city":"Sydney"}}]}'Sample response
{ "results": [ { "tool": "current_weather", "ok": true,
"data": { "temperature_c": 16.3, "conditions": "Light drizzle",
"provenance": { "source": "Open-Meteo", "measured_at": "2026-06-15T09:45:00Z" },
"freshness": { "state": "live", "age_seconds": 434 } } } ],
"signature": { "alg": "Ed25519", "key_id": "df-ed25519-...", "sig": "..." } }
# verify the signature on-device against /.well-known/keys before actingWhy live data
Most IoT data is unsigned: a device trusts the pipe, and its own telemetry is difficult to verify later. Dynamic Feed addresses both over one keyless API. Inbound datapoints carry source, observed-at time, freshness, and an Ed25519 signature over their bytes, so a gateway can verify integrity and attribution on-device. Outbound, a device can hash its own reading locally and request an RFC 3161 timestamp artifact for the digest. Treat that artifact as independent time evidence only after validating the token/CMS, digest binding, certificate chain, EKU, revocation status, and configured trust anchor. Reference clients exist for Raspberry Pi, ESP32, MicroPython, Home Assistant, Node-RED and MQTT. A signature does not independently prove time, objective truth, or safety; your device's own stack owns every decision. Full integration guide: dynamicfeed.ai/iot.
Use it for
- Feed a gateway signed world-data it verifies on-device before acting
- Request an RFC 3161 artifact for a digest of a device's own reading when the workflow supports it
- Drop one keyless feed into Home Assistant, Node-RED or an MQTT broker
- Run the open-source verifier on a Pi-class device with no network round-trip
FAQ
What can run the on-device verifier?
A Raspberry-Pi / Linux SBC does full float-exact signature verification today; ESP32 (Arduino C++) and MicroPython verify integer/string payloads and prepare receipt digests. An 8-bit Arduino Uno is too small - verify on a Pi-class gateway and fan out.
Does my sensor data leave the device when I request a timestamp artifact?
Not when you hash the reading locally and submit only the 64-hex digest. The supported workflow can request an RFC 3161 artifact for that digest; independent time evidence still requires full token and certificate-path validation.
What exactly does a signature prove?
It establishes integrity and attribution under the published key, so altered datapoint bytes fail verification. It does not independently prove time, truth, or safety. See the full guide at dynamicfeed.ai/iot.