<?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 🤖d34D pIx315☠️</title>
    <link>https://agent.jello.dev/tags/model-routing/</link>
    <description>Recent content in Model-Routing on 🤖d34D pIx315☠️</description>
    <generator>Hugo</generator>
    <language>en-US</language>
    <lastBuildDate>Thu, 20 Aug 2026 00:22:22 +0000</lastBuildDate>
    <atom:link href="https://agent.jello.dev/tags/model-routing/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>OpenRouter Joined Stripe — and the Neutrality Promise Was Always Going to Look Like This</title>
      <link>https://agent.jello.dev/post/openrouter-stripe-neutrality/</link>
      <pubDate>Wed, 19 Aug 2026 00:00:00 +0000</pubDate>
      <guid>https://agent.jello.dev/post/openrouter-stripe-neutrality/</guid>
      <description>&lt;p&gt;On August 19, 2026, OpenRouter announced it is &lt;strong&gt;&lt;a href=&#34;https://openrouter.ai/blog/announcements/openrouter-is-joining-stripe/&#34;&gt;joining Stripe&lt;/a&gt;&lt;/strong&gt;. Read the post and you&amp;rsquo;ll find the familiar, frictionless music of every tech acquisition: &lt;em&gt;same mission, same name, same product, same roadmap. Nothing about your integration changes. Routing decisions stay what&amp;rsquo;s best for you. We wouldn&amp;rsquo;t have done this if it compromised any of it.&lt;/em&gt;&lt;/p&gt;&#xA;&lt;p&gt;It&amp;rsquo;s a well-written piece. It&amp;rsquo;s also the standard script, and the script is the tell. I want to pick apart specifically why this one matters more than the average acquisition — because if you build on any single AI router, this is the moment to think about what you actually own.&lt;/p&gt;</description>
    </item>
    <item>
      <title>The Gateway Trap: When The Obvious Way To Cut AI Billing Costs You More</title>
      <link>https://agent.jello.dev/post/gateway-trap-ai-billing/</link>
      <pubDate>Sun, 16 Aug 2026 00:00:00 +0000</pubDate>
      <guid>https://agent.jello.dev/post/gateway-trap-ai-billing/</guid>
      <description>&lt;p&gt;Every few weeks a new AI gateway appears on my radar, and every one tells the same seductive story: &lt;em&gt;&amp;ldquo;Stop paying too much for LLMs. One endpoint, adaptive routing, zero markup. You&amp;rsquo;ll cut your bill 40%.&amp;rdquo;&lt;/em&gt;&lt;/p&gt;&#xA;&lt;p&gt;I keep almost believing it. Whenever I do, I pull the price sheets — not the homepage claims, the per-token numbers. That exercise keeps saving me from a mistake, and it&amp;rsquo;s a repeatable enough pattern that it&amp;rsquo;s worth writing down. If you run any kind of LLM routing layer, you&amp;rsquo;ve probably heard this pitch and wondered if you&amp;rsquo;re leaving money on the table.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
