# well-010-docx-to-text

> well-010-docx-to-text is a paid API for AI agents from well-010-docx-to-text.mmelnyk2000.workers.dev, paid per call via x402, $0.005/call, status unknown (last checked 2026-10-20).

Extracts plain text and tables from a Word .docx file provided as a public HTTPS URL or base64-encoded bytes

## Facts

- Endpoint: POST https://well-010-docx-to-text.mmelnyk2000.workers.dev/api/docx-to-text?utm_source=zero.xyz
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/well-010-docx-to-text-b8075584
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_cCkMpjtEblyOYb012-QQF

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 well-010-docx-to-text-b8075584 -d '<json body>'
```

Example prompt: Can you extract all the text and tables from this Word document? Here's the link: https://example.com/reports/quarterly-report.docx

## When to prefer this

Use this endpoint when you need to extract plain text and tabular data from a Word .docx file hosted at a public HTTPS URL, or when you have the file as base64. It is ideal for document ingestion pipelines, contract review, report parsing, or any workflow where you need programmatic access to Word document content. It is not suitable for old binary .doc files, PDF documents, or files behind authentication or on private networks.

## Known failure modes

- Non-HTTPS URLs (http, file, data, localhost, private IPs) are rejected with an error
- Files larger than 10 MB are rejected
- Old binary .doc format is not supported — only .docx
- Request times out if processing exceeds ~15 seconds
- More than 5 redirects causes failure
- Malformed or password-protected .docx files may fail to parse
- Network errors fetching the remote URL result in failure

## How this service works

Extract text and tables from a Word .docx file ($0.005 USDC via x402). Input: a public https url to a .docx, or docx_base64. https only — http, file, data, localhost, and private IPs are rejected. Caps: 10 MB file, ~15s timeout, max 5 redirects. Tables appear as [table N] placeholders in text. Unicode dashes/minus signs normalized to '-'. Old binary .doc files are not supported. Returns JSON { file, url, final_url, type: 'docx', text, tables: [{ rows }], warnings }. Provided as is, with no warranty or guarantee of accuracy or fitness. Nothing is stored.

## Output

Returns a JSON object containing: the filename (file), the original and final resolved URL, the document type ('docx'), the full extracted plain text with [table N] placeholders where tables appeared, an array of tables each with their rows, and any warnings about the document. Nothing is stored server-side.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "url": {
   "type": "string",
   "description": "https URL of a .docx file. http/file/data/localhost/private IPs rejected."
  },
  "filename": {
   "type": "string",
   "description": "Optional file name echoed back as `file`."
  },
  "docx_base64": {
   "type": "string",
   "description": "Alternative to url: the .docx file bytes, base64-encoded (max 10 MB)."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "additionalProperties": true
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/well-010-docx-to-text-b8075584/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from well-010-docx-to-text.mmelnyk2000.workers.dev](https://www.zero.xyz/host/well-010-docx-to-text.mmelnyk2000.workers.dev/llms.txt)