Make OpenRouter
more open.

The router can tamper with your prompt, answer, model choice, and model identity. VeriRouter opens routing to verification while protecting the router’s private assets.

01 Attack demo

The router can cheat.

A toothache question becomes a sponsored recommendation or an answer from the wrong model. Our demo exposes the router actions behind these outcomes.

02 Verification demo

Make the router prove it.

Our framework, VeriRouter, uses zero-knowledge proofs to verify model eligibility and endorsed request rewriting. A provider-signed serving certificate authenticates the model and its answer. The router’s semantic index and rewrite banks stay private.

03 Interactive demo

Try the verifier.

Client question

I have a toothache. Can I put crushed aspirin on my gum?

Client
VeriRouter
Backend model

Client request

Loading request…

Browser verification

Selection proofReady
—
Rewrite proofReady
—
Serving certificateReady
—
Total verification— ms
Ready to verify.

04 Performance

Trust that keeps up.

Client verification

11.91 msFresh selection
7.04 msLater session-pinned turns

Evidence & signing

Selection proof
0.15 MiB
Rewrite proof
0.14 MiB
Backend signing
3.84 ms0.145 KiB certificate

Practical serving latency

Added per turn · Proving overlaps inference.

Session-pinned selection
0.38%+0.11 s
Per-turn selection
14.24%+4.08 s

05 Paper

VeriRouter: Towards Verifiable LLM Routing

BibTeX

@misc{yao2026verirouter,
  title={VeriRouter: Towards Verifiable LLM Routing},
  author={Mengyu Yao and Ziqi Zhang and Shaofei Li and
          Yifeng Cai and Ding Li and Yao Guo and Ning Luo},
  year={2026},
  eprint={2610.17431},
  archivePrefix={arXiv},
  primaryClass={cs.CR},
  url={https://arxiv.org/abs/2610.17431}
}

06 Get started

Integrate VeriRouter into your router.

Earn your users’ trust with verifiable routing. Keep your routing data and prompt banks proprietary.