cliproxyapi-cloudflare-stack

Deploy an OpenAI-compatible LLM API gateway with Cloudflare Tunnel.

119|10|Updated Jul 12, 2026

Search Tags:#automation #llm #cloudflare #tunneling #api-gateway #self-hosted

Ready to run

npx skills add https://github.com/xsser/cliproxyapi-cloudflare-stack --skill cliproxyapi-cloudflare-stack

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: cliproxyapi-cloudflare-stack
Source: https://github.com/xsser/cliproxyapi-cloudflare-stack/tree/main
Command: npx skills add https://github.com/xsser/cliproxyapi-cloudflare-stack --skill cliproxyapi-cloudflare-stack

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires python3, wrangler, gh, git, curl, jq, rsync, and includes scripts (resource) components.

What problem does it solve?

This skill solves the challenge of managing multiple LLM credentials and API access without relying on third-party proxies, ensuring you maintain full control over your infrastructure and security.

Core Features & Use Cases

API Gateway: Exposes an OpenAI-compatible /v1 endpoint with credential hot-reloading and failover capabilities.
Secure Exposure: Uses Cloudflare Tunnel to provide HTTPS access to your internal gateway without opening public inbound ports.
Inbound Mail Handling: Deploys a Cloudflare Worker and D1 database to programmatically manage email-based credential verification.

Quick Start

Deploy the gateway stack to your Linux VM by executing the provided deployment script and configuring the Cloudflare Tunnel service.

Frequently Asked Questions about cliproxyapi-cloudflare-stack

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I deploy a self-hosted OpenAI-compatible LLM API gateway using Cloudflare Tunnel?▼

You can deploy a self-hosted LLM API gateway by running the provided deployment script on a Linux VM, which configures CLIProxyAPI and establishes a secure Cloudflare Tunnel for external HTTPS access without opening public inbound ports.

How does email-based credential verification work for an automated LLM API gateway?▼

Email-based credential verification is handled by a Cloudflare Worker and D1 database that programmatically route and manage inbound verification emails, enabling automated account authentication workflows for your LLM credential pools.

Do I need Cloudflare Workers and D1 to maintain secure private API access for my LLM credentials?▼

Yes, Cloudflare Workers and D1 are required to handle inbound email routing for automated account verification, while a Linux VM and Cloudflare Tunnel maintain secure, private HTTPS access to your internal API gateway.

Can I manage multiple LLM credentials with hot-reloading and failover without third-party proxies?▼

Yes, the gateway exposes an OpenAI-compatible endpoint with credential hot-reloading and failover capabilities, allowing you to manage multiple LLM credentials directly and maintain full control over your infrastructure without third-party proxies.

What are the limitations of using Cloudflare infrastructure for tunneling an internal API gateway?▼

Using Cloudflare infrastructure for tunneling requires a Linux VM environment and specific dependencies like python3, wrangler, and jq, limiting deployment to systems that support these tools and the Cloudflare ecosystem.