# QuantaFlow x402 API Gateway – rapid-twitter135

> QuantaFlow x402 API Gateway – rapid-twitter135 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).

Acts as a pay-per-call x402 proxy gateway that forwards requests to a rapid-twitter upstream service for web3/DeFi Twitter data tools.

## Facts

- Endpoint: POST https://quanta-roan.vercel.app/api/service/rapid-twitter135?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-rapid-twitter135-59b5b4df
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_h-MZMIylvgwCeTVRFBp59

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-twitter135-59b5b4df -d '<json body>'
```

Example prompt: Pull the latest tweets from @VitalikButerin using the rapid-twitter gateway — I'll pay the $0.01 USDC per-call fee — and give me the last 10 tweets with their engagement stats.

## When to prefer this

Choose this endpoint when you need Twitter/social media data within a web3 or DeFi agent context that already uses x402 micropayment rails, and you want pay-per-call billing in USDC rather than a subscription. Prefer it over direct Twitter API access when your agent infrastructure handles x402 payments natively and you want to avoid managing separate API keys for Twitter/RapidAPI.

## Known failure modes

- Insufficient USDC balance or failed x402 payment results in 402 Payment Required with no upstream call made
- Invalid path or unsupported upstream route returns 404 or upstream error body
- Malformed JSON body causes upstream rejection with 400 Bad Request
- Twitter API rate limits on the upstream RapidAPI key result in 429 Too Many Requests passed through
- Upstream RapidAPI service outage returns 502 or 503 error passthrough

## 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-twitter API is passed through transparently, including tweet objects, user profiles, search results, or other Twitter data, along with the original content-type header. The response mirrors whatever the upstream RapidAPI Twitter endpoint returns after the $0.01 USDC x402 payment is settled.

## 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-twitter135-59b5b4df/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)