<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Cloudflare on ByF (BaiFan) · Daily Deep Think</title>
    <link>https://blog.baifan.site/en/tags/cloudflare/</link>
    <description>Recent content in Cloudflare on ByF (BaiFan) · Daily Deep Think</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <managingEditor>blog@baifan.site (ByF (BaiFan))</managingEditor>
    <webMaster>blog@baifan.site (ByF (BaiFan))</webMaster>
    <copyright>CC BY-NC 4.0</copyright>
    <lastBuildDate>Tue, 06 Jan 2026 14:00:00 +0800</lastBuildDate><atom:link href="https://blog.baifan.site/en/tags/cloudflare/index.xml" 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 +0800</pubDate>
      <author>blog@baifan.site (ByF (BaiFan))</author>
      <guid>https://blog.baifan.site/en/self-hosted-ai-api-pipeline/</guid>
      <description>&lt;p&gt;I originally wrote this post for a friend; I&amp;rsquo;m just cleaning it up a bit and publishing it.&lt;/p&gt;&#xA;&lt;p&gt;I&amp;rsquo;ll assume you&amp;rsquo;ve never touched domain email, Cloudflare Workers, SMS-code platforms, registration bots, or AI API relays before. Wherever possible I&amp;rsquo;ll explain things in terms of &amp;ldquo;why this step exists&amp;rdquo; and &amp;ldquo;how to confirm you did it right&amp;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&amp;rsquo;t ask me how I know.&lt;/p&gt;</description>
      
    </item>
    
  </channel>
</rss>
