# httpay.xyz API Gateway: Hugging Face Hub API (PATCH)

> httpay.xyz API Gateway: Hugging Face Hub API (PATCH) is a paid API for AI agents from httpay.xyz, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-15).

Proxies PATCH requests to the Hugging Face Hub API through a pay-per-call x402 payment gateway

## Facts

- Endpoint: POST https://httpay.xyz/api/gateway/huggingface/%7B*path%7D
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/httpay-xyz-api-gateway-hugging-face-hub-api-patch-4c5ad644
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_UA7zDHolCP_OudYtnhm5s

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-hugging-face-hub-api-patch-4c5ad644 -d '<json body>'
```

Example prompt: Update the description metadata on my Hugging Face model repository 'my-org/my-bert-model' by patching its card data to add a new language tag for French.

## When to prefer this

Use this endpoint when an AI agent needs to make PATCH requests to the Hugging Face Hub API without holding a long-lived API key, paying per-call in USDC via x402 micropayments. Ideal for automated MLOps workflows that occasionally update model repos, dataset cards, or space configurations on Hugging Face Hub.

## Known failure modes

- Payment not included or invalid x402 token — gateway rejects with 402 Payment Required
- Invalid or non-existent Hugging Face path — upstream returns 404 Not Found
- Insufficient permissions for the target Hugging Face resource — upstream returns 403 Forbidden
- Malformed request body — upstream returns 400 Bad Request
- Hugging Face Hub API rate limit exceeded — upstream returns 429 Too Many Requests
- Gateway timeout if Hugging Face upstream is slow or unavailable

## How this service works

API Gateway: Hugging Face Hub API

## Output

Returns the Hugging Face Hub API's response to the PATCH operation — typically a JSON object confirming the updated resource state, modified fields, or repository metadata reflecting the applied changes.

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/httpay-xyz-api-gateway-hugging-face-hub-api-patch-4c5ad644/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)