ALL SYSTEMS LIVE·67 INSTRUMENTS · 18 VERTICALS
ED25519 · BITCOIN-ANCHORED·--:--:-- UTC
Ed25519-signed · verify in-browser

Verified data for AI agents, provable in one click.

Agents act on what they're told — so what they're told should be provable. Every Dynamic Feed response carries its source, licence and timestamp, and is Ed25519-signed over its exact bytes. Verify one right now, in your browser.

The call

Keyless. Fetch signed data, then verify it against the published key — in the box above, with scripts/verify_awareness.py, or by hand.

# keyless — a signed, grounded snapshot any agent can verify
curl -X POST https://dynamicfeed.ai/v1/awareness -H "Content-Type: application/json" -d '{"robot":{"class":"ground"},"location":{"lat":-27.47,"lon":153.02}}'

# the public key — verify the signature yourself, no account
curl https://dynamicfeed.ai/.well-known/keys

Sample response

{ "facts": [ { "id": "wx.wind_kmh", "value": 21, "unit": "km/h",
               "source": "Open-Meteo", "age_s": 240, "stale": false } ],
  "signature": { "alg": "Ed25519", "key_id": "df-ed25519-4cb32e72f333",
                 "canonicalization": "json-sorted-compact", "sig": "..." } }

Why live data

To an agent, a hallucinated number, a stale cache and a fresh fact all look identical: text. The fix isn't bigger models, it's a data layer whose answers carry their own evidence — source, licence and timestamp on every datapoint, an Ed25519 signature over the exact bytes, and optional Bitcoin anchoring for proof-of-when. The agent (or its auditor, or its customer) can verify any answer independently, even years later — against us, not just with us. A signature proves we reported this data at this time; it doesn't claim the data is objectively true — no signature can.

Use it for

FAQ

How is this different from a normal data API?

Three layers a raw API doesn't have: a provenance envelope (source, licence, timestamp, age) on every datapoint; an Ed25519 signature over the exact canonical bytes; and optional Bitcoin anchoring plus a permanent archive, so what was true on a date stays provable.

Does a signature prove the data is true?

No — and we say so plainly. It proves authenticity (it came from us), integrity (unaltered) and time. The truth claim stays with the named upstream source, which every response cites.

How does an agent verify in practice?

Drop the signature field, canonicalize the rest (JSON, keys sorted, compact separators), check the Ed25519 signature against /.well-known/keys. The widget above does it in your browser; /verify.js and scripts/verify_awareness.py are the reference implementations.

What does it cost?

The MCP endpoint and /v1 verification surfaces are keyless. A free REST key adds limits and usage; paid plans from US$19/month — /#pricing.

Related live feeds

Ready when your agent is

Plug your agent into the now.

Keyless over MCP, or a free REST key — 67 live tools, signed and Bitcoin-anchored. Live in under a minute.