# QuantaFlow x402 API Gateway — Alchemy ETH Mainnet Beacon

> QuantaFlow x402 API Gateway — Alchemy ETH Mainnet Beacon 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-16).

Proxies requests to the Alchemy ETH Mainnet Beacon API endpoint via the x402 micropayment protocol, charging $0.01 USDC per call

## Facts

- Endpoint: POST https://quanta-roan.vercel.app/api/service/alchemy-eth-mainnetbeacon
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/quantaflow-x402-api-gateway-alchemy-eth-mainnet-beacon-9453b723
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_2F9MAQFXkKHpUwM68gB5H

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-eth-mainnet-beacon-9453b723 -d '<json body>'
```

Example prompt: Can you fetch the latest Ethereum beacon chain slot data from the Alchemy mainnet beacon API — use the path /eth/v1/beacon/states/head/validators and pay the per-request fee.

## When to prefer this

Use this endpoint when you need per-call, pay-as-you-go access to the Alchemy ETH Mainnet Beacon API without managing an Alchemy API key directly, and when operating in an x402-compatible agent or wallet context that can handle USDC micropayments on-chain. Prefer this over direct Alchemy API access when you want metered billing at $0.01/call and do not want to commit to a subscription.

## Known failure modes

- Insufficient USDC balance or failed x402 payment causes request to be rejected before forwarding
- Invalid or malformed path results in upstream 404 or 400 from Alchemy
- Alchemy API rate limit or downtime causes upstream 429 or 5xx error
- Malformed query object or body causes gateway parsing error
- Network timeout on the Vercel proxy layer

## How this service works

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

## Output

The raw upstream response body from the Alchemy ETH Mainnet Beacon API, passed through as-is after successful micropayment, including the content type. Typically contains Ethereum beacon chain JSON data such as validator info, slot details, epoch data, or finality checkpoints.

## 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-eth-mainnet-beacon-9453b723/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)