The AI ground truth you can cryptographically verify.
Most data layers ask you to trust them. Dynamic Feed signs every answer with Ed25519 and lets you verify it — right here in your browser — against a published key. Change one byte and it fails.
The call
Keyless. Fetch a signed verdict, then verify it yourself — in the box above, with scripts/verify_awareness.py, or by hand.
# 1) get a keyless signed verdict
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) verify the Ed25519 signature against the published key
curl https://dynamicfeed.ai/.well-known/keys
# canonical = the response WITHOUT its "signature" field, keys sorted, compact separators
# reference verifier: scripts/verify_awareness.py - or verify in-browser above / at /proofSample response
{ "verdict": { "status": "go" },
"signature": { "alg": "Ed25519", "key_id": "df-ed25519-6ca0de29113b",
"canonicalization": "json-sorted-compact", "sig": "..." } }Why live data
When an AI only writes text, a wrong answer is a bad sentence. When it acts — a robot, a trade, a filing — you need a tamper-evident record of exactly what it was told. Supported Dynamic Feed paths sign canonical bytes with Ed25519, and anyone can verify integrity and attribution against the published key. A valid signature does not establish objective truth or independent time. Supported workflows can request an RFC 3161 artifact for a digest; independent time evidence requires full token, digest-binding and certificate-path validation.
Use it for
- Robots & drones — a signed go/caution/no-go record before acting
- Fintech / legal / medical — a tamper-evident audit trail for regulated AI
- Compliance & gov procurement — independently verifiable provenance, not ‘trust us’
- Any agent — cite a signed, source-attributed record instead of a guess
FAQ
How do I verify a signature?
Fetch a response, drop its ‘signature’ field, canonicalize the rest (JSON, keys sorted, compact separators), and check the Ed25519 signature against the key at /.well-known/keys. The box above does exactly this in your browser; scripts/verify_awareness.py and the /proof widget do too.
What does a signature actually prove?
Authenticity and integrity — a signature we cannot later disown: Dynamic Feed reported this exact data at this time and it has not been altered. It is not a claim that the data is objectively true; no signature can promise that.
Can I request independent time evidence?
POST /v1/anchor requests an RFC 3161 artifact for a digest. Treat it as independent time evidence only after validating the token/CMS, digest binding, certificate chain, EKU, revocation status and configured trust anchor.