Introduction

You can now enable the TEE Confidential Computing Attestation option for a specified APIKey. Once enabled, every request made with that APIKey will generate an independently verifiable receipt proving that the request was genuinely sent to the real upstream domain, along with the input and output content.

What does it mean?

You can't see what happens between us and the upstream provider: whether the response really came from the model you selected, or whether the model was swapped, parameters were changed, or content was rewritten. In the past, you had to take our word for it.

Now, you can verify it yourself.

What can it prove?

• The actual request target: The receipt records the upstream domain, path, and public key of the upstream TLS certificate that were actually connected to.
• The original input and output data: The hashes of the request and response content are written into the receipt, including for streaming responses. This leaves model adulteration and prompt injection attacks nowhere to hide.
• No one can forge it: Receipts are issued by VeriRelay running inside an AMD SEV-SNP confidential VM. The signing key is isolated by hardware, so the VeriRelay service operator cannot cheat.
• Open, auditable code: The remote attestation report corresponds to publicly available source code that can be reproducibly built.

How to enable it?

1. Go to the API Key creation or edit page.
2. Check "TEE Confidential Computing Attestation".
3. After saving, requests made with this Key will carry X-VeriRelay-* fields in the response headers.

Integration stays the same — no changes to the existing API endpoint or SDK are required.

How to verify?

Option 1: One-click verification on the website

1. Go to "Usage" → "Request Details".
2. Find the corresponding request and click the "Verifiable" button to view a popup of this request's VeriRelay response headers.
3. Click the jump button in the popup to go to the VeriRelay website, where you can quickly complete verification on VeriRelay.

Please complete verification or download and save the evidence within 1 hour after the request is completed.

Option 2: Verify on your own

After the response completes, download the receipt evidence bundle, then use the open-source Verifier to validate it locally:

    verifier check evidence.json request.bin response.bin

You can also follow the public Protocol to implement the verification project's code and principles yourself.