anonrouter
Sign up

Trust / Verification

Check the proof.

Inspect the gateway’s current verification, the checks behind it, and the release it’s running.

Checking the enclave

Your browser is checking a fresh response from the enclave.

Intel TDXapi.anonrouter.ai

Checked in your browser

Recomputed locally from the quote and signed release policy.

Checking
Fresh quote answered your challenge

Waiting for fresh evidence to run this check.

Binding hash recomputed

Waiting for fresh evidence to run this check.

Quote commits to the binding

Waiting for fresh evidence to run this check.

Intel TDX quote, debug off

Waiting for fresh evidence to run this check.

Bound to api.anonrouter.ai, TLS inside the enclave

Waiting for fresh evidence to run this check.

Instance ID matches the boot key

Waiting for fresh evidence to run this check.

Release policy signed by both custodians

Waiting for fresh evidence to run this check.

Running code is an approved release

Waiting for fresh evidence to run this check.

Check our work.

Download the evidence and copy the review prompt. Then check the result with an AI of your choice.

Check with

ChatGPTClaudeAnonChat
Read the review prompt

Reported by control

Intel signature, platform firmware, and the TLS key control observed.

Checking
Signed by Intel

Waiting for fresh evidence to run this check.

Platform firmware up to date

Waiting for fresh evidence to run this check.

Control's connection ended at the enclave key

Waiting for fresh evidence to run this check.

Running release

Gateway
api.anonrouter.ai
Release policy
Checking…
Approved image
Checking…
Release
Checking…
App ID
Checking…
Compose hash
Checking…
Quote SHA-256
Checking…
Raw evidence & measurements
Loading signed evidence…

Protected routing.Verifiable hardware.

Client, protected gateway, and model providerAn encrypted connection joins your client to the secure enclave within AnonRouter’s gateway. The enclave routes selected content to the external model provider. A separate verification path checks fresh evidence relayed by control and the signed release. Account and billing receive only content-free metadata.AnonRouter gatewayGateway verificationYour clientSecure enclaveTLS ends inside isolatedIntel TDX hardware.Model provider
Client, protected gateway, and model providerAn encrypted connection joins your client to the secure enclave within AnonRouter’s gateway. The enclave routes selected content to the external model provider. A separate verification path checks fresh evidence relayed by control and the signed release. Account and billing receive only content-free metadata.AnonRouter gatewayYour clientGateway verificationSecure enclaveTLS ends inside isolatedIntel TDX hardware.Model provider

With AnonRouter

  • Your connection is encrypted directly to the secure enclave.
  • Prompts and responses stay out of the control plane.
  • You can verify the gateway’s hardware evidence and signed release.

What this checks

A snapshot of AnonRouter’s gateway. Your browser checks the challenge, binding, and signed release. Intel and observed TLS results are reported by control.

What it doesn’t check

Model providers, past chats, and the TLS key of your browser’s own connection. For independent hardware verification, use the SDK.

Independent verification guide