# Apiosk Gateway – Financial Identifiers Execute

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

Executes a financial-identifiers API operation via the Apiosk x402 pay-per-call gateway, returning structured financial identifier data for a given input.

## Facts

- Endpoint: POST https://gateway.apiosk.com/financial-identifiers/execute
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/apiosk-gateway-financial-identifiers-execute-7fff1bb7
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ApaVxx1iD183nxTxCkDww

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-financial-identifiers-execute-7fff1bb7 -d '<json body>'
```

Example prompt: Can you look up the ISIN and LEI for Apple Inc. using the financial-identifiers operation on Apiosk — I need to cross-reference it with another dataset?

## When to prefer this

Choose this endpoint when you need to resolve, validate, or cross-reference standard financial identifiers (ISIN, CUSIP, LEI, ticker) in a pay-per-call model without a subscription. Ideal for agents that need occasional identifier lookups billed in USDC micro-payments via the x402 protocol, avoiding monthly API key overhead.

## Known failure modes

- Invalid or unrecognized operation selector returns an error status
- Malformed JSON in the input field causes upstream rejection
- Unknown or unsupported financial identifier format returns empty or null result
- x402 payment failure (insufficient USDC balance) blocks the call
- Upstream financial-identifiers provider downtime returns non-200 upstream_status
- Rate limiting or quota exhaustion from the upstream provider

## 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 (success/failure), the upstream financial identifier data as the result field, the operation and API name echoed back, cost in USDC, latency in milliseconds, 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-financial-identifiers-execute-7fff1bb7/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)