Tag

openai-compatible

5 posts tagged "openai-compatible".

Posts

Latest first

LLM Streaming Failures: Why Mid-Stream Retry Duplicates Output
Engineering

LLM Streaming Failures: Why Mid-Stream Retry Duplicates Output

Streaming makes responses feel fast, but it creates a hard recovery boundary. Learn when an LLM request can fail over safely, why emitted tokens cannot be replayed silently, and how clients should handle partial output.

nRouter team
11 minRead →
One API Key Across Providers: The Integration You Stop Writing
Product

One API Key Across Providers: The Integration You Stop Writing

Provider breadth behind a single OpenAI-compatible key. What the swap changes in your codebase, what the model string buys you, which providers are live today, and the integration work that stops being yours to maintain.

nRouter team
11 minRead →
Migrate Off OpenRouter: The Base-URL Swap and What Does Not Map
Product

Migrate Off OpenRouter: The Base-URL Swap and What Does Not Map

Moving an OpenAI-compatible app from OpenRouter to nRouter is two lines of config. The work that is actually left is model-slug mapping, the vendor extensions you added, and a cost-and-error contract that behaves differently. Here is the whole checklist.

nRouter team
10 minRead →
Claude Proxy: One Base URL for Budgets, Fallback and Cost Data
Product

Claude Proxy: One Base URL for Budgets, Fallback and Cost Data

Point your Anthropic client at one gateway base URL and every Claude call arrives with a hard budget, a fallback path, a per-request cost header, and a team it can be billed to. No SDK rewrite, no provider key to paste.

nRouter team
11 minRead →
nRouter: One Key, Many Providers, a Cost on Every Call
Product

nRouter: One Key, Many Providers, a Cost on Every Call

nRouter is a managed LLM gateway. One OpenAI-compatible key reaches every model in your catalog, every response carries its exact cost, and guardrails, budgets, A/B tests and prompt management are on every plan, not gated.

nRouter team
11 minRead →