<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Angel Avocado</title>
    <description>The latest articles on DEV Community by Angel Avocado (@monseant).</description>
    <link>https://dev.to/monseant</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3894517%2Fb54a2a13-53cb-47ae-8479-e70ba0cfff8c.png</url>
      <title>DEV Community: Angel Avocado</title>
      <link>https://dev.to/monseant</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/monseant"/>
    <language>en</language>
    <item>
      <title>I built an API gateway for 48 AI models — here's how it works</title>
      <dc:creator>Angel Avocado</dc:creator>
      <pubDate>Thu, 23 Apr 2026 14:52:33 +0000</pubDate>
      <link>https://dev.to/monseant/i-built-an-api-gateway-for-48-ai-models-heres-how-it-works-1j5b</link>
      <guid>https://dev.to/monseant/i-built-an-api-gateway-for-48-ai-models-heres-how-it-works-1j5b</guid>
      <description>&lt;p&gt;I've been working on RiftAI — an OpenAI-compatible API gateway that gives developers access to 48+ AI models through a single endpoint.&lt;/p&gt;

&lt;h2&gt;
  
  
  The problem
&lt;/h2&gt;

&lt;p&gt;If you work with multiple AI providers (OpenAI, Anthropic, Google, etc.), you end up managing multiple API keys, different SDKs, and separate billing. It gets messy fast.&lt;/p&gt;

&lt;h2&gt;
  
  
  The solution
&lt;/h2&gt;

&lt;p&gt;RiftAI provides one API key that works with all major models: Claude, GPT-5, Gemini, DeepSeek, Qwen, GLM, Llama and more. The endpoint is fully OpenAI-compatible, so any existing code that works with OpenAI works with RiftAI — just change the base URL.&lt;/p&gt;

&lt;h2&gt;
  
  
  Credit-based pricing
&lt;/h2&gt;

&lt;p&gt;Instead of per-token billing, RiftAI uses a daily credit pool. Each model has a cost multiplier based on how resource-heavy it is:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;DeepSeek V3: ×1 (very cheap)&lt;/li&gt;
&lt;li&gt;Gemini 2.5 Flash: ×2&lt;/li&gt;
&lt;li&gt;GPT-5: ×8&lt;/li&gt;
&lt;li&gt;Claude Sonnet 4.6: ×25&lt;/li&gt;
&lt;li&gt;Claude Opus 4.7: ×60 (premium)&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Formula:&lt;/strong&gt; &lt;code&gt;credits = (input_tokens × multiplier) + (output_tokens × multiplier × 3)&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;This means you can use cheap models for simple tasks and save credits for premium models when you actually need them.&lt;/p&gt;

&lt;h2&gt;
  
  
  Quick start
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;curl https://riftai.su/v1/chat/completions &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;-H&lt;/span&gt; &lt;span class="s2"&gt;"Authorization: Bearer YOUR_API_KEY"&lt;/span&gt; &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;-H&lt;/span&gt; &lt;span class="s2"&gt;"Content-Type: application/json"&lt;/span&gt; &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;-d&lt;/span&gt; &lt;span class="s1"&gt;'{
    "model": "gemini-2.5-flash",
    "messages": [{"role": "user", "content": "Hello!"}]
  }'&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  Plans
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Free:&lt;/strong&gt; 100K credits/day, no card required&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Paid:&lt;/strong&gt; from $4.99 to $149.99/mo with up to 100M credits/day&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;There's a credit calculator on the pricing page so you can estimate costs: &lt;a href="https://riftai.su/pricing" rel="noopener noreferrer"&gt;riftai.su/pricing&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Would love to hear feedback from the dev community.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>api</category>
      <category>saas</category>
      <category>programming</category>
    </item>
  </channel>
</rss>
