Cut your LLM bill by 7–50%, depending on your workload.

No. Your messages pass through the proxy to reach the AI provider. Our audit and billing logs contain metadata only — token counts, timestamps, provider, and billing meters. Prompt and response content is not persisted beyond the compression step. Retention windows, sub-processors, and data-subject rights are enumerated in our Data Processing Agreement.

No. Ordica reduces token count without changing what your prompt asks the AI to do. The compressed version produces equivalent responses — validated blind across 150 prompts × 4 providers (RAG cohort in progress) with a separate AI judging equivalence on a 1–5 scale: mean equivalence 4.38 on OpenAI, 3.96 on Anthropic, 3.78 on Gemini, 3.76 on Grok. If the engine cannot compress safely, your prompt goes through untouched — you never get a worse response. Per-provider quality scores are published in the methodology page.

The compression adds a few milliseconds — you won't notice it. Whether you're using GPT-4o, Claude, Gemini, or Grok, the provider's response time is what you feel, and that's unchanged. In some cases, shorter prompts actually get faster responses because the AI has less to process.

Ordica's compression is deterministic on our tested model corpus — the same input produces byte-identical output across repeated runs under equivalent configuration, so provider-side cache keys stay stable. In our verified test harness, a compressed prompt produced a full read-hit on the second call (Anthropic cache_read_input_tokens equal to cache_creation_input_tokens), confirming no interference on that path. Results on other prompt shapes are expected to hold but are measured per workload rather than universally asserted. If you're already using provider-side caching, you keep your cache hits.

For customers whose prompts already include cache_control markers: Ordica leaves those markers untouched. Your existing caching setup works exactly as before.

The system is fail-safe by design. If compression cannot be applied confidently, your prompt passes through untouched — you just don't save tokens on that message. Under normal operation the compressed prompt reaches the model and responses should match the original within the equivalence bounds we publish; if the engine can't compress safely, you get the uncompressed path rather than a degraded one. Worst case is zero savings, not worse quality.

Billing runs on token counts, not estimates. For every request, we record the token count of the prompt you sent and the token count of the prompt we forwarded to the provider — both measured against the provider's tokenizer reference. The difference is your savings; your bill is a fixed percentage of the dollar value of that difference. Your Stripe receipt shows the metered total for the billing period, and the savings analytics in your account show the per-request counts that produced it. Anything we cannot measure, we do not charge for: if compression is skipped on a request (pass-through), that request contributes zero to your bill. Enterprise customers can request a full billing audit export covering any billing period.

GPT-4o is a strong all-rounder — great for general questions, writing, and brainstorming. Claude is known for natural writing and careful, thoughtful responses. Gemini has a large context window and strong reasoning on structured problems. Grok is fast and conversational with less filtering. Try each and see which fits your workload.

Yes. The Free tier gives you the drop-in proxy endpoint — point your existing OpenAI or Anthropic SDK at Ordica with one environment variable — 10,000 requests per month, and a savings dashboard. No credit card required. You get the same compression engine as paid tiers. When you're ready for higher limits and the full optimization profile, Pro and Enterprise are there.

We charge a percentage of your measured savings — 30% on Pro, 20% on Enterprise. If compression saves you $100, you keep $70 (Pro) or $80 (Enterprise). If it saves you nothing, you pay nothing. Your dashboard shows every dollar in real time. No flat fees, no minimums, no surprises.

Your provider API key transits the Ordica proxy in-memory. We use it to authenticate with the provider you chose — OpenAI, Anthropic, xAI, or Google — on your behalf for that single request, then discard it when the request completes. We do not retain it, log it, store it in a database, or share it. The key is used only to reach the provider endpoint you designated; it never leaves that path.

Honest limitation: while your request is in flight, the key is held in process memory on our proxy layer — that's unavoidable for any middleware that forwards authenticated traffic. Ordica is not a secrets vault or KMS and does not claim to be. You hold the key in your code or secret manager the same way you do today, and you can rotate it anytime through your provider's dashboard if you ever want to cut access.

Routing your own API key through a middleware layer is a standard pattern — every major provider (OpenAI, Anthropic, xAI, Google) builds an API ecosystem around SDK wrappers, gateways, observability proxies, and caching layers. Ordica is structured to fit cleanly within that allowed pattern: you remain the authorized account holder, your requests go only to providers you designate, and we do not resell, pool, rent, or share API access across customers. We also do not retain prompt or response content after each request completes.

On that basis Ordica keeps you on the permitted side of each provider's current Terms. What providers actually prohibit (multi-tenant key pooling, API-key resale, unauthorized account sharing) is not what we do. Provider Terms vary by vendor and evolve over time — review your current provider's Terms to confirm compatibility with your specific workload. For enterprise documentation — DPAs, subprocessor list, data-flow diagrams — contact us.