AnonRoutervs OpenRouter
OpenRouter routes your prompts in the clear and asks you to trust its policy. AnonRouter runs prompt handling inside an attested enclave and publishes that code under Apache 2.0.
Every router can see your prompts. This one is built so it cannot.
What each router can see
A promise you can read, or a boundary you can verify.
Both routers publish a privacy policy. Only one of them publishes the code that the policy is about, which is the part you cannot audit from the outside.
“This setting has no bearing on OpenRouter's own policies and what we do with your prompts.”
Your prompt at the router
AnonRouter
Handled inside an attested enclave, and on E2EE routes encrypted to that enclave so the router holds no key.
OpenRouter
Arrives in plaintext on OpenRouter's servers, which is what lets it route and bill the request.
Who the request belongs to
AnonRouter
A ticket. The system that knows your account and the system that sees content are separated.
OpenRouter
A registered account. Usage is attributable to you by design.
Code that can touch plaintext
AnonRouter
Published under Apache 2.0 as the confidential content plane, which is every component inside the enclave.
OpenRouter
Closed source. The published SDKs run on your side; the service handling the prompt is not public.
How you check it
AnonRouter
Run the SDK, pull the enclave's attestation, and compare it against the published build.
OpenRouter
Read the privacy policy and trust it.
Retention policy and routing
AnonRouter
Routing filters to eligible privacy levels first and fails closed rather than downgrading.
OpenRouter
Documents that routing rules do not change based on a provider's data-retention policy.
Read the code that handles your prompt
A privacy claim about a closed service can only ever be a statement of intent. These two repositories are the reason ours is not.
Apache 2.0
The code that touches your prompt is public
Zero prompt logs
No content retention at the router
Hardware attested
Check the enclave yourself before trusting it
The core difference
Built for different guarantees
Both routers put one API in front of many providers. They differ in what the layer between your application and the model is designed to guarantee.
OpenRouter
Built for model access
OpenRouter connects you to a large catalog of models and providers through one API, and stops there.
Best for:
- A longer model list
- Input types our catalog does not cover
- BYOK
- Hand-tuned provider selection
AnonRouter
Built for private model access
AnonRouter puts a strict content-retention boundary and privacy-aware routing layer between your application and 200+ models.
Best for:
- A lower current platform fee
- No router-side prompt or response logs
- Private accounts and separated request roles
- Routing that fails closed on privacy
Pricing
A lower platform fee
AnonRouter's 5% launch fee is about 9.1% lower than OpenRouter's 5.5% fee. That is a difference in the platform fee, not a discount on model inference. Both services pass provider rates through without markup.
Current percentage fee
9.1%
lower at AnonRouter
Based on current public pay-as-you-go rates, before tax. Minimum fees apply to small top-ups.
Platform fee by credit purchase
Exact fee paid, before tax
$10 credits
$50 credits
$100 credits
$250 credits
Feature comparison
What you get here and nowhere else
Nine things AnonRouter does that OpenRouter's gateway does not. Every row is a capability, not a setting you have to trust someone to leave switched off.
Source of the code handling prompts
AnonRouter
Yes. Apache 2.0, including every component that can touch plaintext.
OpenRouter
No. The gateway that receives your prompts is closed source.
Verifying the privacy claim
AnonRouter
Yes. Pull the enclave attestation with the SDK and check it against the published build.
OpenRouter
No. There is nothing to attest against, so the policy is the guarantee.
Prompt and response storage at the router
AnonRouter
Never. There is no content-logging switch to enable later.
OpenRouter
Possible. Content logging ships as an account setting, off by default.
Router-side use of inputs
AnonRouter
None. No training and no durable prompt categorization.
OpenRouter
Yes, by arrangement. A 1% discount is offered for data use, and prompts may be sampled.
End-to-end encrypted routes
AnonRouter
Yes, wherever the provider runs an enclave. The router holds no key.
OpenRouter
No. Prompts arrive at the gateway in plaintext.
Identity separated from request content
AnonRouter
Yes. A ticket flow splits account identity, plaintext, and provider credentials.
OpenRouter
No. One proxy, and every request stays attributable to your account.
Privacy floor on automatic routing
AnonRouter
Yes. /auto stays inside a privacy boundary and fails closed when nothing qualifies.
OpenRouter
No. Their docs state routing rules do not change based on a provider's retention policy.
Account without an email address
AnonRouter
Yes. Private accounts open with a recovery phrase instead of an inbox.
OpenRouter
No. Registration is required to get a key.
Platform fee
AnonRouter
5% with a $0.75 minimum during the launch promotion.
OpenRouter
Higher. 5.5% with a $0.80 minimum.
Why AnonRouter
Why teams choose AnonRouter
The value is not only access to models. It is what the router is structurally unable to retain.
Audit the router instead of trusting it
Every component that can touch prompt plaintext is published under Apache 2.0, and the SDK checks the enclave's attestation against that build.
Remove prompt logging from the product
Prompts and responses are never written to disk. There is no router-side content logging switch to enable later.
Pay a lower platform fee
Model usage bills at the displayed provider rate. The only charge is a platform fee on credit purchases, currently 5%.
Separate identity from request content
The private ticket flow splits the systems that know your account, handle plaintext, and hold provider credentials.
Route inside a privacy boundary
The /auto router filters to eligible privacy levels first, then selects for capability, quality, and cost.
See what every route guarantees
Anonymous, Private, TEE, and E2EE labels make the actual privacy boundary visible before a request is sent.
For both routers, upstream provider policy still matters. A no-log router cannot make every model provider private. Review the exact route label, and use an explicitly supported E2EE route when you need the strongest available boundary.
Choosing
When to choose which
OpenRouter remains the better fit for some stacks. The decision changes when privacy and fee structure move to the front of the requirements list.
Choose OpenRouter when
- You need a specific model that is not in our catalog yet
- Your product depends on an input type our catalog does not cover
- You rely on BYOK
- You would rather hand-tune provider selection than route inside a privacy boundary
Choose AnonRouter when
- You need to audit the code that handles prompts, not just read a policy
- Router-side content logging must be impossible, not just off
- Platform fees are material: 5% vs. 5.5%, with a lower minimum
- Account identity and request content must stay separated
- Automatic routing needs a privacy floor that fails closed
- You want a private account without an email address
OpenRouter vs AnonRouter FAQ
Sources & methodology
Check the primary sources
This comparison is published by AnonRouter and is not affiliated with OpenRouter. It uses current public product pages and documentation, reviewed September 11, 2026. Pricing can change; each service's live checkout is authoritative.
OpenRouter sources
Switch by changing the base URL
Point your OpenAI SDK at AnonRouter, or browse the catalog first. A private account does not need an email address.