# QuantaFlow x402 API Gateway – Twitter/X API v1.1 & v2 Proxy

> QuantaFlow x402 API Gateway – Twitter/X API v1.1 & v2 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-12).

Proxies requests to the Twitter/X Rapid API (v1.1 and v2) with per-call micropayment via the x402 protocol at $0.01 USDC per request

## Facts

- Endpoint: POST https://quanta-roan.vercel.app/api/service/rapid-twitter-v1-1-v2-api?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-twitter-x-api-v1-1-v2-proxy-1efd5b49
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_IGm753PIoDB5P8DZa7MkC

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-twitter-x-api-v1-1-v2-proxy-1efd5b49 -d '<json body>'
```

Example prompt: Search Twitter for the latest tweets mentioning 'Base blockchain' using the v2 search endpoint, and return the 10 most recent results.

## When to prefer this

Choose this endpoint when you need programmatic access to Twitter/X data (user profiles, tweets, search, timelines) and want to pay per-call with USDC via the x402 micropayment protocol rather than managing Twitter API credentials or a RapidAPI subscription directly. It is ideal for agents that need occasional Twitter lookups without a monthly API subscription commitment.

## Known failure modes

- Invalid or missing path parameter causes upstream routing failure
- Twitter API rate limits exceeded returns a 429 from the upstream provider
- Malformed query parameters result in a Twitter API error response passed through
- Insufficient USDC balance or failed x402 payment causes request to be rejected before forwarding
- Unsupported Twitter API endpoint path may return 404 from upstream
- Twitter API authentication issues on the provider side may return 401/403

## 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) is passed through directly — including tweet objects, user objects, search results, pagination tokens, and metadata fields as returned by the Twitter v1.1 or v2 endpoint specified in the path.

## 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-twitter-x-api-v1-1-v2-proxy-1efd5b49/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)