DEV Community

Steve
Steve

Posted on

How to prove what your AI agent emailed

When an AI agent sends email for you, you usually have only its own account of what it sent. That is a weak record. The first time someone asks "did we really send that, to whom, and what was checked first?", your own logs are all you have, and nobody outside your company can check them.

Here is a different approach: a signed receipt for each send, which anyone can check in a browser, without an account and without seeing your email.

What the receipt contains

SentriSend is an outbound email security gateway. Each successful single send returns a field called publicReceipt. It is a compact JWS signed with an Ed25519 key, and it records:

  • a random receipt ID, the time it was issued, and the issuer (https://sentrisend.com)
  • the outcome, provider_accepted, which means the email provider took the message, not that it reached an inbox
  • the result of each check run before sending: recipient pre-flight, a global threat lookup, and policy
  • two salted SHA-256 "commitments", one for the recipient and one for the subject and message

It does not contain the address, the subject, the message body or your API key. The commitments are fingerprints. They let you prove later that a receipt belongs to one particular send, without revealing what was sent.

The public keys are at https://sentrisend.com/api/v1/receipts/keys, so anyone can check a signature without asking SentriSend for permission.

Check a real one

This receipt comes from a real send through the production service on 17 November 2026. It has no address, subject or message text in it:

eyJhbGciOiJFZERTQSIsInR5cCI6InNlbnRyaXNlbmQtcmVjZWlwdCtqd3MiLCJraWQiOiJyZWNlaXB0LWQ3ZGY5ZDk3LTdkNjMtNDIxNC04ZGI3LTk3ZjE4MGRiN2Y4MiJ9.eyJ2ZXJzaW9uIjoxLCJpc3MiOiJodHRwczovL3NlbnRyaXNlbmQuY29tIiwidHlwZSI6InNlbnRyaXNlbmQuc2VuZC1yZWNlaXB0IiwicmVjZWlwdElkIjoiYTE5MmE3ODctZjhkYS00MTUxLWE3ZWEtYzI4NmE1Zjk4MjY2IiwiaXNzdWVkQXQiOiIyMDI2LTExLTE3VDIwOjMwOjQ4LjUwNFoiLCJvdXRjb21lIjoicHJvdmlkZXJfYWNjZXB0ZWQiLCJjaGVja3MiOnsicmVjaXBpZW50UHJlZmxpZ2h0IjoiYWxsb3dlZCIsImdsb2JhbFRocmVhdExvb2t1cCI6Im5vX21hdGNoIiwicG9saWN5IjoiYWxsb3dlZCJ9LCJyZWNpcGllbnRDb21taXRtZW50IjoiOWYxNzkzZWUyYWQwMzYwODQzNTMwOGM0ZTY1NTE4YzVhMTcxODE5Yzk0MjBlYjU2NGE5MTY4YWJiMmQ3ZDM2ZCIsIm1lc3NhZ2VDb21taXRtZW50IjoiMmI0NmYxNTk2ZjY0Y2Y5MTViNWQ5NGI4NjFiZGNmYjEyNDE3MTU2NWRmNWE4ZmZlNTIxZmNmY2I0MjIxOTVmMSJ9.UtbX-w-lCv1oYlxeccWdqGDvOfXxKv-8gFheY8Mnkdy4Hfw3wCidoqB8-5a1Ha7O8tTDz9Pww6LnIwZ2NRi2CQ
Enter fullscreen mode Exit fullscreen mode

Paste it into the checker at sentrisend.com/receipts and press Check signature. The page reports whether it matches a published, non-revoked key, and shows the decoded fields.

To tie a receipt to one particular send, you also need the original recipients, subject and message, plus the opening data returned with the send. The comparison runs in your browser. Even a trailing space changes the result, because the commitments are exact.

What a receipt does not show

  • Delivery. provider_accepted means the provider accepted the message, not that it was read.
  • That the message was appropriate. The checks are the ones SentriSend ran. They are not a judgement on the content.
  • Anonymity. Someone who guesses your recipient list could test the guess against the opening data, so handle it with care.

The opening data (two random salts) comes back only in the original send response, and SentriSend doesn't store it. Keep it if you may want to prove a send later.

Try it

A free Sandbox key needs no card, allows 100 requests a month, and sends only to its owner's verified address, so it is a safe way to try receipts on your own mailbox. Full field definitions are in the OpenAPI description.

Top comments (1)

Collapse
 
innerluxes profile image
INNERLUXES •

The part that usually bites is not proving the send, it's proving what the agent checked before sending. A receipt over the final message gives you the content, but the dispute is almost always about the decision: which recipient list was loaded, which policy version was in force, whether a human approval existed at all. Does the receipt cover the approval event too, or only the outbound message?