# QuantaFlow x402 API Gateway – Alchemy zkSync Mainnet

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

Proxies requests to the Alchemy zkSync Mainnet RPC/API with per-call micropayment settlement via the x402 protocol

## Facts

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

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

Example prompt: Call the Alchemy zkSync mainnet API to get the current ETH balance for address 0xAbCd...1234 — use the eth_getBalance JSON-RPC method and pay the $0.01 USDC fee per call.

## When to prefer this

Choose this endpoint when you need pay-per-use, no-subscription access to Alchemy's zkSync Mainnet APIs (RPC, enhanced APIs, NFT data, etc.) and want to settle costs via x402 USDC micropayments rather than managing an Alchemy API key subscription. Ideal for agents that make infrequent or unpredictable zkSync calls and prefer on-chain payment over OAuth/API-key auth.

## Known failure modes

- Payment failure: insufficient USDC balance or invalid x402 payment header results in 402 Payment Required
- Invalid path: unrecognized path below the upstream origin returns an upstream 404 or gateway error
- Malformed body: invalid JSON body forwarded to a POST endpoint may return Alchemy 400 Bad Request
- Rate limiting: Alchemy upstream may throttle or reject requests returning 429
- Network error: zkSync mainnet RPC node unavailability may cause 503 or timeout

## How this service works

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

## Output

The raw upstream Alchemy zkSync Mainnet API response body (JSON-RPC result, token data, transaction info, etc.) and its content type are passed through transparently after the x402 micropayment is settled. The agent receives exactly what Alchemy would return directly.

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