# QuantaFlow x402 Gateway – Twelve Data Financial Markets API

> QuantaFlow x402 Gateway – Twelve Data Financial Markets API 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-20).

Proxies requests to the Twelve Data financial markets API (stock quotes, forex, crypto, indicators) via x402 micropayment protocol at $0.01 USDC per call

## Facts

- Endpoint: POST https://quanta-roan.vercel.app/api/service/twelvedata?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/quantaflow-x402-gateway-twelve-data-financial-markets-api-2ebb4cda
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_GqAi63Cy9DGQgVOjiJLsY

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-gateway-twelve-data-financial-markets-api-2ebb4cda -d '<json body>'
```

Example prompt: Can you pull the latest real-time quote for AAPL and the 14-day RSI from Twelve Data — I want to see if it's overbought right now?

## When to prefer this

Choose this endpoint when you need financial market data (stocks, forex, crypto, technical indicators) and are operating in a web3/x402 micropayment context where you pay per call in USDC. Prefer this over direct Twelve Data API access when you need trustless per-request billing without managing a traditional API subscription key.

## Known failure modes

- Payment failure: insufficient USDC balance causes x402 payment rejection and no data returned
- Invalid path: incorrect Twelve Data API path returns 404 or upstream error
- Rate limit: Twelve Data upstream rate limits may cause 429 errors even after payment
- Invalid ticker: querying a non-existent symbol returns an upstream error message
- Malformed query: missing required Twelve Data parameters (e.g. symbol) causes upstream validation error

## How this service works

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

## Output

The raw upstream response from Twelve Data passed through after successful x402 payment — typically JSON containing financial data such as price quotes, OHLCV time series, technical indicator values, exchange rates, or company metadata depending on the API 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-gateway-twelve-data-financial-markets-api-2ebb4cda/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)