# Apiosk Gateway – Twelve Data Execute

> Apiosk Gateway – Twelve Data Execute is a paid API for AI agents from gateway.apiosk.com, paid per call via x402, $0.05/call, status unknown (last checked 2026-09-15).

Executes a pay-per-call request to the Twelve Data financial market data API via the x402 USDC micropayment gateway

## Facts

- Endpoint: POST https://gateway.apiosk.com/twelve-data/execute
- Price: $0.05/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/apiosk-gateway-twelve-data-execute-9f0cb76f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_uNWInVzI6eEoKbb-W8spo

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 apiosk-gateway-twelve-data-execute-9f0cb76f -d '<json body>'
```

Example prompt: Fetch the latest daily OHLC candlestick data for AAPL stock from Twelve Data — use the time_series operation with symbol AAPL, interval 1day, and outputsize 30.

## When to prefer this

Choose this endpoint when you need on-demand access to Twelve Data financial market data (stocks, forex, crypto, indicators) without a direct Twelve Data subscription, and you want to pay $0.05 USDC per call via the x402 micropayment protocol. Ideal for agents that infrequently need market data and want pay-as-you-go pricing rather than a monthly subscription.

## Known failure modes

- Invalid or unknown operation selector returns error status
- Malformed JSON payload causes upstream 4xx response
- Insufficient USDC balance or failed x402 payment results in 402 response
- Rate limit or authentication failure at Twelve Data upstream returns 429 or 401 in upstream_status
- Unsupported financial symbol or interval returns error from upstream

## How this service works

Pay-per-call API gateway on the x402 protocol (HTTP 402 + USDC on Base). This document covers the gateway's discovery and execution meta-endpoints. Individual provider APIs are reachable at /{api_slug}/{path} and described by GET /{api_slug}/metadata.

## Output

Returns a JSON object containing status, the upstream Twelve Data API response body under 'result', the operation used, latency in milliseconds, cost string, and the upstream HTTP status code.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "input": {
   "type": "string",
   "description": "JSON payload forwarded to the selected operation."
  },
  "operation": {
   "type": "string",
   "description": "Operation id, /path, or METHOD /path selector."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "status",
  "result"
 ],
 "properties": {
  "api": {
   "type": "string"
  },
  "cost": {
   "type": "string"
  },
  "result": {
   "description": "Upstream response body."
  },
  "status": {
   "type": "string"
  },
  "latency": {
   "type": "number"
  },
  "operation": {
   "type": "string"
  },
  "upstream_status": {
   "type": "integer"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/apiosk-gateway-twelve-data-execute-9f0cb76f/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from gateway.apiosk.com](https://www.zero.xyz/host/gateway.apiosk.com/llms.txt)