# Runx Marketplace – Ausca Async AWS Transcribe

> Runx Marketplace – Ausca Async AWS Transcribe is a paid API for AI agents from api.runx.ai, paid per call via x402, $0.05/call, status unknown (last checked 2026-09-14).

Submits an audio or video file for asynchronous speech-to-text transcription via AWS Transcribe, purchased through the Runx marketplace at a metered per-call price.

## Facts

- Endpoint: POST https://api.runx.ai/v1/skills/ausca/media-transcription/run
- Price: $0.05/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/runx-marketplace-ausca-async-aws-transcribe-1b3df607
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Mp6tJFozwir7dJTbBiZ29

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 runx-marketplace-ausca-async-aws-transcribe-1b3df607 -d '<json body>'
```

Example prompt: Can you transcribe this audio recording for me? Submit it to the Runx Ausca transcription service asynchronously and return the full text once it's done — use idempotency key 'meeting-2024-06-01' so we don't double-submit.

## When to prefer this

Choose this endpoint when you need asynchronous, cost-metered speech-to-text transcription powered by AWS Transcribe, purchased through the Runx marketplace with per-call USDC billing via the x402 protocol. Prefer it over synchronous alternatives when processing longer audio/video files where a blocking call would be impractical. It is especially suitable for pipelines that can accept a job-submission model and poll for results.

## Known failure modes

- Invalid or inaccessible media file URL — 400 or processing error
- Idempotency key reuse with conflicting inputs — may return cached result or error
- Payment failure via x402 protocol — 402 response blocking execution
- Unsupported audio/video format not accepted by AWS Transcribe
- Job timeout or async result not yet available — may need polling
- Rate limiting or quota exhaustion on the underlying AWS Transcribe service

## How this service works

Buy Ausca asynchronous AWS Transcribe through one measured Runx marketplace listing.

## Output

Returns a job confirmation or transcript output from AWS Transcribe, delivered asynchronously. The agent receives a response indicating the transcription job was accepted or completed, with the resulting text extracted from the audio/video input.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "inputs": {
   "type": "object",
   "additionalProperties": true
  },
  "runner": {
   "type": "string",
   "const": "invoke"
  },
  "idempotency_key": {
   "type": "string",
   "minLength": 1
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/runx-marketplace-ausca-async-aws-transcribe-1b3df607/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.runx.ai](https://www.zero.xyz/host/api.runx.ai/llms.txt)