# httpay.xyz API Gateway: Cloudflare API (PATCH)

> httpay.xyz API Gateway: Cloudflare API (PATCH) is a paid API for AI agents from httpay.xyz, paid per call via x402, $0.002/call, status unknown (last checked 2026-09-12).

Proxies PATCH requests to the Cloudflare API via a pay-per-call x402 gateway, requiring no Cloudflare API key — just USDC micropayment on Base.

## Facts

- Endpoint: POST https://httpay.xyz/api/gateway/cloudflare/%7B*path%7D
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-12
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/httpay-xyz-api-gateway-cloudflare-api-patch-254ed0f3
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ujdywg2otz2JyeT4Te3Hd

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability httpay-xyz-api-gateway-cloudflare-api-patch-254ed0f3 -d '<json body>'
```

Example prompt: Update my Cloudflare DNS record — send a PATCH to the Cloudflare API at zones/{zone_id}/dns_records/{record_id} with the new TTL set to 300, and pay the gateway fee with USDC on Base.

## When to prefer this

Choose this endpoint when you need to perform a PATCH (partial update) on a Cloudflare resource — such as DNS records, zone settings, firewall rules, or workers — and want to avoid managing Cloudflare API keys directly, instead paying per call with USDC via x402 on Base. It is ideal for agents or automation pipelines that need occasional Cloudflare updates without full credential management overhead.

## Known failure modes

- Invalid or malformed Cloudflare API path results in 404 from upstream
- Insufficient USDC balance or missing x402 payment header causes 402 Payment Required
- Cloudflare API rejects the request body with 400 Bad Request if payload is invalid
- Cloudflare rate limiting returns 429 Too Many Requests
- Cloudflare resource not found or wrong zone ID results in upstream 404
- Gateway timeout if Cloudflare API is slow to respond

## How this service works

API Gateway: Cloudflare API

## Output

Returns the raw Cloudflare API response for the PATCH operation — typically the updated resource object (e.g. DNS record, zone setting, firewall rule) with its new state, or an error message if the request failed.

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/httpay-xyz-api-gateway-cloudflare-api-patch-254ed0f3/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from httpay.xyz](https://www.zero.xyz/host/httpay.xyz/llms.txt)