# QuantaFlow x402 API Gateway – Infura Hemi Mainnet

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

Proxies requests to the Infura Hemi Mainnet blockchain RPC endpoint via x402 pay-per-call micropayment protocol at $0.01 USDC per request

## Facts

- Endpoint: POST https://quanta-roan.vercel.app/api/service/infura-hemi-mainnet?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/quantaflow-x402-api-gateway-infura-hemi-mainnet-29d80d46
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_-5PCuWl-mMwqjs02fW4-F

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-hemi-mainnet-29d80d46 -d '<json body>'
```

Example prompt: Query the Hemi mainnet to get the current block number — use the Infura RPC path /eth_blockNumber and forward it through the QuantaFlow gateway.

## When to prefer this

Choose this endpoint when you need pay-per-call access to Hemi Mainnet via Infura without committing to a subscription API key, especially in agent workflows that make sporadic RPC calls and benefit from x402 micropayment billing at $0.01 USDC per request. Prefer this over direct Infura subscriptions for low-volume or cost-sensitive agent pipelines targeting the Hemi network specifically.

## Known failure modes

- Payment failure: insufficient USDC balance causes 402 Payment Required before request is forwarded
- Invalid path: malformed or unsupported RPC path returns upstream error
- Upstream unavailability: Infura Hemi Mainnet outage returns 502 or 503
- Malformed JSON body: invalid request body causes RPC error from upstream
- Rate limiting: excessive calls may trigger upstream Infura rate limits

## How this service works

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

## Output

The raw upstream Infura Hemi Mainnet RPC response body is passed through as-is, including the content type. Typically a JSON-RPC result object containing blockchain data such as block numbers, balances, transaction receipts, or contract return values.

## 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-hemi-mainnet-29d80d46/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)