A receipt beside every agent payment.
Agent wallets move the money; someone has to make the spend defensible. Dynamic Feed is that someone: witness the payment record (or its hash) and get a signed, independently-verifiable receipt — without Dynamic Feed ever touching, holding or routing the funds.
The call
Keyless over MCP, or one REST call with a free key. Every datapoint is provenance-stamped and citeable.
# After your rail (x402 / AP2 / Stripe) settles, witness the record (free key):
curl -s https://dynamicfeed.ai/v1/witness -H "X-API-Key: $KEY" -H "Content-Type: application/json" \
-d '{"content_hash":"","parties":["agent:payer","merchant:x"],"txn_ref":""}'
# Dynamic Feed witnesses the record. Your rail moves the money. They never overlap. Sample response
{ "schema": "txn-receipt/v1", "data": { "content_hash": "sha256:...", "txn_ref": "x402-settlement-…",
"parties": ["agent:payer","merchant:…"] }, "signature": { "alg": "Ed25519", "key_id": "df-ed25519-6ca0de29113b" } }Why live data
When an agent pays — and a human or policy is on the hook for it — the question on any disputed charge is what was agreed and what the agent acted on. Dynamic Feed witnesses the payment RECORD beside whatever rail settled it (x402, Google AP2, Stripe agent checkout): it signs the record's hash and logs the signed record so all parties can inspect the same bytes. Supported workflows can request an RFC 3161 artifact for that digest, but independent time evidence requires full artifact and certificate-path validation. Dynamic Feed is NOT a payment processor or money transmitter: it never accepts, holds, routes, converts or custodies funds, and holds no key that releases money. It records what was reported; it does not make the payment happen or prove it was authorized or completed.
Use it for
- A defensible record behind 'you take responsibility for your agent's spend'
- An independent receipt either side of an agent purchase can re-check
- Sits beside x402 / AP2 / Stripe agent checkout — never competes with them
- Feeds AI-liability and chargeback evidence
FAQ
Are you a payment processor or money transmitter?
No, and by design never will be. Dynamic Feed signs a record hash and records the caller-reported time. A supported workflow can separately request an RFC 3161 artifact, which must be fully validated before relying on time evidence. We never accept, hold, route, convert or custody funds.
How does it fit x402 / AP2 / Stripe?
After your rail settles, you send the settlement record (or its hash) to be witnessed. The receipt is independent of the rail and verifiable by any party.
What does it prove?
That the record existed and is intact (tamper-evident) and which agent co-signed — NOT that the payment was authorized, correct, or completed. Evidence, not settlement.