# Apiosk Gateway – AssemblyAI Execute

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

Proxies API calls to AssemblyAI (speech-to-text and audio intelligence) through the x402 pay-per-call gateway using USDC on Base for billing.

## Facts

- Endpoint: POST https://gateway.apiosk.com/assemblyai/execute
- Price: $0.14/call
- Payment: x402
- Status: down
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/apiosk-gateway-assemblyai-execute-18a4306c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_pAJGqnJxWzDO7YbiVuR28

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-assemblyai-execute-18a4306c -d '<json body>'
```

Example prompt: Can you transcribe this audio file for me — the URL is https://example.com/meeting.mp3 — using the AssemblyAI transcribe operation and give me back the full text with speaker labels?

## When to prefer this

Choose this endpoint when you need AssemblyAI's speech-to-text or audio intelligence capabilities and want to pay per call in USDC via the x402 protocol without managing an AssemblyAI API key subscription — ideal for agents that process audio intermittently and benefit from usage-based micropayment billing.

## Known failure modes

- Invalid or inaccessible audio URL returns upstream 4xx error in result
- Unsupported audio format causes AssemblyAI rejection
- Insufficient USDC balance or x402 payment failure blocks the request
- Malformed operation selector returns gateway-level error
- Audio file too long or exceeds AssemblyAI limits triggers upstream rejection
- Network timeout to upstream AssemblyAI increases latency or fails

## 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 the upstream AssemblyAI API response body (transcript text, word-level timestamps, speaker diarization, confidence scores, etc.) along with gateway metadata including status, latency, cost, and the operation that was invoked.

## 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-assemblyai-execute-18a4306c/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)