A contemporaneous record to defend an AI decision.
When an AI or autonomous system is blamed for a loss, the contested question is what data it was given, and exactly when that data was measured. Supported Dynamic Feed paths deliver an Ed25519-signed record carrying its source and measurement time, so the data your system consumed can be produced and checked later — evidence, not legal advice.
The call
Keyless over MCP, or one REST call with a free key. Every datapoint is provenance-stamped and citeable.
# Keyless over MCP — point any client at https://dynamicfeed.ai/mcp
# Or one signed REST call (free key) — full reference at https://dynamicfeed.ai/docs:
curl -s https://dynamicfeed.ai/v1/batch -H "Content-Type: application/json" \
-d '{"calls":[{"tool":"","args":{}}]}' Sample response
{ "value": "...", "provenance": { "source": "...", "measured_at": "...Z", "age_seconds": 42 },
"signature": { "alg": "Ed25519", "key_id": "df-ed25519-6ca0de29113b" } }Why live data
Some liability frameworks — notably the EU's revised Product Liability Directive — now let courts presume a defect and causation in complex AI cases where proof is excessively difficult; the presumption is rebuttable. A contemporaneous record of the data a system was given can help explain the decision context. Supported Dynamic Feed paths sign the exact record and preserve source and measurement time, so the data can be produced and re-checked later. A valid signature establishes integrity and attribution, not the independent truth of the time or the correctness of a decision. Supported workflows can request an RFC 3161 artifact for a digest; treating it as independent time evidence requires full token, digest-binding and certificate-path validation. This is evidence, not legal advice.
Use it for
- A signed record of the Dynamic Feed data behind an automated decision
- Defence material if an AI or robot decision is later disputed
- Incident review — show which Dynamic Feed inputs were available, and when
- Pairs with the signed go/caution/no-go verdict trail for embodied AI
FAQ
Does this prove my AI was right?
No. A valid signature establishes integrity and attribution under the signing key. It does not independently prove time, objective truth or that acting on the value was correct. It is evidence of the inputs, not a verdict on the decision.
Is this legal advice?
No. Dynamic Feed is a data-evidence layer, not a law firm. We provide verifiable records you and your counsel can use; we don't advise on liability.
How is the record kept tamper-evident?
Supported records are Ed25519-signed over canonical bytes, so a changed signed byte fails verification. A workflow can also request an RFC 3161 artifact for a digest; independent time evidence requires full token, digest-binding and certificate-path validation.