# QuantaFlow x402 API Gateway – Rapid Twitter AIO

> QuantaFlow x402 API Gateway – Rapid Twitter AIO 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 a Rapid API-backed Twitter all-in-one service via x402 micropayment protocol, charging $0.01 USDC per call.

## Facts

- Endpoint: POST https://quanta-roan.vercel.app/api/service/rapid-twitter-aio?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-twitter-aio-f7601c1a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Dqw9ynheV6Y_Uiidgz3s_

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-twitter-aio-f7601c1a -d '<json body>'
```

Example prompt: Search Twitter for the latest tweets mentioning 'Bitcoin ETF' from the past 24 hours and give me the top 10 results with engagement stats.

## When to prefer this

Choose this endpoint when you need Twitter/X data (user profiles, tweets, search results, timelines) and prefer pay-per-use micropayment billing over a monthly RapidAPI subscription or direct Twitter API credentials. Ideal for agents making infrequent or bursty Twitter queries that don't justify a standing API plan.

## Known failure modes

- Payment failure: insufficient USDC balance or x402 payment not accepted — returns 402 Payment Required
- Invalid path: unrecognized API path below the upstream origin returns 404 or upstream error
- Rate limiting: upstream RapidAPI quota exceeded returns 429
- Malformed query: missing or invalid query parameters returns 400 from upstream
- Upstream unavailability: RapidAPI or Twitter service downtime returns 502 or 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 from the Twitter AIO API, passed through after successful x402 micropayment — typically JSON containing tweet objects, user profiles, timelines, or search results depending on the path queried.

## 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-twitter-aio-f7601c1a/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)