# boring-api · convert: DOCX to Markdown

> boring-api · convert: DOCX to Markdown is a paid API for AI agents from convert.boring-api.com, paid per call via x402, $0.005/call, status unknown (last checked 2026-09-14).

Converts a Microsoft Word DOCX file to Markdown text using Pandoc, accepting base64-encoded DOCX input and returning the Markdown output as JSON.

## Facts

- Endpoint: POST https://convert.boring-api.com/docx-to-markdown
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/boring-api-convert-docx-to-markdown-9f746972
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_wq4wJdzWQ_33LuYIea-Wp

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 boring-api-convert-docx-to-markdown-9f746972 -d '<json body>'
```

Example prompt: Can you convert this Word document to Markdown? Here's the DOCX file encoded in base64: [base64string].

## When to prefer this

Use this endpoint when you need to programmatically convert Microsoft Word (.docx) files to Markdown, especially in automated pipelines for documentation sites, static site generators, or content migration workflows. Prefer this over manual conversion or local Pandoc installs when you need a hosted, pay-per-call API with no infrastructure overhead.

## Known failure modes

- Invalid or corrupt base64 input returns an error
- Non-DOCX file encoded in base64 may produce garbled output or error
- Missing content_base64 field causes a validation error
- Very large DOCX files may time out or be rejected
- Complex DOCX formatting (e.g. tables, embedded images) may not convert perfectly

## How this service works

Document and data format conversions via Pandoc, Chromium-headless, and pure-JS libs. Text inputs/outputs are JSON-fielded; binary inputs/outputs use base64 in JSON for uniformity.

## Output

A JSON object containing the Markdown representation of the input DOCX file, with formatting such as headings, lists, bold/italic, and links translated into Markdown syntax.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "content_base64": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/boring-api-convert-docx-to-markdown-9f746972/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from convert.boring-api.com](https://www.zero.xyz/host/convert.boring-api.com/llms.txt)