Verifiable air-quality data for smart-city sensors.
A city's sensor network is only as trusted as its weakest node. Dynamic Feed gives you a signed, independent air-quality and weather reference over one keyless call to corroborate a field sensor, plus a workflow that can request an RFC 3161 timestamp artifact for a digest of your own published reading.
The call
One keyless call returns a signed reference reading you can cross-check a local sensor against:
curl -s -X POST https://dynamicfeed.ai/v1/batch \
-H 'Content-Type: application/json' \
-d '{"calls":[{"tool":"air_quality","args":{"city":"Sydney"}}]}'Sample response
{ "results": [ { "tool": "air_quality", "ok": true,
"data": { "us_aqi": 45, "us_aqi_category": "Good", "pm2_5": 8.3, "pm10": 14.1,
"observed_at": "2026-06-15T10:45+10:00",
"provenance": { "source": "Open-Meteo Air Quality" },
"freshness": { "state": "live", "age_seconds": 300 } } } ],
"signature": { "alg": "Ed25519", "key_id": "df-ed25519-...", "sig": "..." } }Why live data
Smart-city and environmental programs publish numbers people make decisions on, so the data needs to be both corroborated and inspectable. Dynamic Feed returns a signed reference air-quality and weather reading over one keyless call to cross-check a field node. Supported workflows can request an RFC 3161 timestamp artifact for a digest of your own published reading; your raw sensor data need not leave your side. Treat that artifact as independent time evidence only after validating the token/CMS, digest binding, certificate chain, EKU, revocation status, and configured trust anchor. The signature establishes integrity and attribution; it 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
- Corroborate a field air-quality node against an independent signed reference
- Flag a drifting or tampered sensor when it diverges from the reference beyond a threshold
- Retain signed published-reading digests so a resident or regulator can inspect them
- Surface provenance + freshness so an automation refuses to act on stale data
FAQ
Is the reference an official monitor?
It is a modelled/observed reference (PM2.5/PM10, US & European AQI) suitable for corroboration, with its source and observed-at time on every datapoint. It is a cross-check, not a substitute for an accredited regulatory monitor.
How does the timestamp-artifact workflow protect my readings?
Hash the reading locally and submit only the digest. A supported workflow can request an RFC 3161 timestamp artifact for that digest. Independent time evidence requires full token/CMS, digest-binding, certificate-chain, EKU, revocation, and trust-anchor validation; the signature alone proves integrity and attribution, not time or truth.
Do I need an API key?
No. MCP and the REST batch endpoint are keyless and free for fair use; a key adds rate and usage controls for a larger network.