Signed receipts for agent transactions.
When agents pay, book, sign or subscribe, the contested question is what was agreed, by whom, and when. Dynamic Feed is the neutral witness: POST /v1/witness returns a signed receipt of the record — keyless to verify, a free key to issue.
The call
Keyless over MCP, or one REST call with a free key. Every datapoint is provenance-stamped and citeable.
# Witness a transaction record (free key, no KYC):
curl -s https://dynamicfeed.ai/v1/witness -H "X-API-Key: $KEY" -H "Content-Type: application/json" \
-d '{"content_hash":"","parties":["agent:buyer","agent:seller"],"txn_ref":"order-123"}'
# Keyless — see a sample + verify it in-browser: https://dynamicfeed.ai/witness Sample response
{ "schema": "txn-receipt/v1", "data": { "content_hash": "sha256:...", "parties": ["agent:buyer","agent:seller"] },
"witnessed_at": "2026-07-14T00:00:00Z", "signature": { "alg": "Ed25519", "key_id": "df-ed25519-6ca0de29113b" } }Why live data
Dynamic Feed witnesses a machine-to-machine transaction record by signing its hash and recording it in the existing log. Send the record, or keep it private and send only its sha256. An agent can co-sign with its own key, so the receipt shows which key attested. Supported workflows can separately request an RFC 3161 artifact for the digest; treating that artifact as independent time evidence requires validation of the token, digest binding, certificate chain, EKU, revocation state and trust anchor. Dynamic Feed sits BESIDE the transaction and NEVER in the value path — it never accepts, holds, routes or custodies funds. A receipt proves integrity and attribution under the signing scheme — NOT that the transaction was authorized, correct, or that any value moved.
Use it for
- A signed, independent record of what two agents agreed, and when
- Resolve agent-transaction disputes on facts, not he-said/she-said
- An audit trail an insurer or auditor can re-check without trusting either party
- Pairs with agent identity + the awareness verdict trail
FAQ
Do you move or hold the money?
No. Dynamic Feed is a neutral WITNESS — it signs a hash of a record you give it. It never accepts, holds, routes or custodies funds. A receipt rail, not a payment rail.
What does the receipt prove?
The Ed25519 signature makes the exact record and signing key checkable. A separately requested RFC 3161 artifact can add independent time evidence only after full token and certificate-path validation. Neither proves the transaction was authorized, correct, lawful, or that value moved.
Can I keep the transaction private?
Yes — send only the sha256 of your record. Dynamic Feed witnesses the hash, never the contents. No PII.