# QuantaFlow x402 API Gateway — Rapid Twitter API v1.1 Enterprise

> QuantaFlow x402 API Gateway — Rapid Twitter API v1.1 Enterprise 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 paid requests to the Rapid Twitter API v1.1 Enterprise endpoint via x402 micropayment protocol, charging $0.01 USDC per call.

## Facts

- Endpoint: POST https://quanta-roan.vercel.app/api/service/rapid-twitter-api-v1-1-enterprise?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-twitter-api-v1-1-enterprise-136a87b3
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_bj-djcrzjpPqGKAuUwsdJ

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-v1-1-enterprise-136a87b3 -d '<json body>'
```

Example prompt: Pull the latest 20 tweets from @elonmusk's timeline using the Twitter v1.1 enterprise endpoint — send a GET to /statuses/user_timeline with screen_name=elonmusk and count=20.

## When to prefer this

Choose this endpoint when you need access to Twitter/X v1.1 Enterprise API data without managing your own Twitter developer credentials, and are comfortable paying $0.01 USDC per request via x402 micropayments. Useful for agents in web3/DeFi workflows that already handle USDC payments natively.

## Known failure modes

- Upstream Twitter API rate limit exceeded — returns 429 from upstream
- Invalid path or unsupported Twitter v1.1 endpoint — returns 404 or upstream error
- Payment failure or insufficient USDC balance — x402 payment rejected before request is forwarded
- Malformed query parameters — upstream returns 400 bad request
- Twitter API authentication error on upstream side — returns 401 or 403 from upstream

## 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 v1.1 Enterprise JSON response is passed through directly — including tweet objects, user objects, metadata, and pagination tokens, 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-api-v1-1-enterprise-136a87b3/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)