# QuantaFlow x402 API Gateway – Alchemy Pharos Mainnet

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

Proxies paid API requests to the Alchemy Pharos mainnet node via the x402 micropayment protocol, charging $0.01 USDC per call.

## Facts

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

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-pharos-mainnet-ef905639 -d '<json body>'
```

Example prompt: Hit the Alchemy Pharos mainnet RPC to fetch the latest block number — forward a POST to the root path with body '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}' and pay the $0.01 USDC fee via x402.

## When to prefer this

Choose this endpoint when you need pay-as-you-go access to Alchemy's Pharos mainnet RPC without committing to a subscription or API key plan. Ideal for agents that make sporadic on-chain queries, want micropayment-based billing via USDC, or are operating in a web3-native x402 payment context. Prefer this over direct Alchemy subscriptions when the use case is low-volume, automated, or requires programmatic per-call payment settlement.

## Known failure modes

- Payment failure or insufficient USDC balance — gateway rejects with 402 Payment Required
- Invalid or malformed x402 payment header — request blocked before reaching upstream
- Upstream Alchemy Pharos endpoint error — non-2xx status passed through from origin
- Invalid JSON-RPC body — Alchemy returns a JSON-RPC error object
- Rate limiting or node unavailability on Alchemy side — 503 or timeout
- Incorrect path parameter — request routed to wrong upstream endpoint

## 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 and content-type from the Alchemy Pharos mainnet API, passed through transparently after successful x402 micropayment verification. The agent receives whatever JSON-RPC or REST response the underlying Alchemy endpoint returns.

## 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-pharos-mainnet-ef905639/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)