Signed, tamper-evident data for autonomous agents.
When an agent acts on data with no human in the loop, you need to prove the bytes it consumed were not altered between source and decision. Dynamic Feed signs every datapoint with Ed25519 and stamps it with source, observed-at and freshness - so any downstream step can verify the payload independently.
The call
Each result comes back with an Ed25519 signature plus a provenance block (source, observed-at, freshness). Re-canonicalize the payload and verify the signature against the published key at /.well-known/keys before your agent acts on it:
curl -s -X POST https://dynamicfeed.ai/v1/batch \
-H "Content-Type: application/json" \
-d '{"calls":[{"tool":"gps_interference","args":{"region":"baltic"}},{"tool":"earthquakes","args":{"min_magnitude":5.0}}]}'Sample response
{ "mcpServers": { "dynamic-feed": { "url": "https://dynamicfeed.ai/mcp" } } }Why live data
An autonomous agent often passes data through several hops - a proxy, a queue, another model - before it drives an action. A signature lets the final step confirm the payload is byte-for-byte what we emitted, so silent corruption or a man-in-the-middle edit is detectable rather than invisible. Be precise about what the signature means: it establishes integrity and attribution under the published key, so altered bytes fail verification. It does not independently prove time, truth, accuracy, or safety. Provenance (source, observed-at, freshness) is included so your own policy layer can judge whether the reading is fresh and trustworthy enough for the action at hand. Supported workflows can request an RFC 3161 timestamp artifact for a digest; independent time evidence requires full token/CMS, digest-binding, certificate-chain, EKU, revocation, and trust-anchor validation. The verifier is open: re-canonicalize the payload and check it against the public key yourself.
Use it for
- Prove an autonomous agent acted on unaltered, attributable data
- Gate an action behind a freshness and provenance check before execution
- Keep a tamper-evident audit trail of every external reading a fleet consumed
- Verify payloads independently across multi-hop agent pipelines
FAQ
Does a signature mean the data is correct?
No. The signature establishes integrity and attribution under the published key, so altered bytes fail verification. It does not independently prove time, truth, accuracy, or safety. Your policy layer still decides whether to act, using the provenance and freshness carried with each datapoint.
How do I verify a signature myself?
Re-canonicalize the returned payload, fetch our public key from https://dynamicfeed.ai/.well-known/keys and check the Ed25519 signature. The verifier is open and reproducible, so you never have to trust our server - if a byte changed in transit, verification fails.
Do I need an API key?
No. The MCP endpoint at https://dynamicfeed.ai/mcp and the REST endpoint POST https://dynamicfeed.ai/v1/batch are both keyless and free for fair use. Signing and provenance stamping apply to every datapoint regardless of tier.