Markdown Endpoints

Every product page on our store responds to .md format. AI agents and LLMs can consume structured product data as clean Markdown including pricing, stock levels, variants, and descriptions.

Product pages

# Get any product as Markdown
GET /products/{handle}.md

# Example
GET /products/raspberry-pi-5.md

The Markdown response includes:

Product title and full description
Current pricing (including sale prices)
Local warehouse stock levels
Supplier stock levels
All variants with SKUs and individual pricing
Product images and options

Product search

# Search all products as Markdown
GET /products.md?q=jetson

Returns a Markdown listing of matching products with key details. Useful for AI agents that need to compare options within a single context window.

Other Markdown endpoints

Beyond product pages, several other resources are available as Markdown:

Cart — GET /cart/export_md — Current cart contents as Markdown
Quotes — GET /account/quotes/{id}/export_md — Quote with line items and terms
Invoices — GET /account/orders/{id}/invoice_md — Invoice for automated processing
Credit notes — GET /account/orders/{id}/credit_note_md — Credit note as Markdown
Statements — GET /account/orders/statement_md — Account statement

Why Markdown?

Markdown is the ideal format for LLMs because it's structured enough to be parsed reliably, but compact enough to fit in context windows. Compared to HTML, Markdown strips away layout and styling noise while preserving the semantic structure that AI agents need.

For programmatic access where you need typed fields (numbers, booleans), use the JSON API instead. For human-friendly formatted output, use the PDF exports.

Markdown Endpoints