# QuantaFlow x402 API Gateway – Alchemy Hyperliquid Mainnet Proxy

> QuantaFlow x402 API Gateway – Alchemy Hyperliquid Mainnet 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-11).

Proxies HTTP requests to Alchemy's Hyperliquid mainnet RPC/API endpoint via the x402 pay-per-call protocol, charging $0.01 USDC per request.

## Facts

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

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-alchemy-hyperliquid-mainnet-proxy-382246d1 -d '<json body>'
```

Example prompt: Fetch the current order book for BTC-USDC perpetuals on Hyperliquid mainnet using the Alchemy gateway — use the /info path with a POST body asking for the L2Book snapshot.

## When to prefer this

Choose this endpoint when you need pay-per-call access to Alchemy's Hyperliquid mainnet API without committing to a monthly subscription or managing API keys, especially in agentic or automated workflows that use the x402 micropayment protocol with USDC on Base or another supported chain.

## Known failure modes

- Payment failure: insufficient USDC balance or x402 payment header missing/invalid returns 402 Payment Required
- Invalid path: unrecognized or malformed path below the upstream origin returns upstream 404 or error
- Upstream error: Alchemy or Hyperliquid mainnet outage propagates as upstream error response
- Malformed JSON body: invalid JSON in body field causes upstream rejection
- Rate limit: upstream Alchemy rate limits may apply beyond the payment gateway layer

## How this service works

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

## Output

The raw upstream response body from Alchemy's Hyperliquid mainnet API is passed through with its original content type, after the x402 micropayment of $0.01 USDC is settled. This includes RPC results, market data, account state, or any other data the upstream Hyperliquid endpoint returns.

## 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-alchemy-hyperliquid-mainnet-proxy-382246d1/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)