# QuantaFlow x402 API Gateway – Infura Mainnet Proxy

> QuantaFlow x402 API Gateway – Infura 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-12).

Proxies requests to Infura's Ethereum mainnet JSON-RPC endpoint via the x402 micropayment protocol, charging $0.01 USDC per call.

## Facts

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

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-infura-mainnet-proxy-6751cc22 -d '<json body>'
```

Example prompt: Query the Ethereum mainnet through the QuantaFlow gateway — call eth_getBalance for address 0xAbC123... on the latest block and pay the $0.01 USDC fee automatically.

## When to prefer this

Use this endpoint when you need pay-per-call access to Infura's Ethereum mainnet JSON-RPC without committing to a monthly subscription, and your agent stack already supports the x402 micropayment protocol. Ideal for low-frequency or bursty on-chain queries where per-call billing is more economical than a flat subscription.

## Known failure modes

- Payment failure: insufficient USDC balance or x402 payment not accepted — gateway returns 402 Payment Required
- Invalid JSON-RPC method or params: Infura returns a JSON-RPC error object with code and message
- Network or upstream error: Infura mainnet temporarily unavailable — 502 or 504 from the gateway
- Malformed request body: non-JSON or missing required fields returns a 400 error
- Rate limiting by upstream Infura even after payment — rare but possible under high load

## How this service works

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

## Output

The raw upstream response from Infura's Ethereum mainnet JSON-RPC API is passed through directly, including the JSON-RPC result or error object, HTTP status, and content-type headers, after the x402 micropayment of $0.01 USDC is 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-infura-mainnet-proxy-6751cc22/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)