# QuantaFlow x402 API Gateway – TradingView Data

> QuantaFlow x402 API Gateway – TradingView 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-16).

Proxies paid requests to TradingView market data upstream via the x402 micropayment protocol, charging $0.01 USDC per call.

## Facts

- Endpoint: POST https://quanta-roan.vercel.app/api/service/rapid-tradingview-data1?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-tradingview-data-247c0f12
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_HrUnfBiFp9OmLrQZBnHSr

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-tradingview-data-247c0f12 -d '<json body>'
```

Example prompt: Pull the latest OHLCV 1-hour candle data for BTC/USDT from TradingView — I need the last 50 candles to analyze momentum.

## When to prefer this

Choose this endpoint when you need TradingView market data (prices, OHLCV, indicators) on a pay-per-call basis without a TradingView API subscription, and your agent infrastructure supports x402 USDC micropayments. Prefer it over direct TradingView API access when you want metered, no-subscription cost control at $0.01/call.

## Known failure modes

- Payment failure: insufficient USDC balance or wallet not configured for x402 causes 402 Payment Required
- Invalid path: upstream TradingView endpoint not found returns 404 passthrough
- Rate limiting: TradingView upstream throttles the request returning 429
- Malformed query: incorrect path or query parameters yield an upstream error response
- Gateway downtime: Vercel cold-start or deployment outage causes 503

## How this service works

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

## Output

The raw upstream TradingView response body is passed through after successful $0.01 USDC x402 micropayment — typically JSON containing price quotes, OHLCV candles, technical indicator values, or screener results 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-tradingview-data-247c0f12/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)