# QuantaFlow x402 API Gateway — Alchemy Abstract Mainnet

> QuantaFlow x402 API Gateway — Alchemy Abstract 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-09-15).

Proxies paid API requests to Alchemy's Abstract mainnet blockchain node, charging $0.01 USDC per call via the x402 payment protocol.

## Facts

- Endpoint: POST https://quanta-roan.vercel.app/api/service/alchemy-abstract-mainnet
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/quantaflow-x402-api-gateway-alchemy-abstract-mainnet-69be13fb
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_jBel7v8lGhEHP08LTxso9

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-abstract-mainnet-69be13fb -d '<json body>'
```

Example prompt: Query the Abstract mainnet blockchain via Alchemy — call the eth_getBalance RPC method for address 0xAbC123... using the /v2/{apiKey} path, and pay the $0.01 USDC fee per request.

## When to prefer this

Choose this endpoint when you need pay-per-call access to Alchemy's Abstract mainnet RPC without committing to a subscription plan, and your agent supports the x402 micropayment protocol. Ideal for low-volume or sporadic blockchain queries where per-request $0.01 USDC billing is preferable to a flat subscription, or when building DeFi agents that need on-chain data from the Abstract network specifically.

## Known failure modes

- Insufficient USDC balance causes payment failure and 402 response
- Invalid or missing path parameter causes upstream 404 or routing error
- Malformed JSON body results in upstream RPC error
- Alchemy API key or rate limit exceeded returns upstream 429 or 403
- Unsupported RPC method on Abstract mainnet returns JSON-RPC error
- Network downtime on Vercel or Alchemy causes 502/503

## 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 Abstract mainnet node is passed through directly, including JSON-RPC results such as account balances, block data, transaction receipts, or contract call outputs, along with the appropriate content-type header.

## 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-abstract-mainnet-69be13fb/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)