There are three usual ways to feed WordPress content to AI systems and integrations: let them parse the rendered HTML, hand-maintain exported Markdown files, or point developers at the REST API. Here's the honest breakdown against all three.
Rendered HTML is built for browsers — the content arrives wrapped in navigation, theme markup, scripts and tracking that a machine has to fight through. Exported files are clean but stale the day after you export them. The REST API returns raw HTML in a JSON envelope, lives on /wp-json/ URLs nobody can derive from a permalink, and needs a developer on the other end. WP Markdown Endpoint (this site) makes the live page itself available on the permalink everyone already knows — clean Markdown at .md, a structured JSON representation at .json — generated fresh on every request, advertised with rel="alternate" links, llms.txt and an AI news feed so machines find it without being told.
| Feature | WP Markdown Endpoint | Raw HTML | DIY .md exports | REST API |
|---|---|---|---|---|
| Machine-readable content | ✓ Clean Markdown | ✗ Div soup | ✓ Clean | ◐ HTML in JSON |
| Always current | ✓ Generated per request | ✓ Live | ✗ Stale after export | ✓ Live |
| Discoverable URL | ✓ Permalink + .md | ✓ The permalink | ✗ Wherever you put it | ✗ /wp-json/… + post ID |
| Token cost for an LLM | ✓ Just the content | ✗ 10–50× the article | ✓ Low | ◐ Envelope + HTML |
| Code blocks survive | ✓ Fenced, language kept | ◐ Buried in markup | ◐ Depends on the export | ◐ Raw HTML |
| Drafts & private protected | ✓ 404, always | ✓ | ◐ Human error | ◐ Config-dependent |
| Maintenance burden | ✓ None | ✓ None | ✗ Every edit, forever | ◐ Developer time |
| Needs a developer | ✓ No | ✗ To parse it, yes | ◐ Or an editor's afternoon | ✗ Yes |
| Metadata included | ✓ Toggleable + front matter (Pro) | ◐ Scattered meta tags | ◐ If you typed it | ✓ JSON fields |
| Structured JSON, clean content | ✓ Permalink + .json, Markdown body (Pro) | ✗ | ✗ | ◐ Raw HTML inside |
| Latest-content feed for agents | ✓ JSON Feed 1.1 at /feed/ai/ (Pro) | ◐ RSS, HTML inside | ✗ | ◐ Paginated lists |
| Advertised on the page itself | ✓ rel="alternate" + Link headers | ✗ n/a | ✗ | ◐ One rel="https://api.w.org/" |
| SEO-safe duplicates | ✓ noindex + canonical on every response | ✓ n/a | ✗ Your problem | ✓ Not indexed |
| Index for crawlers | ✓ llms.txt + markdown-sitemap.md (Pro) | ◐ XML sitemap | ✗ | ◐ Paginated lists |
| Cost | From $49/yr · $599 lifetime | Free | Free — plus the hours | Free — plus the developer |
Your integrators need to write to the site, or want WordPress application data beyond content — users, settings, media management. That's the REST API's job and it does it well. Or you publish twice a year and don't mind re-exporting by hand.
You want AI systems, agents and content tools reading your live content in the formats they parse best — Markdown as a document, JSON as data — on URLs anyone can derive from the permalink, discoverable through rel="alternate" links, llms.txt and the /feed/ai/ news feed, with drafts and private content protected automatically and your SEO untouched. Install once, save permalinks, and every page you've ever published has machine-readable twins. That's us.
The converter is deliberately lightweight and dependency-free. For content built as pure visual design in a page builder, it captures the readable text and structure — not the layout. Only published, public content is ever served.