# QuantaFlow Rapid Botometer Pro Gateway

> QuantaFlow Rapid Botometer Pro 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-12).

Proxies requests to the Rapid Botometer Pro bot-detection API via x402 micropayment protocol, charging $0.01 USDC per call

## Facts

- Endpoint: POST https://quanta-roan.vercel.app/api/service/rapid-botometer-pro?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-rapid-botometer-pro-gateway-9460f4ff
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_YyW7cR3wl4T5GyZpGYh48

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-botometer-pro-gateway-9460f4ff -d '<json body>'
```

Example prompt: Check whether the Twitter account @elonmusk is a bot using Botometer Pro and give me a bot score.

## When to prefer this

Choose this endpoint when you need per-call, pay-as-you-go bot detection without a subscription to RapidAPI or Botometer Pro directly, especially in web3/agent contexts where x402 USDC micropayments are already supported. Ideal for low-volume or sporadic checks where a monthly subscription is overkill, or for AI agents that need to autonomously pay for bot detection inline within a workflow.

## Known failure modes

- Insufficient USDC balance causes payment failure and request is rejected before forwarding
- Invalid or non-existent Twitter handle returns an upstream 404 or error from Botometer Pro
- Malformed JSON body results in upstream API error
- Rate limits on the underlying RapidAPI Botometer Pro tier cause 429 responses
- Upstream Botometer Pro service downtime results in 502 or timeout errors
- Missing required path or query parameters may cause unexpected upstream behavior

## How this service works

Every request, a quantum of value. x402 protocol-based payment endpoint for web3/DeFi tools.

## Output

The upstream Botometer Pro API response passed through directly, typically including a bot score (0–5 scale), CAP (complete automation probability), and sub-scores for language, sentiment, network, and temporal features of the queried Twitter account.

## 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-botometer-pro-gateway-9460f4ff/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)