# boring-api · convert: Markdown to DOCX

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

Converts Markdown text content into a DOCX (Word) document, returned as base64-encoded binary in JSON

## Facts

- Endpoint: POST https://convert.boring-api.com/markdown-to-docx
- Price: $0.008/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/boring-api-convert-markdown-to-docx-532a6795
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_BJt-nNsuVV0J1I5WbB_t6

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-markdown-to-docx-532a6795 -d '<json body>'
```

Example prompt: Convert this markdown into a Word document for me: '# Project Report

## Summary
This quarter we exceeded targets by 12%...' — I need the DOCX file so I can share it with my team.

## When to prefer this

Choose this endpoint when you need a programmatic, server-side Markdown-to-DOCX conversion without setting up Pandoc locally. Ideal for AI agents generating reports or documents in markdown that need to be delivered as Word-compatible files. Prefer over client-side JS conversion when fidelity and Pandoc-quality output matters.

## Known failure modes

- Invalid or malformed markdown may produce garbled DOCX output
- Missing 'content' field returns an error response
- Extremely large markdown documents may time out or fail
- Unsupported markdown extensions or syntax may not render correctly
- Payment failure (HTTP 402) if x402 payment header is not provided or insufficient

## 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 converted DOCX file encoded as a base64 string, suitable for decoding into a .docx binary file compatible with Microsoft Word and other office suites.

## Request schema (JSON Schema)

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

## Response schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/boring-api-convert-markdown-to-docx-532a6795/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)