Verifiable, signed data for AI that acts.
Most data for AI is 'trust me.' Supported Dynamic Feed paths provide source-attributed records whose signed-byte integrity can be checked against a published key.
The call
Verify supported signatures against the published key; request a separate RFC 3161 artifact when your workflow needs independently validated time evidence.
# Every awareness snapshot is signed. Fetch the public key:
curl https://dynamicfeed.ai/.well-known/keys
# Request an RFC 3161 artifact for a snapshot digest:
curl -X POST https://dynamicfeed.ai/v1/anchor -H "Content-Type: application/json" -d '{"snapshot": { ... }}' Sample response
"signature": { "alg": "Ed25519", "key_id": "df-ed25519-3a52a473cde2", "sig": "base64url(...)" }
# POST /v1/anchor ->
{ "backend": "rfc3161", "digest_sha256": "...", "artifact_b64": "..." }Why live data
When an AI acts on the world, 'trust me' is not enough. A valid Ed25519 signature establishes integrity and attribution for the signed bytes. It does not establish objective truth or independent time. A supported workflow can separately request an RFC 3161 artifact for the record digest; independent time evidence requires full token/CMS, digest-binding, certificate-chain, EKU, revocation and trust-anchor validation.
Use it for
- Tamper-evident decision records for robots and agents
- Compliance / audit trails for regulated fintech, legal and medical AI
- Request an RFC 3161 artifact for a record digest
- Defend or investigate an AI's action with cryptographic evidence
FAQ
How is the data signed?
Ed25519 over the canonical JSON of each snapshot. The public key is published at /.well-known/keys (JWKS-style), so anyone can verify independently.
What does an RFC 3161 artifact add over a signature?
A signature establishes integrity and attribution. A fully validated RFC 3161 artifact can add independent time evidence for the digest; it must be checked for token/CMS validity, digest binding and a trusted certificate path.
Does the payload leave my system?
Not when you submit only its SHA-256 digest. Preserve the returned artifact alongside the original bytes.
Can I verify it without trusting Dynamic Feed?
Verify the Ed25519 signature against the published public key. Separately validate the RFC 3161 token/CMS, digest binding, certificate chain, EKU, revocation status and configured trust anchor.