# DOCX to Text Extractor

> DOCX to Text Extractor 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 structured tables from a Word .docx file provided via public URL or base64, returning JSON with text content and table data

## Facts

- Endpoint: POST https://well-010-docx-to-text.mmelnyk2000.workers.dev/mcp?utm_source=zero.xyz#docx-to-text#docx-to-text
- 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/docx-to-text-extractor-c9db2b77
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_4VDqhaZG5MGcbBBmQIxgI

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 docx-to-text-extractor-c9db2b77 -d '<json body>'
```

Example prompt: Can you extract all the text and tables from this Word document at https://example.com/report.docx and give me the full content as plain text?

## When to prefer this

Choose this endpoint when you need to programmatically extract text and table content from Microsoft Word .docx files hosted at public HTTPS URLs or provided as base64. It is well-suited for document processing pipelines, content indexing, and data extraction workflows. It does not support old binary .doc files, password-protected documents, or files on private networks. Prefer this over generic file parsers when the source is specifically a .docx and you need both text and structured table data in a single JSON response.

## Known failure modes

- File URL uses HTTP, file://, data://, localhost, or private IP — request rejected
- File exceeds 10 MB size cap — error returned
- Processing exceeds ~15 second timeout — timeout error
- More than 5 redirects encountered — redirect limit error
- File is an old binary .doc format (not .docx) — unsupported format error
- URL is inaccessible or returns non-200 status — fetch error
- Invalid or malformed base64 input — parse error

## 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 }.

## Output

Returns a JSON object containing: the original file reference and URL, the final URL after redirects, type set to 'docx', the full extracted plain text with [table N] placeholders where tables appear, an array of tables each containing rows of cell data, and any warnings (e.g. about unsupported features). Unicode dashes are normalized to '-'.

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/docx-to-text-extractor-c9db2b77/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)