# QuantaFlow x402 API Gateway – Infura zkSync Mainnet

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

Proxies requests to the Infura zkSync Mainnet JSON-RPC API via the x402 micropayment protocol, charging $0.01 USDC per call.

## Facts

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

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-zksync-mainnet-b0309aad -d '<json body>'
```

Example prompt: Check the ETH balance of address 0xAbc123... on zkSync Era mainnet using the Infura RPC — I'm okay paying the per-call fee.

## When to prefer this

Choose this endpoint when you need pay-per-use access to zkSync Era mainnet JSON-RPC without committing to an Infura subscription or managing API keys, and when your agent workflow supports the x402 micropayment protocol for on-demand blockchain queries at $0.01 per call.

## Known failure modes

- Insufficient USDC balance causes payment failure and request rejection
- Invalid or malformed JSON-RPC method returns upstream error from Infura
- Incorrect path parameter causes routing failure to the wrong upstream endpoint
- zkSync mainnet node downtime or Infura outage returns 5xx passthrough error
- Network congestion on zkSync may delay transaction confirmation responses
- Rate limits imposed by Infura upstream can cause throttling errors

## How this service works

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

## Output

The raw upstream Infura zkSync Mainnet JSON-RPC response body is passed through directly after the $0.01 USDC micropayment is settled; this includes standard Ethereum JSON-RPC fields such as result, id, and jsonrpc, containing block data, transaction receipts, account balances, or contract return values depending on the method called.

## 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-zksync-mainnet-b0309aad/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)