Gunjan Jaswal

EndPointy Menus adds custom REST API routes to expose your WordPress navigation menus as JSON.
Base namespace: <code>endpointy-menus/v1</code>
Endpoints:
<ul>
<li>
<code>GET /wp-json/endpointy-menus/v1/menus</code> 
Returns all registered menus with locations and items.
</li>
<li>
<code>GET /wp-json/endpointy-menus/v1/menus/<id></code> 
Returns a single menu and its items by menu ID.
</li>
<li>
<code>GET /wp-json/endpointy-menus/v1/locations</code> 
Returns all registered menu locations with assigned menus.
</li>
<li>
<code>GET /wp-json/endpointy-menus/v1/locations/<location></code> 
Returns a menu assigned to a specific location (e.g., ‘primary’, ‘footer’).
</li>
</ul>
Query Parameters:
<ul>
<li><code>nested=true</code> – Returns menu items in a hierarchical tree structure with parent-child relationships. 
Example: <code>/wp-json/endpointy-menus/v1/menus/2?nested=true</code></li>
</ul>
This is useful for headless WordPress setups or any external app that needs to read your menu structure.
<h3>Usage</h3>
Example requests:
Get all menus: 
 https://your-site.com/wp-json/endpointy-menus/v1/menus
Get single menu by ID: 
 https://your-site.com/wp-json/endpointy-menus/v1/menus/2
Get all menu locations: 
 https://your-site.com/wp-json/endpointy-menus/v1/locations
Get menu by location (e.g., ‘primary’): 
 https://your-site.com/wp-json/endpointy-menus/v1/locations/primary
Get nested menu structure: 
 https://your-site.com/wp-json/endpointy-menus/v1/menus/2?nested=true 
 https://your-site.com/wp-json/endpointy-menus/v1/locations/primary?nested=true
Use these URLs directly from your front-end application or API client.
<h3>Support the Developer</h3>
If you find this plugin useful, you can support the developer:
<ul>
<li>Website: https://gunjanjaswal.me</li>
<li>GitHub: https://github.com/gunjanjaswal/Endpointy-Menus</li>
<li>Ko-fi: https://ko-fi.com/gunjanjaswal</li>
</ul>
<h3>Contributing</h3>
Contributions, issues, and feature requests are welcome! 
GitHub: https://github.com/gunjanjaswal/Endpointy-Menus 
Issues: https://github.com/gunjanjaswal/Endpointy-Menus/issues

EndPointy Menus

Expose WordPress menus via a custom REST API endpoint for headless and external applications.

Michael Sablone

LLM Markdown exposes your public WordPress posts and pages as real <code>.md</code> routes. Simply append .md to any supported post or page URL to access its Markdown representation.
Each Markdown document includes structured YAML front matter and clean content extracted from the rendered HTML.
Designed for:
<ul>
<li>LLM and AI ingestion</li>
<li>Headless and hybrid workflows</li>
<li>Content export pipelines</li>
<li>SEO-friendly alternate representations</li>
</ul>
Example:
<pre><code>https://example.com/my-post.md
</code></pre>
Features:
<ul>
<li>Real <code>.md</code> URLs</li>
<li>YAML front matter (title, dates, taxonomy, URL)</li>
<li>Selector-based content extraction</li>
<li>Respects password protection</li>
<li>Optional respect for noindex</li>
<li>Per-post-type control</li>
<li>Caching for performance</li>
<li>Adds <code><link rel="alternate" type="text/markdown"></code></li>
</ul>
No Gutenberg lock-in. No content duplication. No custom post types required.

LLM Markdown – Expose Content as .md

Expose WordPress posts and pages as real .md URLs with YAML front matter for LLMs, AI ingestion, and headless workflows.

EndPointy Menus vs LLM Markdown – Expose Content as .md