cliproxyapi-cloudflare-stack

Deploy CLIProxyAPI via the deploy_vm.sh script, which installs Docker, pulls the gateway image, generates an sk- API key, and starts the service on port 5000. Then expose it with a Cloudflare tunnel pointing to localhost:5000.

Place one JSON credential file per account in the auth directory with provider, api_key, and status fields. CLIProxyAPI hot-reloads every 30 seconds and routes requests by model prefix, automatically trying the next credential when one is rate limited.

Yes, the gateway exposes a standard /v1 endpoint compatible with the OpenAI SDK. Set base_url to your tunnel domain and api_key to the gateway's sk- token, then call chat.completions normally, including streaming.

Deploy the included Cloudflare Worker with a D1 database binding, then configure Email Routing with a catch-all rule pointing to the worker. Incoming verification codes are stored in D1 and queryable via wrangler d1 execute.

A 502 means the CLIProxyAPI container is down or has no active credentials. Check docker ps and docker logs for the gateway, verify JSON files exist in /opt/cpa/auth with status active, then restart the container.

All pooled credentials share provider rate limits, so exhausting every account still causes failures until limits reset. You must also keep credential JSON files valid and secure, since expired keys require manual updates.