# QuantaFlow x402 API Gateway – Alchemy Boba Mainnet

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

Proxies requests to the Alchemy Boba Mainnet node endpoint via x402 micropayment-gated API gateway, charging $0.01 USDC per call.

## Facts

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

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-boba-mainnet-576d79f0 -d '<json body>'
```

Example prompt: Can you call the Alchemy Boba mainnet RPC and get the latest block number — use eth_blockNumber as the path and a standard JSON-RPC body?

## When to prefer this

Choose this endpoint when you need pay-per-call access to Alchemy's Boba Network mainnet RPC without managing an Alchemy API key subscription. It is ideal for low-frequency or bursty agent workflows querying Boba L2 on-chain data (balances, contract reads, transaction lookups) where micropayment-per-request pricing via x402 is preferable to a monthly plan. Prefer alternatives if you need websocket subscriptions, high-throughput batch calls, or access to Alchemy's enhanced APIs beyond standard JSON-RPC.

## Known failure modes

- Insufficient USDC balance or failed x402 payment — gateway rejects request before forwarding
- Invalid JSON-RPC method or malformed body — Alchemy returns a JSON-RPC error object
- Alchemy node unavailable or rate-limited — upstream 5xx or timeout propagated through
- Incorrect path parameter — request routed to wrong or nonexistent Alchemy endpoint
- Network congestion on Boba mainnet causing slow or dropped responses

## 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 Boba Mainnet RPC node, passed through transparently after the x402 micropayment is settled. Content type mirrors whatever Alchemy returns (typically application/json with a JSON-RPC response envelope containing result or error fields).

## 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-boba-mainnet-576d79f0/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)
