Use the static IP for:

Example AWS Security Group rule:

Type: HTTPS | Source: 198.51.100.45/32

Let’s state this clearly. There is no setting, toggle, or configuration within the consumer version of Cloudflare WARP (free, WARP+, or even the paid Teams plan at the basic level) that provides a static egress IP.

Why? Two reasons: Economics and Architecture.

Run a cheap Virtual Private Server (VPS) with a static IP (e.g., DigitalOcean, Vultr, AWS Lightsail for $5/month). On that VPS, install a SOCKS5 proxy or a simple Nginx reverse proxy. On your local machine, connect to Cloudflare WARP for privacy, then route specific traffic (e.g., your curl commands) through the VPS’s static IP using proxychains.

Are you an individual developer or small business owner who needs a reliable egress IP while using WARP? You have two practical options, though neither is pure Cloudflare WARP.