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

> httpay.xyz API Gateway: Supabase 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 Supabase REST API through a pay-per-call x402 payment gateway

## Facts

- Endpoint: POST https://httpay.xyz/api/gateway/supabase/%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-supabase-api-patch-ff28ad1e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_B2sumRrOeDwOvIJdBPiDQ

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-supabase-api-patch-ff28ad1e -d '<json body>'
```

Example prompt: Update the status field to 'completed' for the record with id 42 in my Supabase 'tasks' table using the API gateway at httpay.xyz — patch it via the Supabase REST API path /rest/v1/tasks?id=eq.42.

## When to prefer this

Use this endpoint when you need to send PATCH (partial update) requests to the Supabase REST API via a pay-per-call x402 gateway — ideal for agents that want to update Supabase database records without managing a long-lived API key subscription, paying only per invocation.

## Known failure modes

- Invalid or malformed Supabase API path returns 400 or 404
- Missing or incorrect authentication headers cause 401 Unauthorized from Supabase
- Payment failure or insufficient USDC balance causes x402 payment error
- Supabase row-level security policy blocks the update, returning 403
- No rows match the filter, resulting in an empty or no-op response
- Gateway downtime or timeout causes 502 or 503 error

## How this service works

API Gateway: Supabase API

## Output

The response from the Supabase REST API reflecting the result of the PATCH operation — typically a 200 or 204 with the updated record(s) or an empty body on success, or a Supabase error object on failure.

## More

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