# QuantaFlow x402 API Gateway — Alchemy Tempo Mainnet

> QuantaFlow x402 API Gateway — Alchemy Tempo 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 Tempo mainnet endpoint using the x402 micropayment protocol, deducting $0.01 USDC per call.

## Facts

- Endpoint: POST https://quanta-roan.vercel.app/api/service/alchemy-tempo-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-tempo-mainnet-1688de3e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_IfhUzLEu9n6le5goXTXT9

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-tempo-mainnet-1688de3e -d '<json body>'
```

Example prompt: Can you fetch the latest Ethereum mainnet block number from Alchemy Tempo by forwarding a JSON-RPC eth_blockNumber request to the /eth-mainnet path, paying $0.01 USDC per call?

## When to prefer this

Choose this endpoint when you need on-demand, pay-per-call access to the Alchemy Tempo Ethereum mainnet API without committing to a subscription — ideal for low-frequency or bursty agent workflows that query on-chain data and want per-request USDC billing via the x402 protocol rather than managing API keys.

## Known failure modes

- Insufficient USDC balance or missing x402 payment header causes 402 Payment Required
- Invalid or malformed path/method results in upstream 400 or 404 from Alchemy
- Alchemy Tempo mainnet rate limit or downtime returns 503 or 500 pass-through
- Malformed JSON body causes upstream parse error
- Network timeout on Vercel edge layer returns 504

## 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 Tempo mainnet is passed through — typically a JSON-RPC result object containing the requested on-chain data (block info, balances, transaction receipts, logs, etc.) along with the original content type.

## 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-tempo-mainnet-1688de3e/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)