# QuantaFlow x402 API Gateway – Rapid X/Twitter API Proxy

> QuantaFlow x402 API Gateway – Rapid X/Twitter API Proxy 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-16).

Proxies requests to the Rapid X/Twitter API through an x402 micropayment gateway, charging $0.01 USDC per call

## Facts

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

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-twitter-api-proxy-52dfb858 -d '<json body>'
```

Example prompt: Search the X/Twitter API for the latest tweets mentioning 'Bitcoin' — use the GET search/tweets path with that keyword as the query parameter and pay per call with USDC.

## When to prefer this

Choose this endpoint when you need access to Twitter/X data without managing your own Twitter developer credentials or RapidAPI subscription, and you want to pay per-call in USDC via the x402 protocol. Ideal for web3-native agents that already handle x402 micropayments and need occasional Twitter/X lookups without committing to a monthly API plan.

## Known failure modes

- Payment failure due to insufficient USDC balance — returns 402 Payment Required
- Invalid or malformed path parameter — upstream returns 404 Not Found
- Upstream Twitter/X API rate limit exceeded — returns 429 Too Many Requests
- Invalid query parameters rejected by upstream — returns 400 Bad Request
- Upstream Twitter/X API authentication failure — returns 401 Unauthorized
- Network timeout reaching upstream — returns 504 Gateway Timeout

## 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 from the Rapid X/Twitter API is passed through directly, including the original content type. The agent receives whatever JSON or data the underlying Twitter/X API endpoint returns for the given path and parameters.

## 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-twitter-api-proxy-52dfb858/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)