# QuantaFlow x402 API Gateway – Alchemy Berachain Mainnet

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

Proxies requests to Alchemy's Berachain mainnet RPC/API endpoint via x402 micropayment protocol, charging $0.01 USDC per call

## Facts

- Endpoint: POST https://quanta-roan.vercel.app/api/service/alchemy-berachain-mainnet
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/quantaflow-x402-api-gateway-alchemy-berachain-mainnet-73827eaa
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_rZXbb5kOnn5dc5dxwvTHA

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-berachain-mainnet-73827eaa -d '<json body>'
```

Example prompt: Can you query the latest block number on Berachain mainnet using the Alchemy node — just forward a JSON-RPC eth_blockNumber call and pay the per-request fee automatically?

## When to prefer this

Choose this endpoint when you need pay-per-call access to Alchemy's Berachain mainnet RPC without committing to a subscription, especially in agent workflows that make infrequent or unpredictable numbers of blockchain queries. Ideal for agents that need to read on-chain data, call smart contracts, or inspect transactions on Berachain without managing API keys — payment is handled automatically via x402 USDC micropayments.

## Known failure modes

- Payment failure – insufficient USDC balance causes 402 rejection before request is forwarded
- Invalid path – malformed or unsupported Alchemy API path returns upstream 404 or error
- Malformed JSON body – invalid JSON in body field causes upstream parse error
- Alchemy rate limit or outage – upstream 429 or 5xx passed through from Alchemy
- Network timeout – Berachain mainnet node latency causes gateway timeout

## 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 Alchemy's Berachain mainnet API is passed through as-is, preserving the original response body and content type (typically JSON-RPC results, block data, transaction receipts, or contract call results).

## 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-berachain-mainnet-73827eaa/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)