# Runx Marketplace – Ausca Asynchronous Document Analysis

> Runx Marketplace – Ausca Asynchronous Document Analysis 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-15).

Submits a document to Ausca's asynchronous Textract-powered analysis pipeline via the Runx marketplace, returning a receipt for later result retrieval.

## Facts

- Endpoint: POST https://api.runx.ai/v1/skills/ausca/document-analysis/run
- Price: $0.05/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/runx-marketplace-ausca-asynchronous-document-analysis-3661ffb5
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_0hEkUj3Vl6v09u1CDW6W8

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-asynchronous-document-analysis-3661ffb5 -d '<json body>'
```

Example prompt: Kick off an async Ausca document analysis job on this invoice PDF — I don't need to wait for the result right now, just submit it and give me a reference so I can check back later.

## When to prefer this

Choose this endpoint when you need to analyze documents asynchronously and can tolerate a processing delay before results are available — ideal for large documents, batch workflows, or pipelines where you don't need an immediate synchronous response. Prefer the sibling synchronous OCR endpoint if you need instant results. Use this when idempotency is important to avoid duplicate job submissions in automated pipelines.

## Known failure modes

- Invalid or missing inputs object returns a 400 validation error
- Duplicate submission without idempotency key may trigger duplicate job creation
- Payment failure (x402) if USDC balance is insufficient or wallet not authorized
- Job submission succeeds but underlying Textract processing fails asynchronously — receipt returned but results never available
- Malformed document format not supported by Textract leads to processing error on retrieval
- Runner field must be 'invoke'; any other value will be rejected
- Idempotency key too short (minLength 1 not met) causes request rejection

## How this service works

Extract structured document data through Ausca's measured asynchronous document analysis service.

## Output

Returns a job receipt or submission acknowledgment containing a reference ID that can be used to poll or retrieve the completed asynchronous analysis results, including extracted text, tables, forms, and structured fields from the document.

## 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-asynchronous-document-analysis-3661ffb5/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)