# QuantaFlow Rapid Crypto Screener API Gateway

> QuantaFlow Rapid Crypto Screener API Gateway 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 requests to the Rapid Crypto Screener official API through an x402 micropayment gateway, enabling per-call paid access to cryptocurrency screening data.

## Facts

- Endpoint: POST https://quanta-roan.vercel.app/api/service/rapid-crypto-screener-official-api?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-rapid-crypto-screener-api-gateway-fd15fb46
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_TZmYO-Hg7BrggnWd10Rp5

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-rapid-crypto-screener-api-gateway-fd15fb46 -d '<json body>'
```

Example prompt: Pull up the rapid crypto screener data for Bitcoin and Ethereum — I want to see their current screening scores and market metrics.

## When to prefer this

Choose this endpoint when you need pay-per-call access to the Rapid Crypto Screener API without committing to a subscription, or when operating in a web3/crypto-native agent context where x402 USDC micropayments are already supported. Ideal for infrequent or burst queries where per-request $0.01 pricing is more economical than a flat subscription.

## Known failure modes

- Payment failure — insufficient USDC balance or x402 payment not accepted, returns 402 Payment Required
- Upstream API error — the Rapid Crypto Screener service is down or returns an error code
- Invalid path — requested API sub-path does not exist on the upstream service
- Malformed request body — JSON body is invalid or missing required upstream parameters
- Rate limiting — upstream API enforces its own rate limits beyond the payment gateway

## 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 the Rapid Crypto Screener API is passed through after successful $0.01 USDC x402 micropayment — typically JSON containing token screening results, market metrics, rankings, scores, or other cryptocurrency data depending on the query path and parameters supplied.

## 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-rapid-crypto-screener-api-gateway-fd15fb46/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)