# httpay.xyz API Gateway: Render API

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

Proxies requests to the Render API through an x402-payable gateway, enabling access to Render platform services for a micro-payment per call.

## Facts

- Endpoint: POST https://httpay.xyz/api/gateway/render/%7B*path%7D/*
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/httpay-xyz-98b5e304
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_n0gvfXjWtVCxkW4kR9T9U

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-98b5e304 -d '<json body>'
```

Example prompt: Can you call the Render API to get the status of my deployed service — route the request through the x402 gateway at the /services endpoint path?

## When to prefer this

Use this endpoint when you need to access the Render cloud platform API through a pay-per-call x402 micropayment model rather than managing Render API credentials directly. Ideal for agents that need occasional Render API access without a standing API key, or in x402-native agentic workflows where USDC micropayments are the preferred auth mechanism.

## Known failure modes

- Invalid or unrecognized Render API path returns 404 or error response
- Insufficient USDC balance causes x402 payment failure
- Render API upstream error returns 500 or 503
- Malformed request body causes 400 bad request
- Unauthorized access if Render API path requires authentication not provided
- Path wildcard not matched returns gateway routing error

## How this service works

API Gateway: Render API

## Output

The raw JSON response from the Render API, forwarded through the httpay.xyz gateway, containing whatever data the specified Render API path returns (e.g. deployment status, service info, logs).

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/httpay-xyz-98b5e304/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)