<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0">
    <channel>
        <title>AI API - Tag - Daily Deep Think</title>
        <link>https://blog.baifan.site/en/tags/ai-api/</link>
        <description>AI API - Tag - Daily Deep Think</description>
        <generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>blog@baifan.site (ByF)</managingEditor>
            <webMaster>blog@baifan.site (ByF)</webMaster><lastBuildDate>Tue, 06 Jan 2026 14:00:00 &#43;0800</lastBuildDate><atom:link href="https://blog.baifan.site/en/tags/ai-api/" rel="self" type="application/rss+xml" /><item>
    <title>Self-Hosted AI API Pipeline: From Domain Email to Sub2API</title>
    <link>https://blog.baifan.site/en/self-hosted-ai-api-pipeline/</link>
    <pubDate>Tue, 06 Jan 2026 14:00:00 &#43;0800</pubDate><author>
                    <name>ByF</name>
                </author><guid>https://blog.baifan.site/en/self-hosted-ai-api-pipeline/</guid>
    <description><![CDATA[<div class="featured-image">
                <img src="/pictures/note/self-hosted-ai-api-featured.svg" referrerpolicy="no-referrer">
            </div><p>I originally wrote this post for a friend; I&rsquo;m just cleaning it up a bit and publishing it.</p>
<p>I&rsquo;ll assume you&rsquo;ve never touched domain email, Cloudflare Workers, SMS-code platforms, registration bots, or AI API relays before. Wherever possible I&rsquo;ll explain things in terms of &ldquo;why this step exists&rdquo; and &ldquo;how to confirm you did it right&rdquo;. When you get stuck, you can just paste the error into an AI and ask — in my testing, Codex handles this kind of deployment doc and config troubleshooting reasonably well. But sanitize API keys, passwords, cookies, and tokens before sending them to an AI. Don&rsquo;t ask me how I know.</p>]]></description>
</item>
</channel>
</rss>
