# Apiosk Gateway – Financial Validation Execute

> Apiosk Gateway – Financial Validation 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-13).

Executes a financial validation operation via the Apiosk pay-per-call gateway, forwarding a JSON payload to the financial-validation API and returning the upstream result for $0.05 USDC per call.

## Facts

- Endpoint: POST https://gateway.apiosk.com/financial-validation/execute
- Price: $0.05/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-validation-execute-262ec048
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_zzQzqJ4tCYD_Wdcb1_ODK

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-validation-execute-262ec048 -d '<json body>'
```

Example prompt: Can you run a financial validation check on this data — use the 'validate' operation and pass this JSON payload: {"account_number": "123456789", "routing_number": "021000021"} — and tell me if it passes?

## When to prefer this

Use this endpoint when you need to validate financial data (account numbers, routing numbers, transaction details) via a lightweight pay-per-call model billed in USDC on Base, without setting up a direct integration with a financial data provider. Ideal for agents that need occasional, on-demand financial validation without committing to a subscription, and when the x402 micropayment protocol is already part of the stack.

## Known failure modes

- Invalid operation selector returns an error status with no result body
- Malformed JSON input payload causes upstream rejection and non-200 upstream_status
- Insufficient USDC balance triggers HTTP 402 and payment failure before the call executes
- Upstream financial validation service unavailable returns a gateway-level error
- Unknown operation ID returns a routing error from the gateway

## 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 a status string, the upstream response body (result), the API slug, the operation executed, the cost of the call, the latency in milliseconds, and the HTTP status code returned by the upstream financial validation service.

## 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-validation-execute-262ec048/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)