# QuantaFlow x402 API Gateway – Rapid Twitter Data

> QuantaFlow x402 API Gateway – Rapid Twitter Data 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-18).

Proxies paid requests to a Twitter/social data upstream service via the x402 micropayment protocol, charging $0.01 USDC per call.

## Facts

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

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-data-d3091c4c -d '<json body>'
```

Example prompt: Fetch the latest tweets mentioning 'Ethereum' using the QuantaFlow rapid Twitter data gateway — search path '/search/tweets' with query term 'Ethereum' and return the top results.

## When to prefer this

Choose this endpoint when you need Twitter/social data and want to pay per-call in USDC via x402 micropayments rather than managing API keys or subscriptions. Ideal for AI agents operating in web3/DeFi environments with on-chain payment capabilities, or when you want low-commitment access to Twitter data at $0.01 per request without rate-plan commitments.

## Known failure modes

- Payment failure: insufficient USDC balance or invalid x402 payment header returns 402 Payment Required
- Invalid path: unrecognized upstream path returns 404 or upstream error
- Rate limiting: upstream Twitter data API rate limit exceeded returns 429
- Malformed query: invalid JSON body or query parameters cause upstream 400 error
- Upstream unavailability: Twitter/RapidAPI service outage returns 502 or 503

## 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 Twitter data API, passed through after a successful $0.01 USDC x402 micropayment — typically JSON containing tweet objects, user profiles, search results, or engagement metrics 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-data-d3091c4c/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)