# QuantaFlow x402 API Gateway – Rapid Twitter API

> QuantaFlow x402 API Gateway – Rapid Twitter API 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-10).

Proxies requests to a Twitter/social data upstream API via the x402 micropayment protocol, charging $0.01 USDC per call.

## Facts

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

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-api-5ffe6b72 -d '<json body>'
```

Example prompt: Search Twitter for recent tweets mentioning 'Bitcoin ETF' and return the top 10 results with their engagement stats — use the rapid-twitter-api47 path with a GET method and query set to {q: 'Bitcoin ETF', count: 10}.

## When to prefer this

Choose this endpoint when you need programmatic access to Twitter/X data (tweets, profiles, search) without managing your own Twitter API credentials, and you prefer pay-per-call micropayment billing via the x402 protocol (USDC on-chain) rather than a subscription. Ideal for agents operating in web3/DeFi contexts that already handle x402 payments.

## Known failure modes

- Payment failure: insufficient USDC balance or x402 payment header missing — returns 402 Payment Required
- Invalid path: unrecognized upstream API path returns 404 or upstream error
- Twitter API rate limit exceeded upstream: upstream returns 429 Too Many Requests
- Malformed query parameters: upstream rejects badly structured query and returns 400
- Upstream Twitter API downtime: gateway passes through 5xx error from upstream
- Invalid method: POST-only gateway may reject non-POST calls

## How this service works

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

## Output

The raw upstream Twitter API response body (JSON) with tweet data, user profiles, search results, or other social content, passed through transparently after successful x402 micropayment authorization. Content-type header is also forwarded.

## 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-api-5ffe6b72/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)