# QuantaFlow x402 API Gateway – Alchemy Humanity Mainnet

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

Proxies requests to the Alchemy Humanity mainnet API through an x402 micropayment-gated gateway, charging $0.01 USDC per call

## Facts

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

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-humanity-mainnet-c1de16e8 -d '<json body>'
```

Example prompt: Query the Alchemy Humanity mainnet node to get the latest block number — forward a eth_blockNumber JSON-RPC POST to the root path with an empty params array.

## When to prefer this

Choose this endpoint when you need pay-per-call, no-subscription access to the Alchemy Humanity Protocol mainnet node via the x402 micropayment standard — ideal for AI agents or DeFi workflows that make infrequent or unpredictable bursts of Humanity mainnet RPC calls and want to avoid managing API key subscriptions, paying only $0.01 USDC per request.

## Known failure modes

- Insufficient USDC balance or failed x402 payment results in a 402 Payment Required response before any upstream call is made
- Invalid or malformed JSON-RPC body forwarded to Alchemy may return a JSON-RPC error object from the upstream
- Incorrect path segment causes a 404 or routing error from the upstream Alchemy endpoint
- Alchemy node downtime or rate limiting returns a 5xx error passed through from upstream
- Malformed query parameters may cause unexpected upstream behavior with no gateway-level validation

## How this service works

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

## Output

Returns the raw upstream response body and content type from the Alchemy Humanity mainnet node, passed through transparently after payment is confirmed — typically a JSON-RPC response containing blockchain data such as block numbers, balances, transaction receipts, or contract return values.

## 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-humanity-mainnet-c1de16e8/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)