# Apiosk Gateway – Finnhub Execute

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

Executes a Finnhub financial data API operation via the x402 pay-per-call gateway, forwarding JSON payloads and returning the upstream response for $0.12 USDC per call.

## Facts

- Endpoint: POST https://gateway.apiosk.com/finnhub/execute
- Price: $0.12/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-finnhub-execute-51dc3215
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap__y-u8DmyttUS5US_1T2ix

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-finnhub-execute-51dc3215 -d '<json body>'
```

Example prompt: Pull the latest stock quote and company profile for AAPL from Finnhub — use the GET /quote operation with the AAPL ticker as the JSON payload.

## When to prefer this

Choose this endpoint when you need programmatic access to Finnhub's financial data (quotes, earnings, news, fundamentals) without managing your own Finnhub API key, and you prefer pay-per-call USDC micropayments over subscription billing. Ideal for agents that need occasional or burst financial data lookups without committing to a recurring subscription.

## Known failure modes

- Invalid operation id returns error status with no result
- Malformed JSON input payload causes upstream rejection
- Unsupported Finnhub endpoint path returns 404 upstream_status
- Insufficient USDC balance on x402 protocol causes 402 payment failure
- Rate limiting by Finnhub upstream returns 429 upstream_status

## 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 with status, the upstream Finnhub response body under 'result', the operation name, api name, latency in milliseconds, cost as a 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-finnhub-execute-51dc3215/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)