A verifiable audit trail for agent-to-agent activity.
The agent web has no shared system of record. Dynamic Feed gives one: witness each event (or its hash) and it's signed and chained into a permanent log any party can verify — without trusting you, the counterparty, or us.
The call
Keyless over MCP, or one REST call with a free key. Every datapoint is provenance-stamped and citeable.
# Append an event to the audit trail (free key):
curl -s https://dynamicfeed.ai/v1/witness -H "X-API-Key: $KEY" -H "Content-Type: application/json" \
-d '{"content_hash":"","txn_ref":"workflow-step-7"}'
# Verify the chain head (keyless): GET https://dynamicfeed.ai/v1/notary/log/head Sample response
{ "schema": "txn-receipt/v1", "transparency": { "log_index": 4821, "prev_hash": "...", "entry_hash": "...",
"entry_url": "https://dynamicfeed.ai/v1/notary/log/4821" }, "signature": { "alg": "Ed25519", "key_id": "df-ed25519-4cb32e72f333" } }Why live data
Each witnessed event lands in a public append-only hash-chain: entry_hash = sha256(prev_hash + canonical(entry)), so altering any past entry breaks every entry after it and contradicts the chain head — which is anchored to Bitcoin daily via OpenTimestamps. The result is a tamper-evident order-of-events any party can recompute and verify against /.well-known/keys. Dynamic Feed is a neutral recorder OUTSIDE the value path; it witnesses hashes, never moves value or stores PII. It proves what was recorded, in what order, intact — not that any recorded claim is true.
Use it for
- A shared, neutral system-of-record for multi-agent workflows
- Reconstruct exactly what happened, in order, after the fact
- Compliance / dispute evidence neither side can rewrite
- Pairs with agent receipts + verifiable agent identity
FAQ
How is it tamper-evident?
Hash-chaining + a daily Bitcoin anchor of the chain head. Change any past entry and every later entry_hash breaks and contradicts the anchored head. Anyone can recompute the chain.
Do you see the event contents?
Only if you send them. Send the sha256 instead and the log holds a hash — no contents, no PII.
Is this a blockchain?
No — it's a signed append-only log anchored TO Bitcoin (proof-of-existence), not a coin or a ledger of value. Dynamic Feed never moves or holds value.