Cloudflare Pages

Cloudflare Pages serves static assets and Pages Functions (Cloudflare Workers) from Cloudflare's global edge — 300+ PoPs with no cold-start overhead for server-side logic. Git-based deployments: push to main → automatic build → global deployment in under 60 seconds. Preview deployments: every PR gets a unique URL. Pages Functions (file-based routing in /functions directory) enable SSR and API routes with Worker capabilities (KV, D1, R2, AI bindings). For agents: the REST API manages deployments, projects, and custom domains. Free tier is generous (unlimited static requests, 500 builds/month). Strong for Next.js, Astro, SvelteKit, and static sites. Confidence is docs-derived.

REST API at api.cloudflare.com/client/v4/accounts/{account_id}/pages. Resources: projects, deployments. GET /projects lists all Pages projects. POST /projects creates a project (name, production_branch, build_config). GET /projects/{name} retrieves project details. GET /projects/{name}/deployments lists deployments with status. POST /projects/{name}/deployments triggers a deployment (from latest commit or file upload). GET /projects/{name}/deployments/{id} retrieves deployment status (idle, active, success, failure). DELETE /projects/{name}/deployments/{id} deletes a deployment. Wrangler CLI: wrangler pages dev (local dev), wrangler pages deploy (direct deploy from build output).

API token auth: Authorization: Bearer {api_token}. Token from Cloudflare Dashboard → My Profile → API Tokens (scope: Cloudflare Pages: Edit). Account ID + project name in URL path. HTTPS enforced. No OAuth2. Git integration: Cloudflare GitHub App / GitLab OAuth for auto-deploy. Pages Functions environment variables: set per-project in Dashboard or API (plaintext and secret). Production vs. preview environment variable separation.

Standard HTTP status codes with JSON response ({success, result, errors}). Deployment status: idle → active → success/failure. Build failures: logs accessible via Dashboard. Build timeout: 20 minutes (configurable for paid plans). Free tier: 500 builds/month (consider build frequency). Pages Functions: same reliability as Cloudflare Workers (99.99%+ uptime, zero cold-start). CDN cache: automatic invalidation on deployment. Cloudflare Pages uptime is tied to Cloudflare global network. Custom domain: DNS propagation may take up to 24 hours on initial setup.

developers.cloudflare.com/pages covers project creation, Git integration, build configuration, Pages Functions guide, environment variables, custom domains, and REST API reference. Getting started: connect GitHub/GitLab, create Pages project, first deployment in under 5 minutes (Wrangler CLI) or via Dashboard. Wrangler v3 (wrangler pages dev) provides local Pages Functions development with Worker bindings (KV, D1, R2). Community via Cloudflare Discord (Pages channel) and Cloudflare Community Forums. Free tier and zero cold-start make Pages very attractive for developer tooling deployments.