# QuantaFlow x402 API Gateway - Twitter/Rapid Endpoint

> QuantaFlow x402 API Gateway - Twitter/Rapid Endpoint 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-Twitter upstream API endpoint via x402 micropayment protocol, charging $0.01 USDC per call

## Facts

- Endpoint: POST https://quanta-roan.vercel.app/api/service/rapid-twitter293?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-rapid-endpoint-baf1cbb7
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_xrGuDjbWEf3pPLL-d9ShW

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-rapid-endpoint-baf1cbb7 -d '<json body>'
```

Example prompt: Fetch the latest tweets for user @elonmusk using the QuantaFlow rapid-Twitter gateway — use the path '/tweets' with a query for the user handle and pay $0.01 USDC per call via x402.

## When to prefer this

Choose this endpoint when you need Twitter/X data access on a pay-per-use basis without committing to a subscription, particularly in web3 or DeFi agent workflows that already handle USDC micropayments via the x402 protocol. It is well-suited for low-frequency or bursty Twitter data needs where per-call billing is more economical than a flat API plan.

## Known failure modes

- Insufficient USDC balance causes x402 payment failure and request rejection
- Invalid or missing path parameter results in upstream 404 or routing error
- Upstream RapidAPI rate limits exceeded returns 429 error passed through
- Malformed query object causes upstream API to return validation error
- Network timeout from upstream Twitter data provider results in 5xx passthrough
- Invalid method or body format may cause upstream rejection

## How this service works

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

## Output

The raw upstream Twitter/Rapid API response body is passed through after the x402 payment is verified, along with the content type. The agent receives whatever JSON or data the underlying Twitter data provider returns for the requested path and query.

## 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-rapid-endpoint-baf1cbb7/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)