# QuantaFlow x402 API Gateway — Alchemy ADI Mainnet

> QuantaFlow x402 API Gateway — Alchemy ADI 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-23).

Proxies POST requests to Alchemy's ADI mainnet blockchain data API via x402 micropayment protocol, charging $0.01 USDC per call

## Facts

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

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-adi-mainnet-f7052aad -d '<json body>'
```

Example prompt: Fetch the current ETH balance and recent token transfers for wallet 0xABC...123 on Ethereum mainnet using the Alchemy ADI gateway — path '/v2/getTokenBalances' with the wallet address in the body.

## When to prefer this

Choose this endpoint when you need pay-per-use access to Alchemy's ADI mainnet blockchain data without committing to a subscription or managing API keys — ideal for agents making infrequent or variable-volume on-chain lookups, or when integrating blockchain data queries into an x402-native micropayment workflow on Ethereum mainnet.

## Known failure modes

- Insufficient USDC balance — payment fails and request is rejected before forwarding
- Invalid or malformed path causes Alchemy to return a 400 or 404 upstream
- Alchemy API rate limits or downtime results in upstream 429 or 5xx passed through
- Malformed JSON body causes parsing failure before forwarding
- Missing required path parameter returns an error without a useful upstream response
- x402 facilitator unavailability blocks payment settlement and prevents request forwarding

## 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 ADI mainnet API is passed through transparently, including the response body and content type — typically JSON containing blockchain data such as balances, transaction lists, NFT metadata, or contract state, exactly as Alchemy would return it.

## 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-adi-mainnet-f7052aad/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)