Blog

Topic

#gateway

8 articles

Matrix of seven protocol dimensions across OpenAI Chat Completions, Anthropic Messages and Gemini generateContent, with the field name each vendor uses

One API for OpenAI, Anthropic and Google models: what translates, and the seven things that leak through

Leo Kaka
Matrix of six LLM API products offered as OpenRouter alternatives — Cloudflare AI Gateway, AWS Bedrock, Google Vertex, Groq, LiteLLM and Portkey — against four production columns: cross-vendor failover, a spend cap below the account, the Anthropic Messages API, and a zero-data-retention control, each cell marked available, gated or absent according to the vendor's own documentation

OpenRouter alternatives for production workloads: what Cloudflare, Bedrock, Vertex, Groq, LiteLLM and Portkey actually document

Leo Kaka
Hand-drawn illustration: one open team wallet on a wooden workbench with five hands reaching in at once, a single yellow coin among grey tokens, and a brass padlock hanging unlatched from the clasp

Shared team wallet for LLM APIs: who actually has one, and what each cap misses

Leo Kaka
Matrix of failover trigger conditions across seven LLM gateways: 5xx, timeouts and 429 are covered everywhere, by default or opt-in; 404 is opt-in or unstated in most; the row for a 200 whose provider state changed is empty in every column, with Portkey's guardrail path as the one partial exception noted in the text

Automatic failover in LiteLLM, Portkey and OpenRouter: what actually triggers it, and the 429 no gateway tracks

Leo Kaka
Matrix of three LLM routers, LiteLLM, OpenRouter and Portkey, against four budget dimensions: the per-key cap parameter, the shared wallet, when the check runs, and the HTTP status returned when the cap is hit

Per-key spending limits: what LiteLLM, OpenRouter and Portkey enforce — and the four leaks a cap doesn't close

Leo Kaka
Path diagram: model tokens become Qwen3 Coder XML, enter the vLLM tool parser, reach a highlighted eval() call and then the host; below it a version bar showing eval() present from v0.10.0 through v0.10.1 and removed in v0.10.1.1

Is the vLLM tool-call parser safe? CVE-2025-9141, the 29-day eval() window, and four checks a gateway owes you

Leo Kaka
The five MCP roadmap priority areas listed in order, with agent identity and improved primitives marked as the two that land on the layer in front of the server

The MCP roadmap hands agent identity to your gateway

PiRouter Team
GitHub's own growth charts from the August 17 post-mortem: merged pull requests, commits and new repositories per month, 2023–2026 (The GitHub Blog)

Retry storms: 9K to 100K RPS, and four rules that stop them

Leo Kaka