# QuantaFlow x402 API Gateway – Alchemy Degen Mainnet

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

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

## Facts

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

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-degen-mainnet-fce2a9de -d '<json body>'
```

Example prompt: Fetch the latest block number on Degen mainnet by hitting the Alchemy Degen endpoint at path /v2/getBlockNumber — pay the $0.01 USDC fee automatically via x402.

## When to prefer this

Choose this endpoint when you need pay-per-use, no-subscription access to Alchemy's Degen L3 mainnet data in an agent or automated workflow that can handle x402 micropayments. Prefer it over self-managed Alchemy API keys for ephemeral or low-volume tasks where a $0.01 per-call USDC cost is acceptable and avoiding key management overhead is valuable.

## Known failure modes

- Payment failure: insufficient USDC balance or invalid x402 payment header returns 402 Payment Required
- Invalid path: unsupported or malformed Alchemy endpoint path returns upstream 404 or error
- Rate limiting: Alchemy upstream may throttle excessive requests
- Malformed body: invalid JSON in the body field causes upstream parse error
- Network timeout: Degen mainnet node latency or Alchemy downtime causes gateway timeout

## 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 Alchemy's Degen mainnet API, passed through after successful x402 micropayment verification — includes blockchain data such as blocks, transactions, balances, contract state, or other Alchemy-supported data, along with the upstream 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-degen-mainnet-fce2a9de/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)