LLM API for Law Firms and Legal Tech | TrustedRouter
An LLM API for law firms and legal tech: hardware-attested confidential compute, no prompt storage by default, and attestation your team can verify live.
When the gateway operator provably cannot read the prompt, your privilege analysis starts from different facts.
Legaltech products and law-firm AI pilots stall on the same question: can client documents go to a third-party API without breaching confidentiality duties or risking privilege waiver by disclosure? Most vendors answer with a privacy policy. TrustedRouter answers with hardware. The prompt path runs inside a hardware-attested confidential-compute gateway, the gateway source is open, the image digest is published, and the attestation is checkable live, bound to your TLS session so it cannot be replayed.
TrustedRouter does not store prompt or output content by default. None of this decides the privilege question; that call belongs to your ethics counsel, and nothing on this page is legal advice. What it gives counsel is a better factual record than a promise: a gateway whose operator provably cannot read the prompt, with evidence your team can re-check on every request. Privacy you can check beats privacy you're promised.
from openai import OpenAI
client = OpenAI(
base_url="https://api.trustedrouter.com/v1",
api_key=TRUSTEDROUTER_KEY,
)
resp = client.chat.completions.create(
model="trustedrouter/auto",
messages=[{"role": "user",
"content": "Flag unusual indemnification terms in this clause: ..."}],
)
print(resp.choices[0].message.content)Attestation, checkable live
A signed attestation ties the running gateway to the published open-source image and to your live TLS session. Anyone on your team can check it before, during, and after a matter. Attestation beats a privacy policy. The exact verification steps are on the security page.
Open, Zero-Data-Retention, TEE
Every route carries a privacy tier. Zero-Data-Retention routes use providers contractually bound to keep nothing. TEE routes run end-to-end confidential compute, where even the serving provider cannot read the prompt. For privileged legal documents, pin your product to ZDR and TEE routes.
What your GC will ask for
TrustedRouter publishes SOC 2 readiness and HIPAA readiness documentation your compliance team can assess alongside the verifiable architecture. These are readiness documents; they are not audit reports or certifications. A DPA, a BAA, and a subprocessor list are available. European teams working under professional-secrecy rules such as §203 StGB can route through the EU gateway.
Ship document review on an inference layer a firm's ethics counsel can inspect.
The API is OpenAI-compatible: change base_url, keep your SDK, your model ids, and your code. Behind it sit 220+ model routes across 30+ providers, including Claude, GPT, Gemini, and open-weight models, with automatic provider fallback when a route is down. One anonymized proof point: a document-processing company scaled from zero to over a billion tokens per week through the attested gateway within three weeks of onboarding.
Open-weight routes for DeepSeek, Kimi, Qwen, GLM, and MiniMax are served by non-Chinese hosting providers on attested infrastructure, so prompts do not go to the model vendor. Pay with prepaid credits, bring your own provider key, or use x402 pay-per-request. Per-model pricing is listed at /pricing, and you can compare routes in the model chooser.
Questions
Does TrustedRouter store our prompts or client documents?
TrustedRouter does not store prompt or output content by default. The prompt path runs inside a hardware-attested confidential-compute gateway whose source is open and whose image digest is published. Your team can verify the running code at any time: the attestation endpoint returns a JWT signed by the CPU vendor's root key, bound to your live TLS session so it cannot be replayed.
Does using an LLM API waive attorney-client privilege?
That is a legal determination only your counsel can make, and TrustedRouter does not give legal advice. What the platform changes is the factual record the analysis rests on: on TEE routes the operator provably cannot read the prompt, content is not stored by default, and the attestation is checkable rather than promised. That supports a privilege analysis; it does not decide one.
Is TrustedRouter SOC 2 or HIPAA certified?
No. TrustedRouter publishes SOC 2 readiness and HIPAA readiness documentation, which are readiness documents, not audit reports or certifications. The position is verifiable architecture plus readiness documentation your compliance team can assess. A DPA, a BAA, and a current subprocessor list are available for review, and an EU gateway with EU-focused routing exists for European teams.
Can we use open-weight models like DeepSeek or Qwen without sending data to the model vendor?
Yes. DeepSeek, Kimi, Qwen, GLM, and MiniMax routes are served by non-Chinese hosting providers on attested infrastructure, with Zero-Data-Retention and TEE tiers available, so prompts do not go to the model vendor. For legal work that means access to frontier open-weight models without adding the model vendor to your disclosure chain.