Building a Resilient AI Text Humanizer with Dual-Engine Fallback (PHP & OpenRouter

If you are building an AI-powered SaaS or a side project, you already know the pain: API downtime and rate limits.

Recently, I built a small, free webmaster toolbox (more on that later). One of the core features is an AI Text Humanizer that rewrites AI-generated text to bypass detectors like Turnitin or GPTZero.

Since I'm bootstrapping this, I relied on free AI models (like those on OpenRouter and SiliconFlow). The problem? Free tiers get heavily rate-limited. If a user hits "Submit" and the API returns a 429 Too Many Requests, a standard error message will immediately kill your conversion rate.

Here is how I built a seamless dual-engine fallback system using pure PHP (no heavy frameworks like Laravel, just vanilla PHP 8) to ensure 99% uptime for my users.

Instead of just calling one API endpoint, my backend logic acts as a traffic controller.

If Engine A takes too long, throws an error, or returns an empty response, the server instantly routes the exact same prompt to Engine B without the user ever knowing.

Here is the stripped-down version of my humanize.php logic.

The key is setting a strict CURLOPT_TIMEOUT. You don't want your user staring at a loading spinner for 30 seconds while Engine A hangs.