# QuantaFlow x402 API Gateway – OpenAI Proxy

> QuantaFlow x402 API Gateway – OpenAI Proxy is a paid API for AI agents from quanta-roan.vercel.app, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-22).

Proxies requests to OpenAI's API via the x402 micropayment protocol, charging $0.01 USDC per call

## Facts

- Endpoint: POST https://quanta-roan.vercel.app/api/service/openai?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-22
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/quantaflow-x402-api-gateway-openai-proxy-f106b66c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_fPXEIDQhRrfZhSbkKjIFA

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 quantaflow-x402-api-gateway-openai-proxy-f106b66c -d '<json body>'
```

Example prompt: Forward a chat completions request to OpenAI through QuantaFlow — send a POST to /v1/chat/completions with the body '{"model":"gpt-4o-mini","messages":[{"role":"user","content":"Hello!"}]}' and pay the $0.01 USDC x402 fee.

## When to prefer this

Choose this endpoint when you need pay-per-request access to OpenAI's API using USDC micropayments via the x402 protocol — ideal for crypto-native agents, DeFi workflows, or scenarios where you want to avoid a traditional OpenAI subscription and instead pay $0.01 per call from a web3 wallet. Prefer alternatives (direct OpenAI API) when you need higher throughput, lower latency, or access to OpenAI features beyond what a transparent proxy exposes.

## Known failure modes

- Payment verification failure: insufficient USDC balance or invalid x402 payment header returns 402 Payment Required
- Invalid path: if the specified path does not match a valid OpenAI endpoint, returns upstream 404 or 400
- Malformed body: non-JSON string in body field causes upstream parse error
- OpenAI API errors (rate limits, invalid model names) are passed through as-is from upstream
- Network/gateway timeout: Vercel function timeout if upstream OpenAI is slow

## How this service works

Every request, a quantum of value. x402 protocol-based payment endpoint for web3/DeFi tools.

## Output

The raw upstream OpenAI response body (e.g. chat completion JSON, embeddings array, model output) is passed through transparently along with the original content type, after the x402 payment is verified and settled.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "body": {
   "type": "string",
   "description": "Optional JSON body forwarded to POST requests."
  },
  "path": {
   "type": "string",
   "description": "Path below the selected upstream origin."
  },
  "query": {
   "type": "object"
  },
  "method": {
   "enum": [
    "GET",
    "POST"
   ],
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "description": "The upstream response body and content type are passed through after successful payment."
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/quantaflow-x402-api-gateway-openai-proxy-f106b66c/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from quanta-roan.vercel.app](https://www.zero.xyz/host/quanta-roan.vercel.app/llms.txt)