<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Model-Routing on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/model-routing/</link>
    <description>Recent content in Model-Routing on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 30 Apr 2026 12:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/model-routing/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>LiteLLM vs One-API: Self-Hosted LLM API Gateway Comparison 2026</title>
      <link>https://www.pistack.xyz/posts/2026-04-30-litellm-vs-one-api-self-hosted-llm-api-gateway-guide/</link>
      <pubDate>Thu, 30 Apr 2026 12:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-04-30-litellm-vs-one-api-self-hosted-llm-api-gateway-guide/</guid>
      <description>&lt;p&gt;If your organization works with multiple LLM providers — OpenAI, Anthropic, Azure, Google, local models via Ollama — managing separate API keys, rate limits, and request formats quickly becomes a nightmare. An &lt;strong&gt;LLM API gateway&lt;/strong&gt; solves this by presenting a single unified API endpoint that routes requests to any backend provider.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
