# QuantaFlow x402 API Gateway — rapid-x-com2

> QuantaFlow x402 API Gateway — rapid-x-com2 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-12).

Proxies HTTP requests to the rapid-x-com2 upstream web3/DeFi service endpoint via the x402 micropayment protocol, charging $0.01 USDC per call.

## Facts

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

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-rapid-x-com2-a11beec0 -d '<json body>'
```

Example prompt: Call the rapid-x-com2 service through QuantaFlow using a GET to /price with query params {symbol: 'ETH'} — pay the $0.01 USDC fee and return me the upstream response.

## When to prefer this

Choose this endpoint when you need pay-per-call access to the rapid-x-com2 web3/DeFi upstream service via x402 micropayments and want to avoid subscription commitments. Ideal for agents that make infrequent or variable-volume calls to crypto/DeFi data tools and need on-chain-verifiable payment semantics.

## Known failure modes

- Payment failure: insufficient USDC balance or wallet not configured for x402 causes 402 Payment Required response
- Invalid path: upstream returns 404 if the specified path does not exist on rapid-x-com2
- Upstream error: upstream service outage or timeout passes through as 5xx error
- Malformed query/body: upstream may return 400 if JSON body or query params are invalid
- Rate limiting: upstream may impose its own rate limits independent of payment

## 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 and content-type from the rapid-x-com2 service, passed through transparently after the $0.01 USDC x402 payment is validated. The agent receives whatever the upstream API returns — JSON, text, or other content — without transformation.

## 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-rapid-x-com2-a11beec0/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)