# QuantaFlow x402 API Gateway – Infura Avalanche Mainnet

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

Proxies JSON-RPC and REST requests to Infura's Avalanche Mainnet node via an x402 pay-per-call gateway, charging $0.01 USDC per request.

## Facts

- Endpoint: POST https://quanta-roan.vercel.app/api/service/infura-avalanche-mainnet
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/quantaflow-x402-api-gateway-infura-avalanche-mainnet-c7c4de2f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_c_XR0GJ-rF0wmt06SFB9J

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-avalanche-mainnet-c7c4de2f -d '<json body>'
```

Example prompt: Can you check the current AVAX balance for wallet address 0xABC123... on Avalanche mainnet using the Infura gateway — just call eth_getBalance at the latest block?

## When to prefer this

Choose this endpoint when you need pay-as-you-go, microtransaction-priced access to Infura's Avalanche Mainnet node without managing an API key subscription. It is ideal for agents that make infrequent or unpredictable calls to Avalanche and want to pay $0.01 USDC per call via the x402 protocol rather than maintaining a monthly Infura plan. Prefer it over direct Infura access when you need x402 payment flow integration in a web3-native agent architecture.

## Known failure modes

- Payment failure: insufficient USDC balance causes 402 response before the upstream call is made
- Invalid JSON-RPC method: upstream returns a JSON-RPC error with code -32601 if the method doesn't exist
- Malformed body: if the forwarded body is not valid JSON, Infura returns a parse error
- Rate limiting: Infura project limits may cause 429 errors if the upstream quota is exceeded
- Network timeout: Avalanche node may be temporarily unreachable, returning a 504 or empty response
- Wrong path: an incorrect path below the origin results in a 404 from the upstream

## 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 Avalanche Mainnet node is passed through verbatim — typically a JSON-RPC response object containing the result field (e.g. balance in hex, block data, transaction receipt) or an error object if the call failed. Content-type mirrors the upstream response.

## 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-avalanche-mainnet-c7c4de2f/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)