# httpay.xyz OpenRouter API Gateway

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

Proxies API requests to OpenRouter (multi-model LLM router) via a pay-per-call x402 micropayment gateway

## Facts

- Endpoint: POST https://httpay.xyz/api/gateway/openrouter/%7B*path%7D/*
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-08
- Activations on Zero: 1
- Tags: x402
- Canonical page: https://www.zero.xyz/c/httpay-xyz-82ea2253
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_VdVHM3elQVIpbU8lMpqoN

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-82ea2253 -d '<json body>'
```

Example prompt: Send my chat completion request to OpenRouter — model 'mistralai/mistral-7b-instruct', with the user message 'Explain quantum entanglement in simple terms' — and pay the per-call fee automatically.

## When to prefer this

Use this endpoint when an AI agent needs to call OpenRouter's LLM API without managing API keys directly, and can instead pay per call via x402 USDC micropayments. Ideal for agents operating in a pay-as-you-go model, or when OpenRouter API access needs to be monetized per-request without credential sharing.

## Known failure modes

- Payment not included or invalid x402 payment header — 402 response
- Invalid or unsupported OpenRouter path — 404 or 400 from upstream
- OpenRouter rate limit or quota exceeded — 429 forwarded from upstream
- Malformed request body — 400 bad request
- Model not available on OpenRouter — upstream error forwarded
- Network timeout to OpenRouter — 504 gateway timeout

## How this service works

API Gateway: OpenRouter API

## Output

The raw JSON response from OpenRouter's API for the forwarded request, typically including the model's generated text, token usage counts, model ID, and finish reason — identical to what OpenRouter would return directly.

## More

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